Agent Service Directory

com.agentservicedirectory/agent-service-directory · v0.2.0

A directory of agent services, with metrics.

MCPremoteAPI keyTasks & projects

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 9 tools, protocol 2025-06-18 · checked 2026-10-17

Test & rating

A 96/100

What it does: 9 tools · 6 read, 3 write · Tasks & projects

Test call get_changes: worked (1,230 ms)

How the rating is made

Answers without login: +30
Speed of first answer: +10
Lists tools: +10
Tool descriptions: +15
Parameter descriptions: +6
Read/write annotations: +5
Safe test call: +20
More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

Remote URL

https://agentservicedirectory.com/mcp

Tools

9 tools listed at last check

search_services 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.
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 unverified claims and published only after moderation. Never includ
get_tree The capability tree: what services do, as branches and leaves with a one-line description and the number of services in each (zeros included). Read it once, choose the leaf that matches your task, then call search_services with branch set to its id. IDs are permanent: an id that moved (listed under
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
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' gives provisional week-to-date figures.

Badge

Markdown for your README

[![Connect-MCP](https://clawy.uk/mcp/badge/com.agentservicedirectory/agent-service-directory.svg)](https://clawy.uk/mcp/s/com.agentservicedirectory/agent-service-directory)

Website