io.github.Deesmo/arch-tools-mcp vs io.github.jbobbink/glippy-mcp
io.github.Deesmo/arch-tools-mcp is an MCP server published by Deesmo. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.jbobbink/glippy-mcp is an MCP server published by jbobbink. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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 |  io.github.Deesmo/arch-tools-mcp |  io.github.jbobbink/glippy-mcp |
|---|---|---|
| Official MCP Registry | Listed Version: 2.0.1 Forks (GitHub): 1 Stars (GitHub): 3 Not marked · First seen |
Listed Version: 0.9.0 Downloads/month (npm): 651 Downloads/week (npm): 56 Not marked · First seen |
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.Deesmo/arch-tools-mcp | io.github.jbobbink/glippy-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 3 | No figure on GitHub |
| Forks (GitHub) (differs) | 1 | No figure on GitHub |
| Last release (differs) | Not published | 2026-10-20 |
| Where it runs (differs) | Remote server (archtools.dev/mcp) | On your machine (glippy-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/deesmo/arch-ai-tools | github.com/jbobbink/glippy |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 3 days ago | no remote endpoint we check |
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.Deesmo/arch-tools-mcp
63 production tools for AI agents — one API key, pay per call in USDC (x402) or Stripe credits.
io.github.jbobbink/glippy-mcp
GEO (Generative Engine Optimization) analysis: check any domain's AI-readiness for LLM search
How to run each
io.github.Deesmo/arch-tools-mcp As a remote MCP server
claude mcp add --transport http arch-tools-mcp https://archtools.dev/mcpio.github.jbobbink/glippy-mcp As a local MCP server: npm package
claude mcp add --env "GLIPPY_LICENSE_KEY=<YOUR_GLIPPY_LICENSE_KEY>" --transport stdio glippy-mcp -- npx -y glippy-mcpRequires: GLIPPY_LICENSE_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.Deesmo/arch-tools-mcp has a remote endpoint we 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.Deesmo/arch-tools-mcp publish no settings it asks for, so we do not compare settings.
What it can do: io.github.Deesmo/arch-tools-mcp · What it can do: io.github.jbobbink/glippy-mcp · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.