Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

mcpindex

NPM · MCP-SERVER-MCPINDEX · 2 COMPONENTS · SCANNED SEP 20

The MCP server index that vets servers, not just lists them. Advisory screen before you install.

−1 this week 84 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 0 of 3 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 528 tokens (~88/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the mcpindex MCP server?

mcpindex runs locally as an npm package, launched with npx -y mcp-server-mcpindex. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · mcp-server-mcpindex

# add to Claude Code
claude mcp add gautamgb-mcp-server-mcpindex -- npx -y mcp-server-mcpindex
// .cursor/mcp.json
{
  "mcpServers": {
    "gautamgb-mcp-server-mcpindex": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-mcpindex"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "gautamgb-mcp-server-mcpindex": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-mcpindex"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add gautamgb-mcp-server-mcpindex -- npx -y mcp-server-mcpindex
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "gautamgb-mcp-server-mcpindex": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "mcp-server-mcpindex"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add gautamgb-mcp-server-mcpindex --command npx --arg -y --arg mcp-server-mcpindex
# ~/.hermes/config.yaml
mcp_servers:
  gautamgb-mcp-server-mcpindex:
    command: "npx"
    args: ["-y", "mcp-server-mcpindex"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "gautamgb-mcp-server-mcpindex": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "mcp-server-mcpindex"
      ]
    }
  }
}
# add to Vellum
assistant mcp add gautamgb-mcp-server-mcpindex -t stdio -c npx -a -y mcp-server-mcpindex
// mcp.json
{
  "mcpServers": {
    "gautamgb-mcp-server-mcpindex": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-mcpindex"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 −2
    • Security disclosure: unverified → fail functional
    • Stability: pass → 0.83 functional
  • 17 Sept 26 0
    • Stability: 0.97 → pass security
    • Security disclosure: fail → unverified functional
  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Sept 26 −1
    • Stability: pass → 0.93 functional
  • 14 Sept 26 0
    • Stability: 0.97 → pass security
  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/mcp-server-mcpindex@0.4.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 3 packages
Packages resolved 3
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~528 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
assess_server ~77

Aggregated pre-flight trust assessment across all tools on an MCP server. Same verdict shape as check_tool_trust. Use for "is THIS server worth integrating?" decisions. v1 advisory; conformance monitored not enforced; verdicts may be UNVERIFIED if not yet probed.

NameTypeReqDescription
server_idstringyesServer slug to assess.

No output schema declared.

No examples provided.

check_tool_trust ~163

Pre-invocation advisory screen for a specific tool on an MCP server. Returns an advisory verdict object (directive ALLOW | DENY | REVIEW | UNVERIFIED, dimensions, freshness). At v1 the public screen produces REVIEW or UNVERIFIED only - ALLOW/DENY are reserved. Not the in-path gate (mcpindex-gate). Agents SHOULD treat UNVERIFIED as "human review required", never as ALLOW.

NameTypeReqDescription
server_idstringyesRegistry slug from search_mcp_servers / recommend results, e.g. "io-github-microsoft-playwright-mcp" (NOT a short name like "github").
tool_namestringyesTool name as exposed by the server (e.g. "create_pull_request").

No output schema declared.

No examples provided.

compare_servers ~42

Side-by-side comparison of 2-5 MCP servers - quality scores, install paths, env vars.

NameTypeReqDescription
slugsarrayyesServer slugs to compare.

No output schema declared.

No examples provided.

get_install_command ~69

Get the exact install command for a given MCP server and client. Returns a JSON block ready to paste into the client config.

NameTypeReqDescription
clientstringyesTarget client.
server_slugstringyesSlug of the server (from search_mcp_servers or recommend_mcp_for_task results).

No output schema declared.

No examples provided.

recommend_mcp_for_task ~92

Recommend the best MCP servers for a natural-language task. Returns top 3 ranked picks with reasoning, install commands, and quality scores. Use this when the user asks for the right MCP server for a task they want to do.

NameTypeReqDescription
taskstringyesNatural-language description of the task, e.g. "read PDFs and write to S3" or "search GitHub and open a PR".

No output schema declared.

No examples provided.

search_mcp_servers ~85

Keyword + semantic search across every MCP server mcpindex indexes. Use when the user knows what tool category they want but not which server.

NameTypeReqDescription
categorystringOptional category filter (e.g. database, browser, github, productivity).
limitnumberMax results (default 10, max 50).
querystringyesSearch query.

No output schema declared.

No examples provided.

Common questions

What is the mcpindex MCP server?

mcpindex is an MCP server listed in the public MCP registry as io.github.gautamgb/mcp-server-mcpindex. The MCP server index that vets servers, not just lists them. Advisory screen before you install. This page covers its npm package (mcp-server-mcpindex).

Is the mcpindex MCP server safe to use?

mcpindex scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the mcpindex MCP server expose?

mcpindex exposes 6 tools: recommend_mcp_for_task, search_mcp_servers, get_install_command, compare_servers, check_tool_trust, assess_server. Their descriptions and schemas cost roughly 528 tokens of context every time the server is loaded.

Is the mcpindex MCP server still maintained?

mcpindex is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the mcpindex MCP server under?

mcpindex declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.