io.github.4DA-Systems/4da-mcp-server vs SEFAZ GO: IPVA
io.github.4DA-Systems/4da-mcp-server is an MCP server published by 4DA-Systems. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). SEFAZ GO: IPVA is an MCP server published by mcp-dir. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-13. 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.4DA-Systems/4da-mcp-server |  SEFAZ GO: IPVA |
|---|---|---|
| Official MCP Registry | Listed Version: 6.2.7 Downloads/month (npm): 2 434 Downloads/week (npm): 254 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| npm registry (MCP servers) | Listed Version: 6.2.7 Downloads/month (npm): 2 434 Downloads/week (npm): 254 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 | io.github.4DA-Systems/4da-mcp-server | SEFAZ GO: IPVA |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 2 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-11-09 | Not published |
| Where it runs (differs) | On your machine (@4da/mcp-server) | Remote server (api.mcp.ai/p_sefaz_go_ipva) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/4da-systems/4da-mcp-server | github.com/mcp-dir/sefaz_go_ipva-mcp |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 19 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.4DA-Systems/4da-mcp-server
Upgrade intelligence for AI agents: what an upgrade changes, where it touches your code, CVE scans.
SEFAZ GO: IPVA
SEFAZ GO: IPVA, official-source lookup. Platform-hosted, pay per query with prepaid credit.
How to run each
io.github.4DA-Systems/4da-mcp-server As a local MCP server: npm package
claude mcp add --transport stdio 4da-mcp-server -- npx -y @4da/mcp-serverSEFAZ GO: IPVA As a remote MCP server
claude mcp add --transport http sefaz-go-ipva-mcp https://api.mcp.ai/p_sefaz_go_ipvaCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only SEFAZ GO: IPVA 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
Neither one's marketplaces publish the settings it asks for.
What it can do: io.github.4DA-Systems/4da-mcp-server · What it can do: SEFAZ GO: IPVA · 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.