Copied. Paste it into Claude Code, Cursor or Codex:Fetch and follow the instructions at https://qamcp.dev/setup.md to test my MCP server.
Your AI finds your server in your project, tests it with QAmcp, explains what's wrong in plain words, fixes it with your OK, and tests again. Read the instructions
On their server. What you send to it goes to them.
What you need
Nothing: it answered without a login
Tools
2 tools
Its own safety labels
2 read-only
Memory it takes
About 1,800 tokens of your AI's memory, just for its tool descriptions
Largest answer
About 4.2 KB in our test
Speed
Average answer in our test: 112 ms
Tokens are an estimate: the characters in its tool names, descriptions and inputs, divided by 4. The exact number depends on your AI model. Safety labels are what the server says about itself. From the daily test on 12 Nov 2026.
Is Border MCP server safe?
None of the hidden-instruction wordings we know were found in its 2 tool descriptions.
Its error messages showed no secrets or internal details.
All 2 of its tools are labeled read-only.
Overall it scored 95/100 on 12 Nov 2026.
A test can only see what the server shows from outside, not what it does with your data behind the scenes. Connect servers from makers you trust.
What this test does not check
Its source code and packages.
What a tool quietly does behind the scenes, such as writing a file or calling another service.
Instructions hidden inside live tool answers. We only look for those in tool descriptions.
Hidden instructions worded in a way our list doesn't know yet.
Tools that could change something. Those are read, never run.
It lists no public code, so there is nothing to look up in GitHub Security Advisories or OSV.dev. QAmcp tests how a server behaves. It does not scan source code.
What it can do
2 tools, in the server's own words.
border_check_corsread-only
Use 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…
border_check_cors_headersread-only
Use 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 D…
!Uses an older MCP version (2025-11-25). It works today, but it isn't on the July 2026 version (2026-07-28) yet.
note
✓
ConnectsConnected in 387 ms
pass
✓
Lists its toolsFound 2 tools
pass
✓
Every tool is describedAll 2 tools and their inputs are described
pass
✓
Tools are labeled safe or dangerousEvery tool has a safety label
pass
✓
No known hidden instructionsNone of the hidden-instruction wordings we know were found in tool descriptions. New wordings can get past this check.
pass
✓
Tools work with good inputsAll good
✓border_check_cors: Worked (121 ms)
✓border_check_cors_headers: Answered with an error, probably because of our sample input: Give preflight_response (the OPTIONS response) and/or response (the actual response): raw headers as printed by curl -i or copied from the …
pass
✓
Bad inputs give a clean errorAll good
✓border_check_cors: Refused missing required input "url" with a clear error
✓border_check_cors: Refused wrong type for "url" with a clear error
✓border_check_cors_headers: Refused missing required input "url" with a clear error
✓border_check_cors_headers: Refused wrong type for "url" with a clear error
No secrets leakedChecked 7 error messages: no secrets or internal details
pass
✓
Follows MCP best practices (not scored yet)Tool names, safety labels and tool list size follow the MCP guide
pass
✓
Resources and prompts workAll good (2 resources, 1 prompt)
✓Opened 2 of 2 resources
✓An address that does not exist gets a clean "not found" error
✓Opened 1 of 1 prompts
pass
–
Tools work togetherNo tool's answer could be fed into another tool, so there were no chains to test (not counted either way)
not tested
Show this score on GitHub
Free for every server in the directory. Paste this into your README: the badge always shows the newest score, from the daily test, a test on our website or a Monitor test.