Server data from the Official MCP Registry
P2P Agent Index MCP — publish and search decentralized web indexes over libp2p.
About
P2P Agent Index MCP — publish and search decentralized web indexes over libp2p.
Security Report
This P2P Agent Index MCP server demonstrates solid architecture with appropriate authentication via libp2p peer IDs and encrypted connections. The codebase shows good error handling and input validation for P2P operations. However, there are moderate concerns around unvalidated external HTTP requests to bootstrap health endpoints, potential denial-of-service vectors in keyword indexing, and insufficient validation of peer-supplied data that warrant user awareness. Supply chain analysis found 1 known vulnerability in dependencies (0 critical, 1 high severity). Package verification found 1 issue.
4 files analyzed · 9 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Required
This plugin requests these system permissions. Most are normal for its category.
What You'll Need
Set these up before or after installing:
Environment variable: AGENT_INDEX_DIRECTORY_URL
How to Install
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-agent-idx-mcp": {
"env": {
"AGENT_INDEX_DIRECTORY_URL": "your-agent-index-directory-url-here"
},
"args": [
"-y",
"@agent-idx/client"
],
"command": "npx"
}
}
}Documentation
View on GitHubFrom the project's GitHub README.
@agent-idx/client
MCP edge client for the P2P Agent Index Network. Connects to a routing peer, publishes local index records with agent-chosen keywords, and fetches records from peers over direct libp2p streams.
Source: github.com/agent-idx/mcp
Agents choose keywords and judge result relevance. The client provides network plumbing only.
Install (npx)
Routing and relay peer multiaddrs change over time. Copy current values from the network Active Nodes directory (/nodes on the project website), not from docs or old configs.
Optional: set AGENT_INDEX_DIRECTORY_URL in MCP server env so agents can call get_network_setup and receive the directory link.
{
"mcpServers": {
"agent-index": {
"command": "npx",
"args": [
"-y",
"@agent-idx/client",
"-b",
"<routing-peer-multiaddr-from-active-nodes>",
"-r",
"<relay-peer-multiaddr-from-active-nodes>"
],
"env": {
"AGENT_INDEX_DIRECTORY_URL": "https://<your-web-app>/nodes"
}
}
}
}
On the Active Nodes page:
- Routing Peers →
-b(required) - Relay Peers →
-r(recommended behind NAT / home routers) - Active Index Nodes → edge agents currently online (empty when nobody is connected; does not mean infrastructure is down)
After connecting, call MCP tool get_network_setup for a machine-readable summary of how the network works.
CLI
npx -y @agent-idx/client \
-b <routing-peer-multiaddr-from-active-nodes> \
-r <relay-peer-multiaddr-from-active-nodes>
For NAT traversal (home routers, etc.), add -r / --relay with the public relay peer multiaddr from Active Nodes. The client uses circuit-relay + DCUtR to upgrade to a direct connection before sending index queries.
Options
| Flag | Description |
|---|---|
-b, --bootstrap <multiaddr> | Required. Routing peer to dial (from Active Nodes) |
-r, --relay <multiaddr> | NAT relay peer for circuit-relay + DCUtR hole-punching (from Active Nodes) |
-d, --db <path> | Local index store (default: index_store.json) |
-k, --keywords <path> | Local keyword store (default: keywords.json) |
MCP tools
| Tool | Description |
|---|---|
get_network_setup | Start here — directory URL, configured peers, Active Nodes sections, blind-test flow |
publish_index | Store a page summary and advertise agent-supplied keywords |
search_index | Discover peers by keywords, fetch records for query, return merged JSON |
query_peer_index | Query a known peer ID directly (bypasses DHT; uses relay hole-punch when needed) |
add_keywords | Add keywords to this peer's advertised topic list |
remove_keywords | Remove keywords from this peer's advertised topic list |
set_keywords | Replace the peer's advertised keyword list |
find_peers_by_keyword | DHT/registry discovery only — peer IDs and multiaddrs |
get_peer_status | Local peer ID, configured routing/relay, keyword and record counts |
get_peer_profile | Fetch ANP locators from another edge peer over libp2p |
Develop from source
npm install
npm run build
node dist/index.js -b /ip4/127.0.0.1/tcp/4001/p2p/<BootstrapPeerId>
Publish to npm (maintainers)
npm login
npm publish --access public
Requires membership in the @agent-idx npm organization.
Reviews
No reviews yet
Be the first to review this server!
More Developer Tools MCP Servers
Git
Freeby Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
Fetch
Freeby Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
mcp-creator-python
Freeby mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.
MCP Marketplace
Freeby mcp-marketplace · Developer Tools
Search and install MCP servers from inside your AI client.
MarkItDown
Freeby Microsoft · Content & Media
Convert files (PDF, Word, Excel, images, audio) to Markdown for LLM consumption