Debug CORS: send the real preflight, get Chrome's exact error and the headers that fix it.
Connect Remote server
claude mcp add --transport http border https://border.clawhard.com/mcp
{
"mcpServers": {
"border": {
"url": "https://border.clawhard.com/mcp"
}
}
}
{
"servers": {
"border": {
"type": "http",
"url": "https://border.clawhard.com/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://border.clawhard.com/mcp
Tools 2 found in our last check
border_check_corsUse when the user hits a CORS error ("blocked by CORS policy", "No 'Access-Control-Allow-Origin' header", "preflight", "Failed to fetch" from a frontend) or is about to call a public API from browser code (React, Next.js, Vue, a browser extension page) and asks whether it will w…
border_check_cors_headersUse when a CORS problem involves a server Border cannot reach (localhost, a dev or staging server, a private network, a custom port) or a POST, PUT, PATCH or DELETE whose real response needs checking, and the raw response headers are available from curl -i or the browser DevTool…
Details
| Endpoint | https://border.clawhard.com/mcp (Streamable HTTP) |
| First published | 12 Nov 2026 |
| Last updated | 12 Nov 2026 |
| Registry name | com.clawhard/border |
More browser automation servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
