Agent Conversion — AI Website Conversion Testing
REMOTE · AGENT-CONVERSION-CORAL.VERCEL.APP
Test whether AI agents complete SaaS pricing, signup or sales journeys; get evidence-backed reports.
Available components
Last scanned (3 hours ago)
Scores higher than 81% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Testing and QA
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 727 tokens (~363/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://agent-conversion-coral.vercel.app/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.vercel.app | CN=WR1,O=Google Trust Services,C=US | 31 Oct 2026 | 29 Jan 2027 | RSA 2048 | SHA256-RSA | 9c5f0e6a35c955e113044c86848e4cd5 |
| SANs: *.vercel.app | ||||||
| CN=WR1,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7fd9e2c2d2048a0474b627a26d0868a7 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of agent-conversion-coral.vercel.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| vercel.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agent-conversion-coral.vercel.app/api/mcp | Verified | 200 | |
| http (plaintext) | http://agent-conversion-coral.vercel.app/api/mcp | HTTPS enforced | 308 | https://agent-conversion-coral.vercel.app/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_conversion_report Get an agent conversion report ~250
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.
| Name | Type | Req | Description |
|---|---|---|---|
| audit_id | string | yes | The audit_id returned by test_conversion, or the report URL. |
| Name | Type | Req | Description |
|---|---|---|---|
| audit_id | string | yes | – |
| created_at | string | yes | – |
| domain | – | yes | – |
| evidence | – | yes | – |
| execution_status | – | yes | – |
| failure_classification | – | yes | – |
| is_benchmark | boolean | yes | – |
| locale | string | yes | – |
| message | string | yes | – |
| ok | boolean | yes | – |
| report_url | – | yes | – |
| result | – | yes | – |
| retry_after_seconds | – | yes | – |
| stale | boolean | yes | – |
| status | string | yes | – |
| task | string | yes | – |
| updated_at | – | yes | – |
| url | – | yes | – |
No examples provided.
test_conversion Test agent conversion on a website ~329
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.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Language for the generated summary and recommendations: "en" (default) or "es". |
| task | string | yes | The commercial task in plain language, e.g. "Find the monthly price of the Pro plan" or "Start the free trial signup and stop before entering payment details". |
| url | string | yes | Public website URL to test, including https://, e.g. https://www.example.com or https://www.example.com/pricing. |
| Name | Type | Req | Description |
|---|---|---|---|
| audit_id | string | yes | Pass this to get_conversion_report. |
| domain | string | yes | – |
| locale | string | yes | – |
| next_step | string | yes | – |
| ok | boolean | yes | – |
| report_url | string | yes | Human-readable report; available once the audit completes (404 before). |
| retry_after_seconds | number | yes | – |
| status | string | yes | – |
| submitted_at | string | yes | – |
| task | string | yes | – |
| url | string | yes | – |
No examples provided.
How do I install the Agent Conversion — AI Website Conversion Testing MCP server?
Agent Conversion — AI Website Conversion Testing is a hosted endpoint at https://agent-conversion-coral.vercel.app/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · agent-conversion-coral.vercel.app
claude mcp add --transport http ivanpq98-agent-conversion 'https://agent-conversion-coral.vercel.app/api/mcp'
What is the Agent Conversion — AI Website Conversion Testing MCP server?
Agent Conversion — AI Website Conversion Testing is an MCP server listed in the public MCP registry as io.github.Ivanpq98/agent-conversion. Test whether AI agents complete SaaS pricing, signup or sales journeys; get evidence-backed reports. This page covers its hosted endpoint (https://agent-conversion-coral.vercel.app/api/mcp).
Is the Agent Conversion — AI Website Conversion Testing MCP server safe to use?
Agent Conversion — AI Website Conversion Testing scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Agent Conversion — AI Website Conversion Testing MCP server expose?
Agent Conversion — AI Website Conversion Testing exposes 2 tools: test_conversion, get_conversion_report. Their descriptions and schemas cost roughly 579 tokens of context every time the server is loaded.
Does the Agent Conversion — AI Website Conversion Testing MCP server require authentication?
No. We connected to Agent Conversion — AI Website Conversion Testing without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Agent Conversion — AI Website Conversion Testing MCP server still maintained?
Agent Conversion — AI Website Conversion Testing is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.