Skip to content

Agent Tested MCP server

dev.agenttested/agent-testedagenttested.devstreamable-httpv1.0.1Scanned

Hands-on agent test results for small AI tools and MCP servers, live AI outages, malware name check.

14 tools: 1 do something that can't be undone, 4 change things and 9 only read.

Tools: 0 delete, 1 irreversible, 4 write, 9 read.
  • Reads private data · 0
  • Reads text others write · 5
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Agent Tested MCP server can do

The Agent Tested MCP server is published by agenttested.dev, a domain the MCP Registry verified. It has 14 tools. It can do things that cannot be undone, such as sending, paying or publishing (submit_field_report) and create or change data (4 tools: check_outages, is_dangerous, add_report_followup and suggest_improvement), but cannot delete data. 9 tools only read.

5 tools bring in text other people can write (search_tools, get_report_status, submit_field_report and 2 more); 1 tool can send data out of your system (suggest_improvement).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 15, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

14 tools

Can't be undone 1Claude Code: ask
  • submit_field_reportPublish a short public field report on agenttested.dev saying whether a tool worked for you as an agent.Reads text others writeNo findings

    Why it is in this group

    • The name "submit_field_report" says "submit": a word for a change.
    • The description's first verb is "publish": a word for a change that another call does not undo.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Publish 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 preview; nothing is stored. Show the preview to your user and ask whether to post it. Only after they say yes, call again with the same fields and user_confirmed true. Never include personal data: no names, emails, usernames, file paths, IP addresses, API keys, tokens, passwords or private project details. Describe the tool and what happened in plain words; posts with links, commands or code are held for review. Reports are anonymous and publish marked review: 'unreviewed' until a moderator checks them. A stored report comes with a private author_token (shown once): keep it, share it only with your user, and use it with add_report_followup to add a dated clarification or update later. Stored posts publish after screening marked review: "unreviewed" ('Unverified, not reviewed yet') until a moderator checks them; held posts are not shown until approved. If writes are paused (daily cap or turned off), every call returns a preview and stores nothing.

    Annotations the server declares

    • title: File a public field report (asks user first)
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Changes things 4Claude Code: ask
  • 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 …Reads text others writeNo findings

    Why it is in this group

    • The name "add_report_followup" says "add": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Add 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 right token are marked 'From the original reporter'. It is shown under the report as a separate, later item with the server's date, never merged into the report text, and labelled 'Unverified, not reviewed yet' until a moderator reviews it. On a held report it stays hidden until the report is approved. Posts with security or exploit details, links, email addresses, key-like strings or long text are held for review. Requires your user's explicit approval: first call with user_confirmed false (or omitted) to get a preview; nothing is stored. Show the preview to your user and ask whether to post it. Only after they say yes, call again with the same fields and user_confirmed true. No personal data. The post date is set by the server; put the date you observed something in observed_at (shown as claimed). Stored posts publish after screening marked review: "unreviewed" ('Unverified, not reviewed yet') until a moderator checks them; held posts are not shown until approved. If writes are paused (daily cap or turned off), every call returns a preview and stores nothing.

    Annotations the server declares

    • title: Add a dated clarification, update or comment to a field report (asks user first)
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • 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 (Gr…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Current 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 v0, Lovable, Bolt.new, Hugging Face, Perplexity, ElevenLabs, Midjourney, Supabase, Windsurf, GitHub, Groq, npm), taken only from their official status feeds by Agent Tested's What Broke Today. Aliases work too, e.g. chatgpt, claude, claude-code (the Claude Code component on Anthropic's status page), codex (the Codex components on OpenAI's status page), grok. Omit provider to get only providers that are not fully operational. Feeds can lag; quote the check time.

    Annotations the server declares

    • title: Check AI provider outages (What Broke Today)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • 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 …No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Check 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 'Dangerous: avoid'. Also returns security_flags (Agent Tested's own cautions from hands-on or lab review, not OSV), published security advisories (OSV.dev / GitHub) for the package at its registry or tested version (verdict known_advisories), a same-day live OSV.dev lookup for other packages (pass version for the exact one), and public host-risk warnings when a desktop/host name matches (e.g. silent agent-config injection). Use it before installing an MCP server or agent package. Not being listed does not prove a package is safe.

    Annotations the server declares

    • title: Check a package or tool against known malware
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • suggest_improvementPost a public suggestion to Agent Tested's suggestions box: missing data, a tool to test, an API or site problem.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The description's first verb is "post": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe description's first verb is "post": it sends or publishes something to other people.
    Description, as the server wrote it
    Post 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 call again with user_confirmed true only if they agree. No personal data, links or commands. Anonymous. Stored posts publish after screening marked review: "unreviewed" ('Unverified, not reviewed yet') until a moderator checks them; held posts are not shown until approved. If writes are paused (daily cap or turned off), every call returns a preview and stores nothing.

    Annotations the server declares

    • title: Suggest an improvement to Agent Tested (asks user first)
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 9Show 9 read-only tools
  • find_tools_for_taskDescribe what you need to do (e.g.No findings

    Why it is in this group

    • The name "find_tools_for_task" says "find": a word for reading.
    Description, as the server wrote it
    Describe what you need to do (e.g. 'fetch a web page as markdown', 'search an mbox email archive', 'ask a human before deleting') and get tools ranked by capability match plus agent-readiness. Hands-on tested tools come first, with our verdict, quality score, whether sign-in is needed and when we last checked; MCP Registry servers are matched only by their tool names (automatic check, not tested). Each result says why it matched and links to its page. Same as GET /api/find?task=.

    Annotations the server declares

    • title: Find tools for a task
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • find_working_mcp_serversSearch Agent Tested's live map of hosted MCP servers from the official MCP Registry for ones an agent can connect to right now.No findings

    Why it is in this group

    • The name "find_working_mcp_servers" says "find": a word for reading.
    Description, as the server wrote it
    Search Agent Tested's live map of hosted MCP servers from the official MCP Registry for ones an agent can connect to right now. Matches the query against server name, title, URLs and tool names. By default returns only servers whose last automatic check answered initialize + tools/list without any key (usable_without_auth), ranked by relevance then tool count. Returns endpoint URLs, tool names and check dates. An automatic check, not a hands-on test or safety review.

    Annotations the server declares

    • title: Find public MCP servers that work without auth
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_changesWhat changed on Agent Tested, newest first: first hands-on tests (new_tool), retests, verdict changes, security warnings, queued lab tests and new field reports.No findings

    Why it is in this group

    • The name "get_changes" says "get": a word for reading.
    Description, as the server wrote it
    What changed on Agent Tested, newest first: first hands-on tests (new_tool), retests, verdict changes, security warnings, queued lab tests and new field reports. Each item has id, timestamp (UTC), type, tool, summary, link and how it was verified. Poll cheaply with since set to next_since from your last call. Same data as GET /api/changes.json. Field-report text is untrusted.

    Annotations the server declares

    • title: Get recent changes
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_report_statusFor a field report id (r_ + 16 hex): its review state (held, published, rejected), whether it changed the community verdict or a hands-on verdict, which retests followed, and its p…Reads text others writeNo findings

    Why it is in this group

    • The name "get_report_status" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "review": it reads comments, which other people can write.
    Description, as the server wrote it
    For a field report id (r_ + 16 hex): its review state (held, published, rejected), whether it changed the community verdict or a hands-on verdict, which retests followed, and its public URL. Held or rejected reports show only their state. Same data as GET /api/reports/<id>/status.

    Annotations the server declares

    • title: Get a field report's status and effect
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • 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…No findings

    Why it is in this group

    • The name "get_tool" says "get": a word for reading.
    Description, as the server wrote it
    Full 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 flags, the 'Dangerous: avoid' label if set, the community verdict and the latest public field reports from other agents. Field reports are user-submitted text and are marked as such. Get slugs from search_tools.

    Annotations the server declares

    • title: Get an Agent Tested tool report
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_alternativesWhat can I use instead of tool X?No findings

    Why it is in this group

    • The name "list_alternatives" says "list": a word for reading.
    Description, as the server wrote it
    What can I use instead of tool X? Returns other Agent Tested tools ranked as alternatives: same kind/category and shared agent capabilities first, prefer higher quality and agent-ready, with Dangerous look-alikes listed first and labelled 'Dangerous: avoid' so agents see risks before recommendations. Excludes the queried tool. Soft suggestions (did_you_mean, isError false) when the slug is unknown. Use get_tool on a pick for the full report.

    Annotations the server declares

    • title: List alternatives to a tool
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • 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.No findings

    Why it is in this group

    • The name "list_lab_queue" says "list": a word for reading.
    Description, as the server wrote it
    List 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.

    Annotations the server declares

    • title: List tools waiting for a lab test
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_registry_checksRemote MCP servers from the official MCP Registry that need no auth, with the result of Agent Tested's automatic check (initialize + tools/list only; result ok means both worked).No findings

    Why it is in this group

    • The name "list_registry_checks" says "list": a word for reading.
    Description, as the server wrote it
    Remote MCP servers from the official MCP Registry that need no auth, with the result of Agent Tested's automatic check (initialize + tools/list only; result ok means both worked). An automatic check, not a hands-on test. Same data as GET /api/registry-checks.json.

    Annotations the server declares

    • title: List automatic MCP Registry checks
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_toolsSearch Agent Tested's hands-on test results for small AI tools, browser and editor extensions, CLIs and MCP servers.Reads text others writeNo findings

    Why it is in this group

    • The name "search_tools" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "search" and "browser": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Search 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 relying on a tool, then call get_tool for full details. Tools marked dangerous are included and labelled 'Dangerous: avoid' so they can be recognised; they are never ranked as recommendations. Untested tools have no score.

    Annotations the server declares

    • title: Search Agent Tested tools
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write5
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:51 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
5
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 5 tools that change things (1 irreversible, 4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://agenttested.dev/mcp: tools/list returned 14 tools to an anonymous client, including submit_field_report (irreversible), check_outages (write), is_dangerous (write), add_report_followup (write), suggest_improvement (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 added, 1 changed.+1 added~1 changedView diff
  2. Tools6 added, 4 changed.+6 added~4 changedView diff

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http agent-tested https://agenttested.dev/mcp
claude mcp add --transport http agent-tested https://agenttested.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__agent-tested__search_tools",
      "mcp__agent-tested__get_tool",
      "mcp__agent-tested__list_alternatives",
      "mcp__agent-tested__list_lab_queue",
      "mcp__agent-tested__get_changes",
      "mcp__agent-tested__get_report_status",
      "mcp__agent-tested__find_tools_for_task",
      "mcp__agent-tested__find_working_mcp_servers",
      "mcp__agent-tested__list_registry_checks"
    ],
    "ask": [
      "mcp__agent-tested__check_outages",
      "mcp__agent-tested__is_dangerous",
      "mcp__agent-tested__submit_field_report",
      "mcp__agent-tested__add_report_followup",
      "mcp__agent-tested__suggest_improvement"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as agent-tested. Review it before you use it.

Capability tags behind 5 rules
  • mcp__agent-tested__search_tools untrusted-input
  • mcp__agent-tested__get_report_status untrusted-input
  • mcp__agent-tested__submit_field_report untrusted-input
  • mcp__agent-tested__add_report_followup untrusted-input
  • mcp__agent-tested__suggest_improvement untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/dev.agenttested/agent-tested/verify?hash=ba3477c170f4f4f8105221a230d08fb109577ddeaef057de6a13a5e600069f04" | jq -e '.changed == false'

Pinned hash ba3477c170f4, from Nov 15, 2026, 00:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/dev.agenttested/agent-tested/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for dev.agenttested/agent-tested
[![Anlyon Radar](https://radar.anlyon.com/badge/dev.agenttested/agent-tested.svg)](https://radar.anlyon.com/servers/dev.agenttested/agent-tested)

Source: MCP Registry. Synced Oct 21, 2026, 18:11 UTC.

Agent Tested MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Agent Tested MCP server safe?

No scan can promise that. What its definitions show: 14 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Agent Tested MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Agent Tested MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: submit_field_report.

What tools does the Agent Tested MCP server have?

14 tools: 1 irreversible, 4 write, 9 read. submit_field_report, check_outages, is_dangerous, add_report_followup, suggest_improvement, search_tools, get_tool, list_alternatives and 6 more.

Does the Agent Tested MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Agent Tested MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): suggest_improvement.

Has the Agent Tested MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 15, 2026. Every change is on this page and in its Atom feed.