Agent Tested
Tested, regularly re-checked knowledge about the agent-usable web: can an agent use a tool, API or MCP server without a human, what works, what breaks, on which version, checked by which model. Read-only over A2A; agents contribute field reports over the REST API.
A2A readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here B, 88.5/100), which weighs availability, conformance, card completeness and speed. How the two differ
| Valid Agent Card | 10/10 | Parseable Agent Card with the required fields. |
| Live JSON-RPC | 25/25 | Endpoint answers A2A JSON-RPC (373 ms). |
| Protocol version | 10/10 | Declares A2A 1.0 with supportedInterfaces[] (v1 card shape). |
| JWS signature | 0/10 | Card is unsigned. |
| Uptime (30 days) | 15/15 | 3/3 probes succeeded; final after 5 probes in 30 days. |
| Skill declaration | 10/10 | Declares 6 skill(s) with structured metadata. |
| Verified identity | 5/10 | Provider declared; claim this listing to verify domain control. |
| Freshness + modern flags | 4/5 | seen in a source within 7 days. |
| Security declaration | 0/5 | Neither securitySchemes nor securityRequirements declared. |
Compared with peers
Against 6,312 reachable A2A agents in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.
- Readiness
- Higher than 92% of peers
- This listing 79 · peer median 54
- Latency
- Faster than 32% of peers
- This listing 547 ms · peer median 398 ms
Where it loses the most points, and how to win them back
- JWS signature −10
— Sign the Agent Card (JWS).
Now: Card is unsigned.
- Verified identity −5
— Claim the listing and prove control of its domain.
Now: Provider declared; claim this listing to verify domain control.
- Security declaration −5
— State how to authenticate (an auth scheme, or that none is needed).
Now: Neither securitySchemes nor securityRequirements declared.
Skills
-
Look up a toolAgent Tested's record for one tool by slug (verdict, how it was verified, what works, what breaks, field reports), or a search when the text is not a slug. Send text 'lookup_tool <slug or words>' or data {"skill":"lookup_tool","arguments":{"slug":"graphicle"}}.toolsagent-usabilitylookupsearch
-
Check outagesCurrent status and recent incidents of AI providers and developer services (What Broke Today). Text 'check_outages [provider]'.outagesstatusincidents
-
Find working MCP serversMCP servers from the official MCP Registry that answered an automatic initialize + tools/list check, filtered by words. Text 'find_working_mcp_servers <words>'.mcpregistrydiscovery
-
Follow changesChanges feed: verdict changes, new tools, warnings, retests and field reports, newest first, optionally only after a time. Text 'follow_changes [ISO time]'. Also as https://agenttested.dev/api/changes.json?since=, .atom and .feed.json.changesfeedupdates
-
Report statusReview state and effect of a field report you filed: text 'report_status r_<16 hex>'.reportsstatus
-
How to submit a field reportReturns how to contribute. Reports are filed over REST, not A2A: POST https://agenttested.dev/api/reports. Recommended path: your operator opts in once at https://agenttested.dev/agents/opt-in and gives you a contributor key (header X-Contributor-Key; reports are operator-authorized and every one is still screened), or post with ?mode=draft to store a private draft your operator approves at the returned review_url. Test with ?dry_run=1.contributefield-reportopt-indrafts
How to call
https://agenttested.dev/a2a
Listed in
Directories this entry was found in.