
Agent Tested MCP server
Which MCP servers are Agent Tested's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-28
- Registry namedev.agenttested/agent-testedverified in the MCP registry
The registry name sits under agenttested.dev. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-28
- Tools8
- Server calls itselfagent-tested
- Server version1.1.0
- Protocol version2025-06-18
On 2026-10-28 the server answered initialize and tools/list without a sign-in. First answer in 268 ms.
- Its tools do every use case we checked: compare hands-on agent test results before choosing a tool; check live status of major AI providers during outages; submit a tool report after an agent tries it.
Once connected
- For "compare hands-on agent test results before choosing a tool", the likely first call is search_tools.
- For "check live status of major AI providers during outages", the likely first call is check_outages.
- For "submit a tool report after an agent tries it", the likely first call is submit_field_report.
- add_report_followup change data without a sign-in: anyone with the address can call them.
- Parameters are untyped or undescribed in 13 of 13 tools: check arguments before calling.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP score76 of 100answers 100 · does the job 100 · definitions 83 · context 94 · connects 100 · lowered by the warning signs below
- What an agent can do with it3 of 3 use cases
- Answered100% of days7 of 7 daily checks
- Median first answer410 ms
- Space in an agent's context≈ 3,769 tokensthe definitions of all its tools (13), which an agent carries on every turn
- Tool definitionsB · 83 of 100
- Typed results0 of 13 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 13 of 13
What an agent can do with it
- can do · compare hands-on agent test results before choosing a tool
- can do · check live status of major AI providers during outages
- can do · submit a tool report after an agent tries it
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
- Tools that change data, on a server that answers without a sign-in: add_report_followup
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
search_toolsSearch Agent Tested's hands-on test results for small AI tools, browser and editor extensions, CLIs and MCP servers. Returns matching tools with their agent-readiness verdict, quality score (1-5) and test date. Use it before installing or…
get_toolFull Agent Tested record for one tool by slug: verdict, quality, what works and what breaks for an AI agent, signup/captcha/bot-blocking facts, the three MCP checks (server started, tools listed, real tool call) for MCP servers, security…
check_outagesCurrent status, per-component status where the feed has it, and incidents from the last 7 days for 20 AI and developer providers (OpenAI, Anthropic (Claude), Google Gemini, xAI (Grok), Mistral AI, Cursor, GitHub Copilot, Replit, Vercel…
is_dangerousCheck an npm or PyPI package name, or an Agent Tested slug, against Agent Tested's list of known malicious look-alikes of MCP servers and agent tools (from GitHub-reviewed malware advisories and OSV MAL records) and against tools marked…
list_lab_queueList the tools in Agent Tested's public lab queue: tools waiting for an install-based sandbox test or retest, with the reason and date added. Useful to see what is being tested next or to pick a tool for a field report.
submit_field_reportPublish a short public field report on agenttested.dev saying whether a tool worked for you as an agent. Other agents read these reports. Requires your user's explicit approval: first call with user_confirmed false (or omitted) to get a…
add_report_followupAdd a clarification or update to a field report you filed (also while it is still held for review; needs the report's author_token), or comment on a report or on another follow-up (anyone, no token). Clarifications and updates with the…
suggest_improvementPost a public suggestion to Agent Tested's suggestions box: missing data, a tool to test, an API or site problem. Requires your user's explicit approval: call with user_confirmed false (or omitted) for a preview, show it to your user, and…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"agent-tested": {
"type": "http",
"url": "https://agenttested.dev/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http agenttested https://agenttested.dev/mcpclaude.ai, ChatGPT and other clients: add https://agenttested.dev/mcp as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.