mcpbeat Sign in

corsproxy.dev MCP Server

by corsproxy Your server? Claim it
answering

corsproxy.dev is answering right now. Last checked 10 min ago.

Call third-party APIs from agents without leaking secrets. SSRF blocked, per-key quotas.

Uptime history 24 days of history · worst day 99%
24 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
169 ms
Response time
average over 24h
authentication required
Access
streamable-http

Nothing serious here today

Today is the operative word: we check corsproxy.dev every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

run in your terminal
claude mcp add mcp --transport http https://api.corsproxy.dev/mcp
Settings → Connectors → Add custom connector, then paste this address
https://api.corsproxy.dev/mcp
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://api.corsproxy.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://api.corsproxy.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://api.corsproxy.dev/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URLTransportStateLatencyChecked
https://api.corsproxy.dev/mcp streamable-http needs auth 78 ms 10 min ago

Alternatives to corsproxy.dev

same job, measured the same way
Tremelay
by charitonmedia

Local MCP broker: agents call credentials through a daemon without seeing secrets.

local only
JFSecure
by theone55

Let AI agents use secrets without seeing them: masked output, every use approved in JFSecure.

local only
Onepassword Agent MCP
by gambadio

Save and use 1Password secrets locally without exposing plaintext to AI agents.

81 installs/wk local only
seekrit — secrets for agents
by seekrit

Encrypted store for API keys and database URLs your code needs. Use them without reading them.

40 tools answering
mcp-toolbelt
by papacasper

29 pay-per-call DNS, SEO, SSL, security, WHOIS, mail, and AI tools for AI agents. x402, no API key.

29 tools answering
Phantom Secrets
by ashlrai

Value-blind secret metadata and gated workflows for AI coding agents through Phantom's local proxy.

61 installs/wk local only
Stashbase
by stashbase

Secrets for developers and agents—secure context and workflows without exposing secret values.

answering
Agent-Shield
by startekenterprises-ai

Security scanner for AI agents: prompt injection, leaked secrets, PII, and SSRF-risk URL detection.

answering

corsproxy.dev — questions

Answers built from our own checks of this server.

Why is there no tool list for corsproxy.dev?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is corsproxy.dev working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 169 ms. The bar chart above shows every period we have measured.
How do I connect corsproxy.dev?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.
Does corsproxy.dev need an API key?
Yes. Every time we knock, corsproxy.dev answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is corsproxy.dev?
It answers our handshake in 169 ms on average, which is faster than 85% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.