Agent Service Directory
REMOTE · AGENTSERVICEDIRECTORY.COM
A directory of agent services, with metrics.
Available components
Last scanned (6 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Search and Retrieval
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1848 tokens (~205/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 79% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_feedback" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 173 → 205 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- New tool “get_tree” functional
- “search_services” added an optional parameter “branch” cosmetic
- “search_services” added an optional parameter “provider” cosmetic
- “search_services” added an optional parameter “scope” cosmetic
- “search_services” reworded the description of “one_per_provider” cosmetic
- “search_services” reworded the description of “query” cosmetic
- 17 Oct 26 56
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 18 Oct 2026 · Probed https://agentservicedirectory.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agentservicedirectory.com | CN=WE1,O=Google Trust Services,C=US | 17 Oct 2026 | 15 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | fbb30c765f0ec8c60e27cbeb8b9ac9b7 |
| SANs: agentservicedirectory.com, www.agentservicedirectory.com, *.www.agentservicedirectory.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of agentservicedirectory.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| agentservicedirectory.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agentservicedirectory.com/mcp | Verified | 200 | |
| http (plaintext) | http://agentservicedirectory.com/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_changes Get detected changes ~60
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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Default 7. |
| id | string | – | Limit to one service. |
No output schema declared.
No examples provided.
get_history Get check history ~68
Individual check results for a service over the last days, newest first. Use it to see patterns (intermittent failures, slowdowns) behind the summary figures.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Default 7. |
| id | string | yes | – |
| limit | integer | – | Default 50. |
No output schema declared.
No examples provided.
get_report Get a weekly report ~92
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Report id (the Monday that starts the week, e.g. '2026-10-19'), or 'current'. |
No output schema declared.
No examples provided.
get_service Get service ~67
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).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | A service id from search_services, e.g. 'svc_...' or 'cand_...'. |
No output schema declared.
No examples provided.
get_stats Get coverage statistics ~25
How many services we track and how many checks ran in the last 24 hours.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_tree Get the capability tree ~210
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.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | json (default) or text: one line per node, about half the size of json. |
| since_revision | integer | – | The revision of a copy you hold: returns only the node changes since then (or unchanged: true) instead of the tree. Service counts are refreshed every five minutes and are not changes. |
No output schema declared.
No examples provided.
report_outcome Report outcome ~188
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.
| Name | Type | Req | Description |
|---|---|---|---|
| failure_kind | string | – | – |
| idempotency_key | string | yes | Unique per report; retries with the same key are not counted twice. |
| operation | string | – | Which operation, e.g. 'GET /v1/search'. |
| outcome | string | yes | – |
| referral_id | string | – | From get_service. Preferred. |
| service_id | string | – | If you have no referral_id. |
| task_category | string | – | Broad category only, e.g. 'web-search'. No task content. |
No output schema declared.
No examples provided.
search_services Search services ~554
Find payable APIs and agent task marketplaces by purpose, with evidence for each. Filter on the evidence (passing, min_pass_rate, max_price_usd) and pick one; then call get_service for connection details. Results are compact; use limit/offset to page.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | Capability tree id from get_tree, e.g. 'messaging/email/validation', 'places/weather' or 'places' (a node includes everything under it), or 'other'. Up to three ids separated by commas list services… |
| limit | integer | – | Default 10, maximum 25. |
| max_price_usd | number | – | Maximum price per call in USD stablecoin, where the price is known. |
| max_terms_changes_90d | integer | – | Only services whose observed x402 payment terms changed at most this many times in the last 90 days (0 = unchanged). Short histories are labelled limited. |
| min_checks | integer | – | Minimum checks in the last 30 days, to avoid judging on one check. |
| min_pass_rate | number | – | Share of checks passed in the last 30 days, 0 to 1. |
| min_payers | integer | – | Minimum unique payers in 30 days, as reported by the registry. |
| network | string | – | Payment network, e.g. 'eip155:8453' (Base) or 'solana'. |
| offset | integer | – | – |
| one_per_provider | boolean | – | Return one endpoint per provider (registrable domain): the first under the chosen sort (by default, the most scheduled checks passed in the 30-day window). |
| passing | boolean | – | true: latest check passed. |
| provider | string | – | Only endpoints from this provider (registrable domain, e.g. 'example.com'), as given in a result's provider field. |
| query | string | – | Text search over names, hosts, URLs and operator names, and the name of a service's place in the capability tree when that place passed our three placement checks. Every word must match (up to five w… |
| scope | string | – | directory (default): services that meet the listing criteria (https://agentservicedirectory.com/methodology#directory); index: everything we watch. |
| sort | string | – | – |
| tag | string | – | Purpose tag, e.g. 'web-search'. |
| tier | string | – | – |
| type | string | – | – |
No output schema declared.
No examples provided.
send_feedback Send feedback ~144
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.
| Name | Type | Req | Description |
|---|---|---|---|
| about | string | – | A service id, host, or the kind of service, e.g. 'marine weather forecasts'. |
| contact | string | – | Only if you want a reply. |
| kind | string | yes | – |
| note | string | – | What you needed or what is wrong, in a sentence or two. |
No output schema declared.
No examples provided.
How do I install the Agent Service Directory MCP server?
Agent Service Directory is a hosted endpoint at https://agentservicedirectory.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · agentservicedirectory.com
claude mcp add --transport http com-agentservicedirectory-agent-service-director 'https://agentservicedirectory.com/mcp'
What is the Agent Service Directory MCP server?
Agent Service Directory is an MCP server listed in the public MCP registry as com.agentservicedirectory/agent-service-directory. A directory of agent services, with metrics. This page covers its hosted endpoint (https://agentservicedirectory.com/mcp).
Is the Agent Service Directory MCP server safe to use?
Agent Service Directory scores 56 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Agent Service Directory MCP server expose?
Agent Service Directory exposes 9 tools: search_services, get_service, get_history, get_changes, report_outcome, and 4 more. Their descriptions and schemas cost roughly 1,408 tokens of context every time the server is loaded.
Does the Agent Service Directory MCP server require authentication?
No. We connected to Agent Service Directory without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Agent Service Directory MCP server still maintained?
Agent Service Directory is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.