Security & Testing
xhr.dev
An MCP server that solves anti-bot captcha and interstitial challenges such as DataDome and Akamai SBSD while exposing health, solve-rate, and queue metrics.
ENDPOINT 1
https://mcp.xhr.dev/mcp
MCP server metadata
- Name
- xhrdev
- Version
- 1.0.0
Known tools 7
solver_statsReport this deployment's own solve rate — how many challenges it has attempted and how many were accepted.
Inferred read-onlyakamai_queue_metricsInspect the Akamai solve queue (active, queued, admitted, completed, rejected, timed out).
Inferred read-onlyweb_fetchFetch a URL and return its content, clearing a DataDome challenge automatically if one is in the way — the fetch, the solve, and the retry all happen server-side, so you get the page back in one call instead of doing the datadome_solve dance yourself.
Inferred read-onlysolver_infoDescribe this MCP deployment: which solver it is pointed at, whether it is running on your API key or the shared trial key, and which tools it does not have.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.xhrdev]
url = "https://mcp.xhr.dev/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"xhrdev": {
"type": "http",
"url": "https://mcp.xhr.dev/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: xhrdev
Remote MCP URL: https://mcp.xhr.dev/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"xhrdev": {
"url": "https://mcp.xhr.dev/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"xhrdev": {
"type": "http",
"url": "https://mcp.xhr.dev/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "xhrdev",
"transport": "streamable-http",
"url": "https://mcp.xhr.dev/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.