io.github.IncodeTechnologies/incode-idv-mcp vs Arkova Verification
io.github.IncodeTechnologies/incode-idv-mcp is an MCP server published by IncodeTechnologies. Marketplaces we read that list it: 1 (Official MCP Registry). Arkova Verification is an MCP server published by carson-see. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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 | ||
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.5 Downloads/month (npm): 193 Downloads/week (npm): 33 Not marked · First seen |
Listed Version: 1.0.1 No figure published 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.IncodeTechnologies/incode-idv-mcp | Arkova Verification |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@incodetech/incode-idv-mcp) | Remote server (edge.arkova.ai/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/incodetechnologies/incode-idv-mcp | github.com/carson-see/arkovacarson |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 31 h ago, requires a key |
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.IncodeTechnologies/incode-idv-mcp
MCP server for Incode IDV, providing identity verification tools for AI assistants.
Arkova Verification
Privacy-first document verification anchored to the public ledger.
How to run each
io.github.IncodeTechnologies/incode-idv-mcp As a local MCP server: npm package
claude mcp add --env "API_KEY=<YOUR_API_KEY>" --transport stdio incode-idv-mcp -- npx -y @incodetech/incode-idv-mcpRequires: API_KEY (secret)
Arkova Verification As a remote MCP server
claude mcp add --transport http arkova-verification https://edge.arkova.ai/mcp --header "X-API-Key: <YOUR_X_API_KEY>"Requires: X-API-Key header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Arkova Verification 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 Arkova Verification publish no settings it asks for, so we do not compare settings.
What it can do: io.github.IncodeTechnologies/incode-idv-mcp · What it can do: Arkova Verification · 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.