Official MCP RegistryListed
Agent Service Directory
A directory of agent services, with metrics.
First seen 17 Oct 2026. Evidence as of 23 Oct 2026.
9
Tools
From an anonymous probe
1
Source listings
Each with its own history
11
Recorded changes
Since first seen
Tools
| Tool | Description | Behaviour |
|---|---|---|
| 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. | Read-only |
| 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. | Read-only |
| 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' gives provisional week-to-date figures. | Read-only |
| 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). | Changes data |
| get_stats | How many services we track and how many checks ran in the last 24 hours. | Read-only |
| 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 matches your task, then call search_services with branch set to its id, or up to three ids separated by commas when more than one fits. format "text" returns the same tree as plain text, one line per node: the cheapest to read. Keep it and pass since_revision later to get only what changed. IDs are permanent: an id that moved (listed under moved) still works as a branch filter. | Read-only |
| 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 unverified claims and published only after moderation. Never include task data, secrets or personal information. | Changes data |
| 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 (query) or by capability tree node (branch); filter on type, access (none_asked, payment, credentials), max_price_usd and the evidence (passing, min_pass_rate); then call get_service for connection details. Results are compact; use limit/offset to page. | Read-only |
| 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 messages are not. Never include task data, secrets or personal information. | Changes data |
Change history
- search_services: input schema changed
- search_services: input schema changed (+currency)
- search_services: input schema changed
- search_services: input schema changed (+access, +max_median_ms, +max_p95_ms, +payment_model)
- search_services: description changed (+"services an agent can use, by what they do: remote MCP servers (with the tools each lists), local MCP servers (packages), pay-per-call" +"(x402, MPP), A2A agents" +"marketplaces,")
- get_tree: input schema changed
- server instructions changed (+"What is here: remote MCP servers (checked with the MCP handshake; the tools each lists), local MCP servers (npm and PyPI packages), pay-per-call APIs (x402 and MPP; checked with an unpaid request), A2A agents and task marketplaces, from public registries and our own listings, each placed in a capability tree by what it does." +"A passing check on a remote MCP server means it completed the MCP handshake with us (initialize and tools/list) or asked for credentials first; tools lists the tool names it reported. It does NOT show that its tools work. - access says what our plain request was asked for (payment, credentials, or nothing) and what the service's agent card or registry entry states. -")
- search_services: input schema changed (+branch, +provider, +scope)
- get_tree: tool added
- server instructions changed (+"get_tree to see what services do (format "text" is the cheapest to read; keep it and pass since_revision later), then" +"with branch set" +"the most specific node id")
- Listed (registry)
| Source | Listing | First seen | Last seen | Versions |
|---|---|---|---|---|
| Official MCP Registry | com.agentservicedirectory/agent-service-directory | 17 Oct 2026 | 23 Oct 2026 | 1 |