InzerPro vs io.github.glongusmain/glongus-mcp
InzerPro is an MCP server published by inzerpro.cz. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.glongusmain/glongus-mcp is an MCP server published by glongusmain. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-10. 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.glongusmain/glongus-mcp | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.1 No figure published Not marked · First seen |
Listed Version: 0.18.0 Downloads/month (npm): 2 313 Downloads/week (npm): 173 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.18.0 Downloads/month (npm): 2 313 Downloads/week (npm): 173 Forks (GitHub): 0 Stars (GitHub): 0 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 | InzerPro | io.github.glongusmain/glongus-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | 2026-11-10 (better) | 2026-11-08 (worse) |
| Where it runs (differs) | Remote server (www.inzerpro.cz/api/mcp) | Remote server or your machine |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | Not stated | github.com/glongusmain/glongus-mcp |
| Changes in the last 7 days | 3 | 3 |
| First seen (differs) | 2026-11-07 | 2026-10-11 |
| Endpoint at the last check (differs) | not checked yet | Responded 27 h ago, requires authentication |
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
InzerPro
Create, edit, relist and take down Czech and Slovak classified ads from your AI agent.
io.github.glongusmain/glongus-mcp
Let your agent buy and sell physical goods, with escrow and shipping.
How to run each
InzerPro As a remote MCP server
claude mcp add --transport http agent https://www.inzerpro.cz/api/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
io.github.glongusmain/glongus-mcp As a remote MCP server
claude mcp add --transport http glongus-mcp https://api.glongus.com/mcpRequires: GLONGUS_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.glongusmain/glongus-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 InzerPro publish no settings it asks for, so we do not compare settings.
What it can do: InzerPro · What it can do: io.github.glongusmain/glongus-mcp · 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). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.