Ext Ops Panel
Open dashboard
Comparison

io.github.IncodeTechnologies/incode-idv-mcp vs io.github.zekebuilds-lab/mcp-identity

io.github.IncodeTechnologies/incode-idv-mcp is an MCP server published by IncodeTechnologies. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.zekebuilds-lab/mcp-identity is an MCP server published by zekebuilds-lab. 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

Where each is published
Marketplaceio.github.IncodeTechnologies/incode-idv-mcpio.github.zekebuilds-lab/mcp-identity
Official MCP Registry Listed
Version: 1.0.5
Downloads/month (npm): 128
Downloads/week (npm): 15
Not marked · First seen
Listed
Version: 0.7.2
Downloads/month (npm): 183
Downloads/week (npm): 90
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

io.github.IncodeTechnologies/incode-idv-mcp vs io.github.zekebuilds-lab/mcp-identity
Factio.github.IncodeTechnologies/incode-idv-mcpio.github.zekebuilds-lab/mcp-identity
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@incodetech/incode-idv-mcp)On your machine (@powforge/mcp-identity)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 12, secrets among them: 0
LicenceNot statedNot stated
Repository (differs)github.com/incodetechnologies/incode-idv-mcpgithub.com/zekebuilds-lab/mcp-identity
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

In its own words, on Official MCP Registry:

MCP server for Incode IDV, providing identity verification tools for AI assistants.

io.github.zekebuilds-lab/mcp-identity

In its own words, on Official MCP Registry:

DoI score lookup, vouch event builder, and offline schnorr verify for AI agents.

How to run each

io.github.IncodeTechnologies/incode-idv-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "API_KEY=<YOUR_API_KEY>" --transport stdio incode-idv-mcp -- npx -y @incodetech/incode-idv-mcp

Requires: API_KEY (secret)

io.github.zekebuilds-lab/mcp-identity As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio mcp-identity -- npx -y @powforge/mcp-identity

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only io.github.IncodeTechnologies/incode-idv-mcp asks for

  • API_KEY (secret)

Only io.github.zekebuilds-lab/mcp-identity asks for

  • ORACLE_PUBKEY
  • ORACLE_URL

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: io.github.IncodeTechnologies/incode-idv-mcp · What it can do: io.github.zekebuilds-lab/mcp-identity · 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.

Where the data comes from: how the catalog is built