Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AgentDrives

REMOTE · AGENTDRIVES.COM · 2 COMPONENTS

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

67 Trust /100

Last scanned (8 minutes ago)

Scores higher than 57% of remote servers

Reachable. Last reached 18 Oct 2026.

Category Search and Retrieval

Trust breakdown (7 categories)

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 Security69
Transport & Reachability100
Schema Quality & AI Usability56
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1743 tokens (~435/item across 4 items; 4 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 Management7
  • Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
Changelog

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 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Oct 26 0
    • Tool “search_tools” rewrote its description, which is the text the model reads security
    • Tool “find_tools_for_task” rewrote its description, which is the text the model reads security
    • Tool “get_tool” rewrote its description, which is the text the model reads security
    • Tool “list_categories” rewrote its description, which is the text the model reads security
    • Stability: unverified → 0.03 ▲ functional
    • Schema quality: excellent → good functional
    • “find_tools_for_task” reworded the description of “task” cosmetic
  • 16 Oct 26 66

    First indexed and scored.

Diagnostics

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://agentdrives.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=agentdrives.com CN=YE2,O=Let's Encrypt,C=US 1 Oct 2026 30 Dec 2026 ECDSA 256 ECDSA-SHA384 6cf5afc23438d7c583d088ce3dda13e9913
SANs: *.agentdrives.com, agentdrives.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of agentdrives.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
agentdrives.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
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self'; connect-src 'self'; img-src 'self' data: blob: https://*.googleusercontent.com; style-src 'self' 'unsafe-inline'; font-src 'self'; media-src 'self'; frame-src 'self' https://www.youtube-nocookie.com; frame-ancestors 'self'; form-action 'self'; base-uri 'none'; object-src 'none'; report-uri /api/csp-report
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy accelerometer=(), autoplay=(self), camera=(), display-capture=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), midi=(), payment=(), usb=(), browsing-topics=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://agentdrives.com/api/mcp Verified 200
http (plaintext) http://agentdrives.com/api/mcp Served over HTTP 200
MCP tools · 4 exposed · ~1,618 tokens

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 →

Tool Tokens
find_tools_for_task ~409

Ranks the products AgentDrives has test-driven for a task given in plain words (e.g. 'send an invoice', 'scrape a web page', 'add a contact to a CRM'). 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: true keeps only products our agent got into on its own. Up to limit results (default 10, at most 25); nothing matches: an empty list. get_tool returns one product in full.

NameTypeReqDescription
categorystring–Only this category: an id or name from list_categories (e.g. 'invoicing')
limitinteger–the most results to return
min_levelinteger–only products at this agent level or higher (0-5)
self_signupboolean–true: only products our agent signed up for and got a key on its own
taskstringyesThe task in plain words, e.g. 'send an invoice' or 'create a contact'

No output schema declared.

No examples provided.

get_tool ~474

Returns one product's full test-drive result: 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 network or challenge, the owner's fix), after_wall: what the agent did on its own once a person cleared one step at the door (never part of the level), works_assisted (the core tasks done once a person set up the account; null: not measured yet), robots (a robots.txt rule on the way in: named, the product's wall, or star, a rule for crawlers; held: the level is from the last drive past it), same_level_drives of drives, the level history with why each move happened (product, rules, noise), rules_date: the date of the rules the level was set by. From the rules of 12 Oct 2026 on: routes (every way in it offers and what happened on each, tried agent-native first), checkout (how far the walk to the last click went and what the checkout showed), docs (its docs read and judged) and claims (the documented ways to do the core work, tried once each: held, broken, worked but undocumented).

NameTypeReqDescription
slugstringyesThe product's directory slug, from search_tools (e.g. 'attio')

No output schema declared.

No examples provided.

list_categories ~47

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_tools ~688

Searches AgentDrives' tested products by name, domain or what they do, and returns each one's agent level and evidence. Filters: 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 and its browser, not a person. An agent that works on its own from a data center doesn't get through unless the owner lets signed agents in. How agents in a person's own browser fare isn't measured yet. challenge: It asks every visitor to prove they are human. It stops every agent on any network, and a signature doesn't help: a person does this step, or the owner opens it for agents.), who paid for the drive (origin: editorial, or owner with disclosure "Owner-paid drive") and the page URL. Sorted by level, then work done, then minutes to the first call. Up to limit results (default 25, at most 100); none match: an empty list. get_tool returns one product's full result by a slug from here; list_categories gives the category ids.

NameTypeReqDescription
accessstring–only products an agent gets into this way: keyless (no key needed), local (runs locally), try_first (try first, claim later), pay_per_call, key_by_api, mcp_signin, email_signup, browser_signup, by_na…
agent_can_buyboolean–only products an agent paid through an agent-native rail, proven from our side
agent_can_leaveboolean–only products an agent leaves on its own
categorystring–A category id or name from list_categories (e.g. 'crm'); an unknown one is an error that says so
limitinteger–the most results to return
min_levelinteger–only products at this agent level or higher (0-5)
pays_withstring–only products that offer this agent-native way to pay (seen or paid), e.g. x402, mpp, l402, stripe-projects, acp, ucp, ap2, mcp-payment
querystring–Name, domain or what the tool does, e.g. 'invoicing', 'stripe.com' or 'postgres'; every word must match (the same search as the directory page)

No output schema declared.

No examples provided.

Install

How do I install the AgentDrives MCP server?

AgentDrives is a hosted endpoint at https://agentdrives.com/api/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 · agentdrives.com

# add to Claude Code
claude mcp add --transport http com-agentdrives-directory 'https://agentdrives.com/api/mcp'
Common questions

What is the AgentDrives MCP server?

AgentDrives is an MCP server listed in the public MCP registry as com.agentdrives/directory. Can an AI agent use this software? Levels from real agent test drives: sign-up, keys, use, pay. This page covers its hosted endpoint (https://agentdrives.com/api/mcp).

Is the AgentDrives MCP server safe to use?

AgentDrives scores 67 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 AgentDrives MCP server expose?

AgentDrives exposes 4 tools: find_tools_for_task, search_tools, get_tool, list_categories. Their descriptions and schemas cost roughly 1,618 tokens of context every time the server is loaded.

Does the AgentDrives MCP server require authentication?

No. We connected to AgentDrives without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the AgentDrives MCP server still maintained?

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