Descope vs Gridzen Verification
Descope is an MCP server published by descope-sample-apps. Marketplaces we read that list it: 1 (Docker MCP Catalog). Gridzen Verification is an MCP server published by gridzen.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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 |  Descope |  Gridzen Verification |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:554b2b490c18 Forks (GitHub): 7 Pulls (Docker Hub): 17 879 Stars (Docker Hub): 0 Stars (GitHub): 38 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.6.1 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 | Descope | Gridzen Verification |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 38 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 17 879 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 7 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-12 |
| Where it runs (differs) | On your machine (mcp/descope) | Remote server (gridzen.ai/developers/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 4 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Licence | MIT | MIT |
| Repository (differs) | github.com/descope-sample-apps/descope-mcp-server | github.com/immurray/gridzen-developer-kit |
| Changes in the last 7 days (differs) | 0 | 5 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 38 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
Descope
The Descope Model Context Protocol (MCP) server provides an interface to interact with Descope's Management APIs, enabling the search and retrieval of project-related information.
Gridzen Verification
Country verification research, integration planning and synthetic tests. No live identity checks.
How to run each
Descope As a local MCP server: Docker image
claude mcp add --env "DESCOPE_MANAGEMENT_KEY=<YOUR_DESCOPE_MANAGEMENT_KEY>" --transport stdio descope -- docker run -i --rm -e DESCOPE_MANAGEMENT_KEY mcp/descopeRequires: DESCOPE_MANAGEMENT_KEY (secret)
Gridzen Verification As a remote MCP server
claude mcp add --transport http verification https://gridzen.ai/developers/mcpCommands 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
The marketplaces of Gridzen Verification publish no list of tools, so we do not compare tools.
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: Descope · What it can do: Gridzen Verification · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.