Remote MCP server to run your Atako AI agents: chat, projects, files, integrations and channels.
- Passed: Handshake
- Passed: Tools listed
- Passed: Updated recently
Median latency 132 ms · Last checked
Explore
Evidence for your next connection.
Independent measurements of remote MCP servers. Every observation has a timestamp.
Read-only probesMCP server · Code & DevOps
Use when choosing a SaaS, API or provider for a task: how far our agent got in each, sign-up to pay.
1 failed · 8 not measured
Median of successful probes over 7 days
Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.
Tool definitions returned by this server
Independent monitoring
Responded
The server completed its last measured handshake. This is an observation, not a guarantee.
Last checked| Test area | Passed | Failed | Unmeasured |
|---|---|---|---|
ConnectionCan a client connect and discover tools? | 5 | 0 | 0 |
Reliability & speedDoes it respond consistently and quickly? | 0 | 0 | 4 |
Access & authenticationWhat is required to use this server? | 1 | 0 | 2 |
Tool qualityAre the tool definitions usable by an agent? | 4 | 0 | 0 |
Publisher identityCan the publisher be traced to its source? | 3 | 1 | 2 |
Unmeasured means there is not enough evidence to decide. How these checks work
Start using AgentDrives: choose a tool, API or provider
Choose your client, copy the configuration, then enable the server in your client’s MCP settings.
Run this command in your terminal, then restart Claude Code.
Claude Code
claude mcp add --transport http agentdrives-choose-a-tool-api-or-provider https://agentdrives.com/api/mcpCapabilities
Use when you or the user must choose a tool, API or provider for a task (send email, take payments, host a database…): send the task in a few plain words ('send an invoice') with filters if they matter. Returns the products our agent drove for it, ranked by how far an agent got on its own (sign-up, key, the work, paying), each with what happened and its sign-up, docs and MCP links. Read-only, no key needed; 5 by default, up to 25; a product by name: search_tools.
DiscoveredUse when you or the user are deciding between 2 or 3 products for one task ('Stripe or Paddle?'): send their slugs (from search_tools), names or domains, and the task in a few plain words. For each: driven or only listed, agent level (0-5), how far our agent got at each step and where it stopped, what it did on the task, how to connect (MCP, API, CLI), the date and its page; a name we don't cover comes back in not_covered. Read-only, no key needed.
DiscoveredUse when you picked a product and need to wire it up: its API, MCP server, CLI, SDK, docs and payment, each tested, documented, none_found or unknown, with the product's own URL for it and the date we saw it. The whole drive result: get_provider. Read-only, no key needed; about 1 KB.
DiscoveredUse when you know the category and want a shortlist: its name, how many products AgentDrives drove in it, the best agent level (0-5) and its top 10 by level, each with its drive date and page. The rest: search_tools with the same category. Read-only, no key needed.
DiscoveredUse when you are about to use or recommend a product and need to know if an agent can work it on its own: send its slug from search_tools, or its name or domain. Returns its drive result: agent level (0-5), where our agent stopped, what it can and can't do, how it gets in and pays; only its API, MCP and CLI: get_agent_surfaces. Read-only, no key needed; the headline unless brief is false.
DiscoveredUse when asked "which provider works best for X?" in a category: its driven products ranked by agent level (0-5), each with where our agent stopped, and how many we drove in it; under 5, not enough drives yet. Then get_provider for one product. Read-only, no key needed.
DiscoveredUse when you need a valid category id for choose_provider_for_task, search_tools or get_category: every category with its id, name, number of products and best agent level (0-5). Read-only, no key needed; no arguments.
DiscoveredUse when you need to know whether a product you picked still works as it did, or what moved lately: with a slug, every dated change at that product (level, surfaces, price and plan, each with its source); without, the level moves of the last days, newest first, with the cause and the level now. Its full drive result: get_provider. Read-only, no key needed; narrow it with days or category.
DiscoveredUse when you have a product's name, domain or kind in mind: send a short query ('stripe.com', 'postgres', 'invoicing') with filters for category, agent level, access or payment. Returns the products we drove, sorted by agent level (0-5), each with where our agent stopped; a task in plain words: choose_provider_for_task, one product in full: get_provider. Read-only, no key needed; up to 100 a page.
DiscoveredRecent measurements
| Checked | Result | Response | Tools |
|---|---|---|---|
| Connected | 285 ms | 9 |