Linkbreakers MCP vs io.github.Jmpy-me/jmpy-mcp-server
Linkbreakers MCP is an MCP server published by linkbreakers.com. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). io.github.Jmpy-me/jmpy-mcp-server is an MCP server published by Jmpy-me. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. 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 |   Linkbreakers MCP |  io.github.Jmpy-me/jmpy-mcp-server |
|---|---|---|
| Official MCP Registry | Listed Version: 1.195.2 Downloads/month (npm): 7 564 Downloads/week (npm): 2 488 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| npm registry (MCP servers) | Listed Version: 1.195.0 Downloads/month (npm): 7 564 Downloads/week (npm): 2 488 Forks (GitHub): 0 Stars (GitHub): 0 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 | Linkbreakers MCP | io.github.Jmpy-me/jmpy-mcp-server |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-11-08 | Not published |
| Where it runs (differs) | Remote server or your machine | Remote server (jmpy.me/mcp/sse) |
| Transport (differs) | Streamable HTTP | SSE |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/linkbreakers-com/agent-skills | github.com/jmpy-me/jmpy-mcp-server |
| Changes in the last 7 days (differs) | 20 or more | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Status out of date: last check 45 h ago returned HTTP 401 | No HTTP response at the last check (10 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
Linkbreakers MCP
QR-driven customer-journey platform for tracked QR codes, short links, and analytics.
io.github.Jmpy-me/jmpy-mcp-server
Official JMPY.me MCP Server: URL shortener, QR codes, and 70+ marketing analytics tools.
How to run each
Linkbreakers MCP As a remote MCP server
claude mcp add --transport http linkbreakers-mcp https://mcp.linkbreakers.com --header "Authorization: Bearer <YOUR_TOKEN>"Requires: LINKBREAKERS_API_TOKEN (secret), Authorization header
io.github.Jmpy-me/jmpy-mcp-server As a remote MCP server
claude mcp add --transport sse jmpy-mcp-server https://jmpy.me/mcp/sseCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only the endpoint of Linkbreakers MCP responded at the last daily check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of io.github.Jmpy-me/jmpy-mcp-server publish no settings it asks for, so we do not compare settings.
What it can do: Linkbreakers MCP · What it can do: io.github.Jmpy-me/jmpy-mcp-server · 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.