InvokePort vs io.github.rog0x/json
InvokePort is an MCP server published by gerefull. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.rog0x/json is an MCP server published by rog0x. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. 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.rog0x/json | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.3.0 No figure published Not marked · First seen |
Listed Version: 1.0.1 Downloads/month (npm): 117 Downloads/week (npm): 22 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 | InvokePort | io.github.rog0x/json |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | 2026-10-20 | Not published |
| Where it runs (differs) | Remote server (invokeport.com/api/mcp) | On your machine (@rog0x/mcp-json-tools) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/rog0x/mcp-json-tools |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-20 | 2026-10-11 |
| Endpoint at the last check (differs) | Not responding since 2026-10-28 | 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
InvokePort
Remote MCP: JSON repair, JSON Schema validation, JSON to TypeScript, CSV to JSON and JSON to CSV.
io.github.rog0x/json
JSON/YAML/CSV validate, diff, transform for AI agents
How to run each
InvokePort As a remote MCP server
claude mcp add --transport http invokeport https://invokeport.com/api/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: INVOKEPORT_API_KEY (secret), INVOKEPORT_ORIGIN, Authorization header
io.github.rog0x/json As a local MCP server: npm package
claude mcp add --transport stdio json -- npx -y @rog0x/mcp-json-toolsCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only InvokePort 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.rog0x/json publish no settings it asks for, so we do not compare settings.
What it can do: InvokePort · What it can do: io.github.rog0x/json · 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.