INDIVIDUAL MCP TOOL
solver_info
Describe 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.
LIVE ENDPOINT
https://mcp.xhr.dev/mcp
Connect to this endpoint to inspect the live schema for solver_info and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- A tool name, description or schema mentions credentials.
Parent server
CONNECT 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.
Related tools
health_check— Check that the xhr.dev solver is reachable and healthy.solver_stats— Report this deployment's own solve rate — how many challenges it has attempted and how many were accepted.akamai_queue_metrics— Inspect the Akamai solve queue (active, queued, admitted, completed, rejected, timed out).datadome_solve— Solve a DataDome captcha or interstitial challenge.akamai_sbsd_solve— Answer Akamai's SBSD channel for one document.web_fetch— Fetch 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.