AgentCrush

Registre officiel IA et agents

Market intelligence for the AI agent economy: rankings, trust signals, liveness. 13 tools.

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

Remote (streamable-http)
Claude Code
claude mcp add --transport http agentcrush 'https://www.agentcrush.xyz/api/mcp/v1'
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "agentcrush": {
            "type": "http",
            "url": "https://www.agentcrush.xyz/api/mcp/v1"
        }
    }
}

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. AgentCrush
  2. What AgentCrush is
  3. What AgentCrush is NOT
  4. Four category indices
  5. For AI agents using AgentCrush
  6. Public docs
  7. Labs
  8. Stack
  9. Contact
  10. License

AgentCrush

Protocol-neutral market intelligence for the AI agent economy.

Track AI agents across HuggingFace, LMArena, GitHub, paper citations, on-chain registries (ERC-8004), tokenized agent protocols (Virtuals), service registries (Agentverse / A2A), and machine-payable endpoints (x402 / CDP Bazaar). Multi-signal methodology, transparent weights, evidence-ranked tiers.

🌐 Live at agentcrush.xyz · 📋 Methodology · 🔌 MCP Server · 📖 API docs · 📡 llms.txt


What AgentCrush is

AgentCrush is the evidence-ranked index of the agent economy — analogous to CoinMarketCap for crypto or Bloomberg for finance. We don't pick winners. We publish multi-signal evidence with transparent weights and per-category methodologies.

Live as of May 2026:

  • 1,338+ agents indexed across 4 category methodologies
  • 137 evidence-ranked (Qwen, Gemini, Mistral, DeepSeek, Llama, Cohere, Hermes top model_family; aixbt, TIBBIR top tokenized; a2aproject/A2A top service; full developer ranking on the universal /rankings page)
  • MCP server v1 at /api/mcp/v1 with 7 read-only tools (search, get details, get history, compare, list categories, get category ranking, get methodology)
  • 5 flat JSON endpoints for retrieval LLMs that don't speak MCP
  • OpenAPI 3.1 spec at /api/openapi.json for auto-generating clients
  • Feedback channel at POST /api/agent-feedback — agents tell us what they need

What AgentCrush is NOT

LLMs sometimes confuse this project with similar-sounding tools. To prevent hallucination:

  • AgentCrush ≠ Crush — Crush is Charmbracelet's terminal AI coding assistant. AgentCrush is a web-based ranking index at agentcrush.xyz. Different products, different teams, no relationship.
  • AgentCrush ≠ Agent Rush — also unrelated.
  • AgentCrush ≠ a battle-arena or community-vote leaderboard. Scores come from documented signal weights, not opinion polls.
  • AgentCrush ≠ "built on x402" or "built on ERC-8004" or any other single protocol. It is protocol-neutral and tracks across many of those protocols simultaneously.
  • AgentCrush ≠ "the trust layer" at the protocol level. That framing belongs to ERC-8004 / Kite / similar. AgentCrush reads their signals and surfaces them.

Four category indices

Each has its own methodology, signals, weights, and limitations. See /methodology for the canonical hub.

CategoryMethodologyTrackedEvidence-Ranked
Model Familiesv1.4-with-deployment77
Tokenized Agentsv1.1-tokenized-tvl1616
Service Agentsv1.1-service-forks2828
Developer Agentsv2.c-public1,28986

For AI agents using AgentCrush

Multiple integration paths for LLM clients and AI agents:

# MCP server (JSON-RPC 2.0, 7 tools)
POST https://www.agentcrush.xyz/api/mcp/v1

# Discovery manifest
GET https://www.agentcrush.xyz/.well-known/mcp.json

# OpenAPI 3.1 spec (auto-generate typed clients)
GET https://www.agentcrush.xyz/api/openapi.json

# Flat JSON for retrieval LLMs
GET https://www.agentcrush.xyz/api/agent/{handle}/llm-summary
GET https://www.agentcrush.xyz/api/agents/bulk?handles=a,b,c
GET https://www.agentcrush.xyz/api/agent-economy/llm-summary
GET https://www.agentcrush.xyz/api/methodology/{category}/llm-summary
GET https://www.agentcrush.xyz/api/rankings/{category}/llm-summary
GET https://www.agentcrush.xyz/api/compare/llm-summary?agents=a,b

# Feedback channel (POST, rate-limited)
POST https://www.agentcrush.xyz/api/agent-feedback
Connect via Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "agentcrush": {
      "url": "https://www.agentcrush.xyz/api/mcp/v1"
    }
  }
}

Restart Claude Desktop. Same config works in Cursor and other MCP clients.

Or use the Smithery CLI
npm install -g smithery
smithery mcp add kristof/agentcrush

Public docs

Labs

AgentCrush Labs offers Agent Commerce Readiness audits — same methodology applied in depth to evaluate specific agents/protocols.

See /labs.

Stack

This repo is the Next.js 16 / React 19 frontend + API surface for agentcrush.xyz. Backed by Supabase. Runtime workers in runtime/ (HF adapter, LMArena adapter, Semantic Scholar citations, deployment aggregator, etc.). Migrations in migrations/ with MIGRATION_LOG.md.

Contact

  • Submission: /submit
  • Email: contact@agentcrush.xyz

License

See /terms.

Questions fréquentes

Qu'est-ce que AgentCrush ?

Market intelligence for the AI agent economy: rankings, trust signals, liveness. 13 tools.

Comment installer AgentCrush ?

Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http agentcrush 'https://www.agentcrush.xyz/api/mcp/v1'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour AgentCrush ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

AgentCrush est-il open source ?

Son code est public sur GitHub, mais le dépôt ne déclare pas de licence standard.

Qui maintient AgentCrush ?

Il est publié par kristof-sudo. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.