Skip to content
Agent Service Directory logo

Agent Service Directory MCP server

Which MCP servers are Agent Service Directory's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-28

← Back to Agent Service Directory

Whose server it is
  • Registry namecom.agentservicedirectory/agent-service-directoryverified in the MCP registry

The registry name sits under agentservicedirectory.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-28
  • Stateanswerschecked 2026-10-28
  • Tools9
  • Server calls itselfagent-service-directory
  • Server version0.1.0
  • Protocol version2025-06-18

On 2026-10-28 the server answered initialize and tools/list without a sign-in. First answer in 164 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 5 of the 7 days it takes to judge reliability.

Once connected

  • For "Find paid APIs with measured uptime and stated prices", the likely first call is search_services.
  • send_feedback change data without a sign-in: anyone with the address can call them.
  • Parameters are untyped or undescribed in 4 of 9 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 5, the first on 2026-10-28
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 5 so far
  • Answeredmeasuring5 of the 7 daily checks it takes to print a share
  • Median first answer471 ms
  • Space in an agent's context≈ 4,651 tokensthe definitions of all its tools (9), which an agent carries on every turn
  • Tool definitionsA · 93 of 100
  • Typed results0 of 9 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 4 of 9

What an agent can do with it

  • can do · Find paid APIs with measured uptime and stated prices
  • not sure · Check whether an MCP server responds as expected
  • not sure · Compare x402 and MPP payment terms across services

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

  • Tools that change data, on a server that answers without a sign-in: send_feedback

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers9 tools · read 2026-10-28
  • search_services

    Find services an agent can use, by what they do: remote MCP servers (with the tools each lists), local MCP servers (packages), pay-per-call APIs (x402, MPP), A2A agents and task marketplaces, with our checks for each. Search by words…

  • get_service

    Full evidence and connection details for one service, plus a referral_id. Use the referral_id with report_outcome after you use the service (valid 7 days).

  • get_history

    Individual check results for a service over the last days, newest first. Use it to see patterns (intermittent failures, slowdowns) behind the summary figures.

  • get_changes

    Recently detected changes to monitored documentation and API schemas, across all reviewed services or for one. A detected change is pending interpretation, not necessarily a breaking change.

  • report_outcome

    After using a service, report whether it worked. Requires a free API key (Authorization: Bearer asd_...; get one with POST https://agentservicedirectory.com/api/v1/keys). Quote the referral_id from get_service. Reports are stored as…

  • get_tree

    The capability tree: what services do, as branches, leaves and leaves' children, each with a one-line description and the number of services in it (zeros included). Read it once (follow its guide), choose the most specific node that…

  • send_feedback

    Tell us what is missing or wrong: a service or kind of service we don't list, a metric you need, a feature, wrong data or unclear docs. No key needed. We use it to decide where to look next; counts by kind are public on the roadmap, the…

  • get_stats

    How many services we track and how many checks ran in the last 24 hours.

  • get_report

    The weekly State of Agent Services report: coverage, probe results, payment networks, prices and purpose tags across everything we track. Counts and distributions only, with their method. Omit id for the latest published report; 'current'…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "agent-service-directory": {
      "type": "http",
      "url": "https://agentservicedirectory.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http agentservicedirectory https://agentservicedirectory.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://agentservicedirectory.com/mcp as a custom connector in the settings.

OpenAPI spec

15 paths, read 2026-10-28. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.