mcpbeat Sign in

Agent Conversion — AI Website Conversion Testing MCP Server

not responding

Agent Conversion — AI Website Conversion Testing is listed as active in the registry but did not answer our last check. It exposes 2 tools.

Test whether AI agents complete SaaS pricing, signup or sales journeys; get evidence-backed reports.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 20 days of history · worst day 20%
20 days agonow
51.1%
Uptime 24h
47 of 92 checks
2
Tools
read from the server
256 ms
Response time
average over 24h
open, no key
Access
streamable-http

Agent Conversion — AI Website Conversion Testing does not always answer

Over the last week it answered 44.1% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

run in your terminal
claude mcp add agent-conversion --transport http https://agent-conversion-coral.vercel.app/api/mcp
Settings → Connectors → Add custom connector, then paste this address
https://agent-conversion-coral.vercel.app/api/mcp
~/.codex/config.toml
[mcp_servers.agent-conversion]
url = "https://agent-conversion-coral.vercel.app/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "agent-conversion": {
      "url": "https://agent-conversion-coral.vercel.app/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "agent-conversion": {
      "type": "http",
      "url": "https://agent-conversion-coral.vercel.app/api/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

conversion
get_conversion_report
Get the status and, once finished, the result of an audit started with test_conversion. Pass the audit_id returned by test_conversion (a report URL also works). status is "pending" while the agent is still running: wait retry_after_seconds and call again. If stale is true, the audit will never finish; start a new one. When status is "completed", result contains: task_completed (did the agent reach the goal), score (0-100 Agent Conversion Score, or null when score_withheld because the run did not finish measuring), summary, successes, frictions and recommendations; evidence.steps lists what the agent did. failure_classification explains a non-clean run: "blocked" (safety boundary or site-side access refusal such as a bot challenge — a real finding about the site), "run_did_not_finish", "infrastructure_failure" or "pipeline_error" (Agent Conversion's own problem, not the site's). report_url is a human-readable report to share. status "failed" means no report will be produced. Calling this tool is free and safe to repeat.
test
test_conversion
Start a real Agent Conversion audit: an autonomous browsing agent opens the given website and tries to complete the task, then the run is scored 0-100 with problems and recommendations. Use this when someone wants to know whether an AI agent can find something or complete a commercial step on a specific website, e.g. "Can an agent find the Pro plan's monthly price on example.com?" or "Can an agent start the self-service signup on example.com?". Returns immediately with an audit_id and status "pending" — it does NOT wait for the result. Call get_conversion_report with the audit_id to get the result. Rules: url must be a public http(s) URL (no localhost, private IPs, credentials or custom ports). task must be 10-1000 characters and describe the goal in plain language; phrase purchase-like goals as "reach checkout without buying". Each call costs a real browser run and is rate limited: do not call it repeatedly for the same url+task — poll get_conversion_report instead. Error codes rate_limited, daily_limit and at_capacity mean try again later.

Endpoints

URLTransportStateLatencyChecked
https://agent-conversion-coral.vercel.app/api/mcp streamable-http answering 49 ms 0 min ago

Alternatives to Agent Conversion — AI Website Conversion Testing

same job, measured the same way
Planner MCP — provable "done" for AI agents
by monopoly-gold-planner

Goal and task planning MCP for Codex and AI agents, with evidence-backed completion.

43 tools answering
Sinter
by shellfu

Persistent, evidence-backed code graph for coding agents.

994 installs/wk local only
Before Users Do
by bhuman-ai

Browser-backed QA with evidence and fix-ready reports for coding agents.

answering
Testers.ai CARBON Test Harness Lite
by jarbon

Local QA workflows, test evidence, screenshot maps and confidence reports for AI coding agents.

local only
M
Maiday
by 35furkan

Distress signal for AI agents: report where you get stuck on websites and fetch site-owner hints.

59 installs/wk local only
Aletheia
by firatmio

Project memory for coding agents whose memories carry code evidence, re-checked on every recall.

76 installs/wk local only
MemCell
by memcell

Shared, persistent memory for AI agents: recall before acting, report outcomes to earn confidence.

1 848 installs/wk answering
T
Traceproof
by raised-traceproof

Search security findings and contribute versioned, evidence-backed reproduction reports.

answering

Agent Conversion — AI Website Conversion Testing — questions

Answers built from our own checks of this server.

What can Agent Conversion — AI Website Conversion Testing do?
It exposes 2 tools, read directly from the server on our last check. Among them: get_conversion_report, test_conversion. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Agent Conversion — AI Website Conversion Testing working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 47 of 92 checks got a reply (51.1%), average response time 256 ms. The bar chart above shows every period we have measured.
Is Agent Conversion — AI Website Conversion Testing still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
The registry lists Agent Conversion — AI Website Conversion Testing as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Agent Conversion — AI Website Conversion Testing?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Agent Conversion — AI Website Conversion Testing need an API key?
No. Agent Conversion — AI Website Conversion Testing completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Agent Conversion — AI Website Conversion Testing?
It answers our handshake in 256 ms on average, which is faster than 54% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.