The MCP server index that vets servers, not just lists them. Search by task, then get an advisory screen on a server before your agent calls its tools: whether each tool does what it claims, backed by conformance monitoring and a public drift ledger. Advisory (REVIEW / UNVERIFIED), monitored not enforced, not a safety verdict. Drop-in for Claude Desktop, Claude Code, Cursor, Gemini CLI, Cline.
Server exposes 6 tools with complete JSON schemas and descriptions. All tools are READ_ONLY and stateless. Naming follows verb_noun convention (recommend_, search_, get_, compare_, check_, assess_). Descriptions are present but vary in quality: some are terse (e.g., 'Search query.' for search_mcp_servers) while others provide context. Parameters have types and descriptions. However, several descriptions fall below the 50-200 char LLM-optimized baseline, and output schemas are not documented in the source. Error handling is basic (API errors thrown as generic messages). No tool annotations (readOnlyHint, etc.) despite all being read-only.
Server slug to assess.
Registry slug from search_mcp_servers / recommend results, e.g. "io-github-microsoft-playwright-mcp" (NOT a short name like "github").
Server slugs to compare.
Slug of the server (from search_mcp_servers or recommend_mcp_for_task results).
Natural-language description of the task, e.g. "read PDFs and write to S3" or "search GitHub and open a PR".
Search query.
Output schemas not documented. Tools return API responses but LLMs cannot see what fields to expect, forcing them to infer structure and plan downstream calls blindly.
Terse parameter descriptions. 'Search query.' and 'Server slugs to compare.' lack context on expected format, constraints, or when to use. Descriptions should be 50-200 chars and explain WHAT, WHEN, and HOW.
No tool annotations. All 6 tools are read-only (no side effects), but lack readOnlyHint annotation. This forces LLMs to reason about safety instead of relying on machine-readable hints.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 62 | 2026-07-28+ | v2 |
Generic error handling. API errors are thrown as 'mcpindex API {status}: {text}' with no recovery guidance. LLMs cannot determine if the error is retryable, user-fixable, or fatal.
No pagination or result limits documented. search_mcp_servers accepts a 'limit' param (default 10, max 50) but the tool description does not state this constraint or explain pagination behavior.