MCP.Market

Coupon Swarm MCP server

by Geo-Coder-17·io.github.Geo-Coder-17/coupon-swarm·v0.1.0·1 stars

Shared CC0 ledger of public coupon codes with dates: find, deposit and report codes.

C65/100grade C
What users say
No reviews yet
Be the first
Safety scan
C65/100

full report

Adoption
New

1 stars

Reviews

Write one

Nobody has reviewed Coupon Swarm yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Coupon Swarm tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.10 · 2026-10-14 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualityno auth information5/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityregistry namespace matches repository owner6/10
Overall 65/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Coupon Swarm compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
65/100
higher than 20% of 48,255 servers
GitHub stars
1
more than 65% of 28,688 servers

Install Coupon Swarm in Claude Code, Cursor or VS Code

The registry entry has no remote endpoint or installable package.

What the publisher says

From the Coupon Swarm repository's README, as published. We do not edit it. Read it on GitHub

coupon-swarm

A shared, open ledger of public coupon codes that AI agents and humans can read from and add to. Every code carries dates (found, expires, last verified), because codes die. Nothing here is affiliate-tagged: a code is a code, and the source it came from is linked next to it.

Pick up codes: https://raw.githubusercontent.com/Geo-Coder-17/coupon-swarm/main/codes.json (machine-readable) or CODES.md (a table of the live ones). Alternate pick-up URLs (GitHub Pages): https://geo-coder-17.github.io/coupon-swarm/codes.json and https://geo-coder-17.github.io/coupon-swarm/llms.txt. Deposit codes: open an issue with one of the forms, or send a pull request. A bot validates and merges within minutes. No push rights needed. For AI agents: the full protocol is in AGENTS.md and summarised in llms.txt. An MCP server is in mcp/.

Pick up

# every live code for one store
curl -s https://raw.githubusercontent.com/Geo-Coder-17/coupon-swarm/main/codes.json \
  | jq '.codes[] | select(.status=="active" and .store=="geekbuying.com")'

# live codes usable from Denmark (country code or global), newest verification first
curl -s https://raw.githubusercontent.com/Geo-Coder-17/coupon-swarm/main/codes.json \
  | jq '[.codes[] | select(.status=="active" and (.region|index("DK") or index("EU") or index("global")))] | sort_by(.last_verified) | reverse | .[] | {store, code, discount, expires_on, last_verified}'
import json, urllib.request
ledger = json.load(urllib.request.urlopen("https://raw.githubusercontent.com/Geo-Coder-17/coupon-swarm/main/codes.json"))
live = [c for c in ledger["codes"] if c["status"] == "active"]

Always pass the dates on to whoever you give a code to. lastverified says when someone last saw it on the brand's page or applied it; expireson is the end date the source stated, or null if none was stated.

Deposit

The intake bot (.github/workflows/intake.yml) parses the issue, normalizes and validates the entry, commits it, comments with the result, and closes the issue. Invalid entries get a comment listing the problems and a needs-fix label; edit the issue and it is re-checked.

Rules

  • Public promotional codes only. Codes the brand publishes for everyone, sponsor codes read out on shows, campaign codes on retailer pages, codes on coupon sites that a second source corroborates.
  • Not allowed: personal referral codes, single-use codes from someone's inbox, employee or insider codes, leaked codes, and codes that were guessed or generated. Testing codes by hammering a checkout with guesses is exactly the behaviour this ledger exists to make unnecessary.
  • status: active needs a lastverified date.** Only claim it if you saw the code on the brand's own current page or applied it successfully that day. Aggregator-only sightings are unverified.
  • Dates are ISO 8601 (YYYY-MM-DD), UTC. expires_on is only what a source states; never guess an expiry.
  • Be honest in submitted_by: a model id (claude-fable-5-1, gpt-5, gemini-2.5-pro), a GitHub handle, or human.

Dates and housekeeping

A daily workflow (.github/workflows/expire.yml, 03:17 UTC) keeps the ledger honest:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Coupon Swarm: common questions

Is Coupon Swarm MCP server safe?
With care: it is graded C, so read the findings first (65/100). Read the Coupon Swarm safety report
Does Coupon Swarm need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Coupon Swarm maintained?
The last commit was 21 days ago (2026-10-14). The latest release is v0.1.0.
How does Coupon Swarm compare with other MCP servers?
safety score 65/100 (higher than 20% of 48,255 servers); github stars 1 (more than 65% of 28,688 servers). Full comparison.