Developers · MCP
AgentCrush MCP Server
v0 · Read-only · Free · No auth required
AgentCrush is market intelligence for the agent economy — an evidence-ranked index of AI agents, frameworks, and agent-facing services. This MCP server exposes that index as tools so any MCP-compatible AI client or agent can query it directly.
Informational only. AgentCrush market intelligence is for research and discovery purposes. Do not use for financial decisions. Rankings are deterministic signals, not investment advice.
Free & open in v0
- ✓No payment required — MCP calls are free in v0
- ✓No API key, no registration, no auth header
- ✓Read-only — all 4 tools are queries, no write actions exist
- ✓CORS open — accessible from browsers and agent runtimes
MCP vs x402 APIs — two separate channels
AgentCrush has two machine-readable interfaces. They serve different use cases and are independently priced:
MCP server (this page)
Free. No auth. Read-only tools for AI clients — lookup, search, compare, history.
x402 REST APIs
Pay-per-call via USDC on Base. No subscriptions.
- trust-summary — $0.02 / call
- history — $0.02 / call
- verification-status — $0.005 / call
Endpoint
MCP JSON-RPC 2.0 · Protocol version 2024-11-05 · Streamable HTTP transport
GET returns server info and tool manifest.
Client configuration
Add to your MCP client config (e.g. Claude Desktop, Cursor, or any MCP-compatible host):
{
"mcpServers": {
"agentcrush": {
"url": "https://www.agentcrush.xyz/api/mcp",
"transport": "http"
}
}
}Quick test
Full JSON-RPC 2.0 call — run this directly in your terminal:
curl -s https://www.agentcrush.xyz/api/mcp \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "lookup_agent",
"arguments": { "handle": "crewai" }
}
}'Example response (abbreviated):
{
"handle": "crewai",
"name": "CrewAI",
"tier": "evidence_ranked",
"rank": 23,
"scores": {
"total": 7820,
"visibility": 81,
"reputation": 62
},
"profile_url": "https://agentcrush.xyz/agent/crewai"
}Available tools
4 read-only tools · pass as params in a tools/call JSON-RPC request
lookup_agentRank, score, tier, archetype, ERC-8004 status, and profile for a single agent.
arguments:
{ "handle": "crewai" }search_agentsSearch agents by name or keyword. Returns up to 20 results ordered by visibility score.
arguments:
{ "query": "agent", "limit": 10 }compare_agentsSide-by-side rank, score, and archetype comparison for two agents, with a plain-text summary.
arguments:
{ "handle_a": "crewai", "handle_b": "autogpt" }get_historyDaily rank and score snapshots (deduplicated per calendar day). Returns safe empty result if no history exists.
arguments:
{ "handle": "crewai", "days": 30 }Protocol notes
- ·
POST /api/mcpaccepts MCP JSON-RPC 2.0 — supportsinitialize,tools/list,tools/call - ·
GET /api/mcpreturns server info and tool manifest (no JSON-RPC wrapper needed) - ·Inputs validated server-side — handles allow only
[a-zA-Z0-9_-], search queries stripped of SQL wildcards, limits clamped