Corsproxy MCP server
Which servers in the official MCP registry are Corsproxy's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-20
- Registry namedev.corsproxy/mcpverified in the MCP registry
The registry name sits under corsproxy.dev. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Staterequires sign-inchecked 2026-10-20
On 2026-10-20 the server answered and asked for a sign-in with a Corsproxy account (OAuth). It shows its tool list only to signed-in users, so we list none here.
- Checked on 2 of the 7 days it takes to judge reliability.
Once connected
- Needs a key pasted into the client config.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
- Answeredmeasuring2 of the 7 daily checks it takes to print a share
- Median first answer117 ms
- Sign-ina key you paste
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"corsproxy": {
"type": "http",
"url": "https://api.corsproxy.dev/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http corsproxy https://api.corsproxy.dev/mcpclaude.ai, ChatGPT and other clients: add https://api.corsproxy.dev/mcp as a custom connector in the settings.
The first time it connects, the client opens a Corsproxy sign-in.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.