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.

AgentIndex

REMOTE · AGENTINDEX.APP

Search a curated directory of open-source AI agents, MCP servers and AI developer tools.

Available components

+3 this week 79 Trust /100

Last scanned (4 hours ago)

Scores higher than 79% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Search and Retrieval

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 911 tokens (~182/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management44
  • Stability check failed: schema churn in the 20 days we've observed: 0 tool removals, 2 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 38 to 41.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 31 to 34.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 24 to 28.

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 18 to 21.

  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 11.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 1 to 4.

  • 17 Oct 26 0
    • Stability: unverified → fail ▼ security
    • A breaking change shipped without a version bump: still 1.1.0 ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_tool_detail” rewrote its description, which is the text the model reads security
    • Tool “get_trending” rewrote its description, which is the text the model reads security
    • Tool “list_categories” rewrote its description, which is the text the model reads security
    • Tool “search_tools” rewrote its description, which is the text the model reads security
    • Tool “submit_tool” rewrote its description, which is the text the model reads security
    • Schema quality: pass → fail ▼ functional
    • “get_trending” changed the type of “limit”: number → integer ▼ functional
    • “search_tools” changed the type of “limit”: number → integer ▼ functional
    • Tool “get_tool_detail” now declares an output schema ▲ functional
    • Tool “get_trending” now declares an output schema ▲ functional
    • Tool “list_categories” now declares an output schema ▲ functional
    • Tool “search_tools” now declares an output schema ▲ functional
    • Tool “submit_tool” now declares an output schema ▲ functional
    • First check of Tool coverage: 100 functional
    • Schema quality: good → excellent functional
    • “get_tool_detail” reworded the description of “id” cosmetic
    • “get_trending” reworded the description of “limit” cosmetic
    • “search_tools” reworded the description of “category” cosmetic
    • “search_tools” reworded the description of “limit” cosmetic
    • “search_tools” reworded the description of “query” cosmetic
    • “submit_tool” reworded the description of “email” cosmetic
    • “submit_tool” reworded the description of “github_url” cosmetic
  • 16 Oct 26 73

    First indexed and scored.

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 5 Nov 2026 · Probed https://agentindex.app/api/mcp/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=agentindex.app CN=WE1,O=Google Trust Services,C=US 11 Sept 2026 10 Dec 2026 ECDSA 256 ECDSA-SHA256 cc7341364087ea5a13ad520759035537
SANs: agentindex.app, *.agentindex.app
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of agentindex.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
agentindex.app. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=15552000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://agentindex.app/api/mcp/ Verified 200
http (plaintext) http://agentindex.app/api/mcp/ HTTPS enforced 301 https://agentindex.app/api/mcp/
MCP tools · 5 exposed · ~801 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
get_tool_detail ~166

Get the full AgentIndex record for one tool when you already have its id (from search_tools, get_trending or an AgentIndex URL such as agentindex.app/en/tool/<id>/). Returns name, description, long intro, summary, features, use cases, pros and cons, when to choose or skip it, compatibility, install command, license, stars, last update date, tags, rank_score, website and GitHub URL. Fields that were never filled in are omitted. Returns an isError result if no tool has that id; use search_tools to find the right id.

NameTypeReqDescription
idstringyesTool id exactly as returned by search_tools or get_trending, usually "<github-owner>-<repo>", e.g. "hangwin-mcp-chrome".
NameTypeReqDescription
ai_tagsarray|null––
categorystring|null––
choose_if––When to pick this tool
compatibility––Compatible clients and platforms
cons––Weaknesses
descriptionstring|null––
features––Feature list
github_urlstring|null––
idstringyesTool id for get_tool_detail
install_commandstring|null––
intro_long––Longer introduction
last_updatedstring|null––
licensestring|null––
namestringyes–
pros––Strengths
rank_scorenumber|null–AgentIndex rank, 0-100
skip_if––When to pick something else
starsstring|number|null–GitHub stars, e.g. "12.3k"
summary––Short summary, { en, zh } or a string
tagsarray|null––
use_cases––Use case list
websitestring|null––

No examples provided.

get_trending ~136

Get the highest-ranked tools across the whole AgentIndex directory, for questions like "what are the best/most popular open-source AI tools right now". Ranking is by rank_score (0-100), which combines GitHub stars, how recently the repository was updated and the quality of its documentation; it is not a weekly-growth chart. Use search_tools instead when the user needs a specific kind of tool. Returns an array of {id, name, category, description, stars, rank_score, ai_tags, website, github_url}.

NameTypeReqDescription
limitinteger–Number of tools to return (1-50, default 10).
NameTypeReqDescription
toolsarrayyes–

No examples provided.

list_categories ~66

List every category in the AgentIndex directory with the number of tools in it, largest first. Call this before using the category filter of search_tools to get valid names, or to give the user an overview of the directory. Returns an array of {category, count}. Takes no arguments.

Input schema present but exposes no named parameters.

NameTypeReqDescription
categoriesarrayyes–

No examples provided.

search_tools ~248

Find AI agents, MCP servers and AI developer tools in the AgentIndex directory by keyword and/or category. Use this when the user describes a need ("MCP server for Postgres", "browser automation agent"); use get_trending instead to browse the best tools without a query. Every keyword must appear (case-insensitive) in the name, description, tags or category. Results are ordered by rank_score, highest first. Returns an array of {id, name, category, description, stars, website, github_url, tags, rank_score}; an empty array means no match, so retry with fewer or broader keywords. Pass an id to get_tool_detail for features, use cases and the install command.

NameTypeReqDescription
categorystring–Exact category name from list_categories (case-insensitive), e.g. "Browser Automation" or "RAG / Knowledge Base". Omit to search all categories.
limitinteger–Maximum number of results (1-50, default 10).
querystring–Space-separated keywords, all of which must match, e.g. "postgres mcp" or "browser automation". Omit to list the top tools of a category.
NameTypeReqDescription
toolsarrayyes–

No examples provided.

submit_tool ~185

Suggest a GitHub repository (an AI agent, MCP server or AI developer tool) for listing on AgentIndex. No login or API key needed. The submission is queued for human review, usually within 1-3 days; it does not appear in search results immediately. Tools are listed only if the repository is public and has at least 100 stars. Check with search_tools first that the tool is not already listed. Returns {success, message, github_url}, or an isError result if the URL is not a GitHub repository URL or the submission service is unavailable.

NameTypeReqDescription
emailstring–Optional address that receives an email when the review is done. Only send it if the user provided it.
github_urlstringyesRepository URL in the form https://github.com/<owner>/<repo>, e.g. https://github.com/modelcontextprotocol/servers.
NameTypeReqDescription
github_urlstring––
messagestringyes–
successbooleanyes–

No examples provided.

Install

How do I install the AgentIndex MCP server?

AgentIndex is a hosted endpoint at https://agentindex.app/api/mcp/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · agentindex.app

# add to Claude Code
claude mcp add --transport http app-agentindex-agentindex 'https://agentindex.app/api/mcp/'
Common questions

What is the AgentIndex MCP server?

AgentIndex is an MCP server listed in the public MCP registry as app.agentindex/agentindex. Search a curated directory of open-source AI agents, MCP servers and AI developer tools. This page covers its hosted endpoint (https://agentindex.app/api/mcp/).

Is the AgentIndex MCP server safe to use?

AgentIndex scores 79 out of 100 on VerifyMCP. 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 AgentIndex MCP server expose?

AgentIndex exposes 5 tools: search_tools, get_tool_detail, list_categories, get_trending, submit_tool. Their descriptions and schemas cost roughly 801 tokens of context every time the server is loaded.

Does the AgentIndex MCP server require authentication?

No. We connected to AgentIndex without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the AgentIndex MCP server still maintained?

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