io.github.codespar/mcp-jumio vs Vivory Verification Gateway
Vivory Verification Gateway is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑23.
io.github.codespar/mcp-jumio is an MCP server published by codespar. Marketplaces we read that list it: 1 (Official MCP Registry). Vivory Verification Gateway is an MCP server published by jayjodev. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-29. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.codespar/mcp-jumio | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.2 Downloads/month (npm): 96 Downloads/week (npm): 19 Forks (GitHub): 52 Stars (GitHub): 275 Not marked · First seen |
Removed on 2026-10-23 Version: 0.10.0 Downloads/month (PyPI): 104 Downloads/week (PyPI): 17 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 | io.github.codespar/mcp-jumio | Vivory Verification Gatewayno longer listed · |
|---|---|---|
| Marketplaces that list it (differs) | 1 | 0 |
| Stars (GitHub) (differs) | 275 | 0 |
| Forks (GitHub) (differs) | 52 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@codespar/mcp-jumio) | On your machine (vivory-mcp-verification) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 4, secrets among them: 1 | 2, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/codespar/mcp-dev-latam | github.com/jayjodev/vivory-mcp |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of Vivory Verification Gateway
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
MCP server exposing 11 honesty-SDK kits (grounding, trust, audit, corroboration) as agent tools.
-
agent-skill io.github.Deep-Identity-Inc/agent-skill
An MCP Server that provides identity verification and anti-fraud tools for AI agents via deepidv.
-
sebbi.pro - the proof layer for AI
Prove AI decisions in Bitcoin: 755 compliance checks, bank fraud proof, AI payment checks. Free.
-
MCP x402 - Evidence-Backed Web Verification
Evidence-backed x402 web verification for AI agents, with auditable decisions for every condition.
-
vouchtrail com.vouchtrail/vouchtrail
Evidence-first trust verdicts for AI-agent services — query one before you transact.
-
oathlayer io.github.oathlayer/oathlayer
Verify AI outputs against real sources. Returns a trust signal and permanent doc number.
What each says it does
io.github.codespar/mcp-jumio
MCP server for Jumio — global identity verification + KYX: documents, liveness, AML screening
Vivory Verification Gateway
98 MCP tools for verifiable AI: citations, law, KYB, peer review, forecast, media provenance.
How to run each
io.github.codespar/mcp-jumio As a local MCP server: npm package
claude mcp add --env "JUMIO_API_SECRET=<YOUR_JUMIO_API_SECRET>" --env "JUMIO_API_TOKEN=<YOUR_JUMIO_API_TOKEN>" --env "JUMIO_USER_AGENT=<YOUR_JUMIO_USER_AGENT>" --transport stdio mcp-jumio -- npx -y @codespar/mcp-jumioRequires: JUMIO_API_SECRET (secret), JUMIO_API_TOKEN, JUMIO_USER_AGENT
Vivory Verification Gateway
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
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.codespar/mcp-jumio asks for
JUMIO_API_SECRET (secret)JUMIO_API_TOKENJUMIO_REGIONJUMIO_USER_AGENT
Only Vivory Verification Gateway asks for
VIVORY_API_BASEVIVORY_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: io.github.codespar/mcp-jumio · What it can do: Vivory Verification Gateway · 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.