@proxlane/sdk
An MCP server that gives an AI agent a web-fetch tool that fails honestly.
A plain fetch hands an agent a 200 with a captcha in the body, and the agent summarises the
captcha. This tool fetches through your own Proxlane gateway, which fails
over between scraping APIs and checks every response for block pages. The agent gets the page as
readable text, or a failure that says what happened and whether retrying is worth it. A block page
is never returned as content.
Set up
You need a running gateway with at least one provider key. That is one container:
proxlane.dev/docs/quickstart.
Then add the server to your MCP client. Claude Code:
Claude Desktop, Cursor and other clients take the same three things in their JSON config:
PROXLANE_API_KEY is the gateway's own key, not a provider's. Provider keys stay on the gateway.
Pin the version, as above: npx -y otherwise runs whatever was published last, with that key in
its environment.
Every call spends provider credits, several times more with render or wait_for. The tool
is deliberately not marked read-only, so clients that auto-approve read-only tools still ask.
The tool
fetch_page
On failure the result is marked as an error and reads:
class is one of six that never grows, and retryable follows from it: the site's own answer
(target) and a bad request (client) are not worth retrying; a block or a provider problem may
be, later. The gateway has already tried every provider it could, so an immediate retry is not.
In your own process
Apache-2.0.