mcpindex.ai valid

mcpindex.ai

The in-path trust gate for agent tool calls. Pins each MCP tool contract and HOLDs the call when it silently drifts - before your agent acts. Zero credentials. Fail-closed. Not a safety oracle.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-25T04:53:28.676Z. Cached copy · Source on mcpindex.ai

# mcpindex.ai

> The in-path trust gate for agent tool calls. Pins each MCP tool contract and HOLDs the call when it silently drifts - before your agent acts. Zero credentials. Fail-closed. Not a safety oracle.

Secondary: a public directory of MCP servers with advisory screening verdicts (REVIEW / UNVERIFIED at v1) so you can check a tool before you wire it.

## Scale

- How many MCP servers are there? 48988 active, latest-version entries in the official registry (methodology + live count: [mcpindex.ai/stats](https://mcpindex.ai/stats)).
- What is MCP tool drift? MCP tool drift is any change to a tool's contract, as a Model Context Protocol server serves it, after a client has already seen that contract. Definition, the change kinds that count, method and measured rates with DOIs: [mcpindex.ai/drift](https://mcpindex.ai/drift).
- Categories: 29
- Source: registry.modelcontextprotocol.io (canonical), enriched with quality scoring, semantic search, and advisory screen verdicts. Delisted and superseded versions are excluded so the same server never counts twice.

## Drift Gate (in-path; tier-0 live, tiers 1-3 held off by default)

- What it is: an in-path trust gate for agent tool calls. It pins each MCP tool's contract trust-on-first-use (TOFU) and, before your agent acts, HOLDs the call the moment that contract silently changes. Unlike the advisory screen below, it sits in the call path, so it can HOLD, not merely alert.
- Method: a deterministic contract-diff (ChangeKind taxonomy: added-required-param, required-set-expanded, constraint-narrowed, type-changed, enum-values-removed, removed-param, annotation-flip-to-destructive, param-mirrored-to-header, output-schema-added/changed, tool-added/removed), plus an injection/exfil marker scan over the input and output schema and description. Postures: Monitor (releases drift holds with a note; a tamper hold and an internal error still stop the call) / Guard (default; hold dangerous, INCONCLUSIVE where behaviour is the gate, auto-accept proven-benign) / Strict (hold anything not proven benign - NOT every drift: the benign auto-accept runs before the posture layer, so a proven-benign change proceeds under strict too). Fail-closed.
- Install: one-click config-wire across Claude Desktop / Claude Code / Cursor / VS Code / Windsurf / Cline / Zed / Gemini CLI via `uv tool install mcpindex-gate && mcpindex-config-wire` or `curl -fsSL https://mcpindex.ai/install.sh | sh` (rewrites the host config to route each server through the gate, which passes each server its env and stores no credentials), or the SDK wrap() one-liner (TS + Python) around an already-authenticated session. Legacy `mcpindex-preflight` is EOL (frozen 0.7.0); install `mcpindex-gate`, not preflight. See /docs.
- Tiered ladder: tier-0 deterministic contract-diff is the live, deterministic leg and runs first. Above it the ladder is built as in-path seams - a cloud tier-1 corpus lookup (a contract judged once clears or condemns it everywhere), a ti
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=mcpindex.ai · GET /v1/domain/mcpindex.ai · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for mcpindex.ai:
1. POST https://agentwebmap.com/v1/sites/mcpindex.ai/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://mcpindex.ai/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/mcpindex.ai/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/mcpindex.ai).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.