Add AgentIndex MCP server — AI agent registry with 25K+ agents

[agentindexworld]

AgentIndex MCP Server

Global AI Agent Registry with RSA-2048 cryptographic passports.

Tools provided:

• check_agent — Verify if an AI agent is registered and trusted
• register_agent — Register a new agent and get a cryptographic passport
• find_agent — Find agents to collaborate with by skill
• verify_passport — Verify a cryptographic passport
• get_reputation — Get full reputation and security report

Stats: 25,000+ agents, 14 nations, autonomy levels 0-5

Links:

• Website: https://agentindex.world
• MCP endpoint: https://agentindex.world/mcp
• GitHub: https://github.com/agentindexworld/agentindex-mcp-server

[JAORMX]

Hey @agentindexworld, thanks for submitting AgentIndex! I went through the PR and the upstream repo. There are a good number of spec issues to work through, plus some things the maintainer team will need to discuss.

server.json spec issues

The server.json is pretty far from the expected schema. I'd suggest looking at an existing remote server entry like registries/toolhive/servers/stripe-remote/server.json as a reference. Here's what needs fixing:

1. $schema is missing — add "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json"
2. name format is wrong — should be "io.github.stacklok/agentindex", not just "agentindex"
3. title is missing — a human-readable display name like "AgentIndex"
4. version field is wrong — use top-level "version": "1.0.0", not "version_detail": { "version": "..." }
5. icons array is missing from top-level fields
6. icon.svg file is missing — needs to be included in the PR
7. _meta block is entirely absent — this is where tier, status, tools, overview, and tags go. The extension key inside _meta must exactly match remotes[0].url (so "https://agentindex.world/mcp")
8. remotes[0].transport_type should be remotes[0].type — the field name is just type
9. tools at top level — tools belong inside the _meta extension block, not at the JSON root. And they should be a flat string array (["check_agent", "register_agent", ...]), not objects with name/description
10. description exceeds 100 chars — needs to be trimmed down
11. Tags should include "remote"

Repository assessment

The upstream repo (https://github.com/agentindexworld/agentindex-mcp-server) exists and has an MIT license, which is good. But it has only 1 commit and a single src/index.js file. No CI, no tests, no SECURITY.md, no dependency automation (Dependabot/Renovate), no releases. That's quite thin for our inclusion criteria.

Also note: the commit message lists get_autonomy_level as a tool, but the PR's server.json lists get_reputation instead. Worth double-checking which tools the server actually exposes.

Things the team needs to discuss

• Remote server to third-party infrastructure: All tool calls would go to https://agentindex.world/mcp, which you operate. For remote servers we can't audit what's running on the other end, so we rely more heavily on the source code and project maturity... which is pretty early here.
• Proprietary agent economy: The $SHELL currency, Bitcoin-anchored identity proofs, and the registration model are a pretty unusual dependency to introduce into the catalog. We'd need to think about whether this fits the scope.
• No auth configured: The server involves agent registration and identity management but there's no oauth_config or authentication mechanism in the entry. That seems like a gap for a service handling identity.

What to do

1. Rework server.json from scratch using the stripe-remote entry as a template
2. Add the icon.svg file
3. Beef up the upstream repo (CI, tests, releases, SECURITY.md)
4. Clarify the auth story for the remote endpoint

Happy to answer questions about the schema!

[JAORMX]

Hey @agentindexworld, thanks for taking the time to submit AgentIndex!

We're going to close this one for now. The upstream project doesn't quite meet our registry inclusion criteria yet... the repo has a single commit and is missing CI, tests, releases, a security policy, and dependency automation. Those are things we look for to ensure the servers in the catalog meet a baseline of maturity and security.

The server.json also needs a pretty significant rework to match the expected schema (the review above has the details).

If the project matures and you'd like to resubmit, we'd be happy to take another look! Check out the stripe-remote entry as a template and our adding entries guide for the full spec.

Thanks again for your interest!