com.agentdrives/directory·Dev tools

AgentDrives

Can an AI agent use this software? Levels from real agent test drives: sign-up, keys, use, pay.

Stars
—
Version
1.4.0
License
—
Review
Passed
Registry update
Oct 16, 2026

Connect

remote
Terminal
$claude mcp add --transport http directory https://agentdrives.com/api/mcp

Also served over: streamable-http https://agentdrives.com/mcp

Headers

Nothing to configure — it works as is.

Security review

Review passed

Reviewed 1h ago.

tools
4 tools scanned
metadata
scanned

No findings.

Tools

4
  • find_tools_for_task

    Which software can your agent use for a job, from AgentDrives's test drives: say the task in plain words (e.g. 'send an invoice', 'scrape a web page', 'add a contact to a CRM') and get the products ranked for it. Each result: the agent level (0-5: 0 Read-only, 1 Needs a person, 2 Gets in, 3 Does the work, 4 Runs on its own, 5 Autonomous); gets_in_alone (our agent signed up and got a key without a person); task: the closest task in the product's capability map and what happened when our agent tried it (result: done, partial, plan_gated, failed, blocked, not_tried, unknown; via: the route, e.g. api, mcp, cli, browser); match (strong or partial); can_do (up to three things our agent did there); stop (where it stopped, and why); work_done (share of the core tasks done, 0-100); the drive date; origin (editorial, or owner with disclosure "Owner-paid drive"); and the page URL. Order: strong matches first, then the ones where our agent did the task, then level, then work done. self_signup: tru

  • search_tools

    Find software an AI agent can really use, from AgentDrives's directory of products test-driven by an AI agent: use it before you pick a tool for a task or ask a person to sign up for one. Filter by category, minimum agent level (0-5: 0 Read-only, 1 Needs a person, 2 Gets in, 3 Does the work, 4 Runs on its own, 5 Autonomous), how an agent gets in (access: pay per call, no key, a key by API, its own sign-up…), agent-native payment (proven, or the rails it offers) and whether an agent leaves on its own. Returns the level and its name, how an agent gets in (access) and the five outcomes (find, access, use, pay, leave: each yes, part, no, unreached or na), the part scores (holds_up, docs_match, setup: 0-100, null = not measured), where it stopped, the agent-native ways to pay it offers (pays_with) and whether our side proved a payment (paid), the bot check that stopped our agent on a way in (it may have got in another way) and its wall_type (network: It judged where our agent connects from

  • get_tool

    One product's full test-drive result, for when you need to know exactly how far an agent gets with it and where it stops (search_tools gives the slug; an unknown slug is an error that says how to find one): the agent level, the five outcomes (find, access, use, pay, leave, by any way in the product offers; stages: the four that decide the level, under their older keys), how an agent gets in (access, with the core tasks done on each way), the part scores, the nine checkpoints in the order of the agent's eight steps (Find: none, it is the Agent-ready setup; Learn: docs; Sign up: sign-up, verify; Get a key: key, first call; Do the work: first action; Pay: pay; Cancel: cancel; Leave: delete), what an agent can and cannot do, tips for agents, pay_options (the ways to pay it offers an agent, the payment our side proved with its transaction, and what the owner could add), the bot check that stopped our agent on a way in, even where it got in another way (agent_check: vendor, step, type networ

  • list_categories

    Every category in the directory: its id (for search_tools' category filter), its name, the number of products driven in it and the best agent level in it (0-5). Use it to see where agents get furthest, or to find the id before a search.

More in Dev tools

Listing from the official MCP Registry.