io.github.chrischall/groupon-mcp vs uk.co.speedi/availability
io.github.chrischall/groupon-mcp is an MCP server published by chrischall. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). uk.co.speedi/availability is an MCP server published by speedi.co.uk. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Official MCP Registry | Listed Version: 1.2.0 Downloads/month (npm): 2 333 Downloads/week (npm): 551 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 1.0.1 No figure published Not marked · First seen |
| npm registry (MCP servers) | Listed Version: 1.2.0 Downloads/month (npm): 2 333 Downloads/week (npm): 551 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Not listed |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | io.github.chrischall/groupon-mcp | uk.co.speedi/availability |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 1 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release (differs) | 2026-11-04 (better) | 2026-10-14 (worse) |
| Where it runs (differs) | On your machine (groupon-mcp) | Remote server (www.speedi.co.uk/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 7, secrets among them: 1 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/chrischall/groupon-mcp | Not stated |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-13 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 27 h ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
io.github.chrischall/groupon-mcp
Groupon deals for Claude — search and browse local, goods, and travel deals
uk.co.speedi/availability
Which UK trades and local services are actually free right now. Live availability, not a directory.
How to run each
io.github.chrischall/groupon-mcp As a local MCP server: npm package
claude mcp add --env "GROUPON_SESSION_COOKIE=<YOUR_GROUPON_SESSION_COOKIE>" --transport stdio groupon-mcp -- npx -y groupon-mcp
Requires: GROUPON_SESSION_COOKIE (secret)
uk.co.speedi/availability As a remote MCP server
claude mcp add --transport http availability https://www.speedi.co.uk/mcp
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only uk.co.speedi/availability has a remote endpoint we check. How we check endpoints
Tools each declares
Neither the marketplaces of io.github.chrischall/groupon-mcp nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
The marketplaces of uk.co.speedi/availability publish no settings it asks for, so we do not compare settings.
What it can do: io.github.chrischall/groupon-mcp · What it can do: uk.co.speedi/availability · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.