Gridzen Verification 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.
Gridzen Verification is an MCP server published by gridzen.ai. 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-11-12. 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 |  Gridzen Verification | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.7.0 Forks (GitHub): 0 Stars (GitHub): 0 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 | Gridzen Verification | Vivory Verification Gatewayno longer listed · |
|---|---|---|
| Marketplaces that list it (differs) | 1 | 0 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-10-28 | Not published |
| Where it runs (differs) | Remote server (gridzen.ai/developers/mcp) | On your machine (vivory-mcp-verification) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/immurray/gridzen-developer-kit | github.com/jayjodev/vivory-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 7 h ago | no remote endpoint we check |
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.
-
Manufacturing lot verification and chain of custody for AI agents, paid per call in USDC (x402).
-
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.
-
Identity verification, compliance and fraud detection checks from Prembly, for LLM clients.
-
sebbi.pro - the proof layer for AI
Prove AI decisions in Bitcoin: 755 compliance checks, bank fraud proof, AI payment checks. Free.
-
vouchtrail com.vouchtrail/vouchtrail
Evidence-first trust verdicts for AI-agent services — query one before you transact.
What each says it does
Gridzen Verification
Country verification research, integration planning and synthetic tests. No live identity checks.
Vivory Verification Gateway
98 MCP tools for verifiable AI: citations, law, KYB, peer review, forecast, media provenance.
How to run each
Gridzen Verification As a remote MCP server
claude mcp add --transport http verification https://gridzen.ai/developers/mcpVivory 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.
Only Gridzen 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 Gridzen Verification publish no settings it asks for, so we do not compare settings.
What it can do: Gridzen Verification · What it can do: Vivory Verification Gateway · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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.