Agent Service Directory MCP Server

by agentservicedirectory Your server? Claim it

answering

Agent Service Directory is answering right now. Last checked 12 min ago. It exposes 9 tools.

A directory of agent services, with metrics.

Uptime history 9 days of history · worst day 21%

9 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

844 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 27

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 18 October 2026. No other catalogue keeps this.

25 Oct a tool changed the parameters it asks for2 times that day search_services

23 Oct a tool changed the parameters it asks for3 times that day search_services

22 Oct a tool changed the parameters it asks for2 times that day search_services

21 Oct a tool changed the parameters it asks for2 times that day search_services

20 Oct a tool changed the parameters it asks for5 times that day search_services

19 Oct 2 tools changed the parameters they ask for6 times that day get_tree, search_services

19 Oct a tool description was rewritten search_services

18 Oct 2 tools changed the parameters they ask for5 times that day get_tree, search_services

18 Oct a tool description was rewritten get_tree

and 16 more, back to 18 October 2026

Agent Service Directory does not always answer

Over the last week it answered 84.8% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

Settings → Connectors → Add custom connector, then paste this address

https://agentservicedirectory.com/mcp

~/.codex/config.toml

[mcp_servers.agent-service-directory]
url = "https://agentservicedirectory.com/mcp"

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 9

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

report

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.

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

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.

history

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.

send

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.

service

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).

services

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.

stats

get_stats

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

tree

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.

Endpoints

URL	Transport	State	Latency	Checked
https://agentservicedirectory.com/mcp	streamable-http	answering	548 ms	12 min ago

Alternatives to Agent Service Directory

same job, measured the same way

Servicegraph

by servicegraph-mcp

Datasets for founders: directories, newsletters, and agencies, with metrics attached.

answering

MCP Victoriametrics

by victoriametrics-community

MCP Server for VictoriaMetrics. Provides integration with VictoriaMetrics API and documentation

local only

MCP Victoriametrics

by victoriametrics

MCP Server for VictoriaMetrics. Provides integration with VictoriaMetrics API and documentation

local only

Monitoring

by pingvera

Client-website monitoring for agencies: uptime, incidents, SSL/domain expiry, server metrics.

answering

MCP Vmanomaly

by victoriametrics

MCP Server for vmanomaly - VictoriaMetrics anomaly detection

local only

MCP Vmanomaly

by victoriametrics-community

MCP Server for vmanomaly - VictoriaMetrics anomaly detection

local only

Infrly

by getinfrly

Read-only access to your Infrly services, deploys, logs, metrics and billing.

answering

Ecosystem Monitor

by memoryapi

Ecosystem monitoring: service status and x402 activity metrics

2 tools answering

Agent Service Directory — questions

Answers built from our own checks of this server.

What can Agent Service Directory do?

It exposes 9 tools, read directly from the server on our last check. Among them: get_changes, get_history, get_report, get_service, get_stats, get_tree and 3 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Agent Service Directory working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 844 ms. The bar chart above shows every period we have measured.

How do I connect Agent Service Directory?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Agent Service Directory need an API key?

No. Agent Service Directory completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 9 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Agent Service Directory?

It answers our handshake in 844 ms on average, which is faster than 10% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.