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
4 tools
Its own safety labels
4 read-only
Memory it takes
About 940 tokens of your AI's memory, just for its tool descriptions
Largest answer
About 16.9 KB in our test
Speed
Average answer in our test: 118 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 13 Nov 2026.
Is Bowling Data Agent API MCP server safe?
None of the hidden-instruction wordings we know were found in its 4 tool descriptions.
Its error messages showed no secrets or internal details.
All 4 of its tools are labeled read-only.
Overall it scored 89/100 on 13 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
4 tools, in the server's own words.
aboutread-only
What Bowling Data (https://bowlingdata.co) measures at bowling centers, its plans, free sample day and every document id, plus its sister sites.
searchread-only
Ask a question in plain language.
fetchread-only
Read one document by id (from search or about).
dataread-only
Structured rows from the Fron Research Data API (https://api.fronresearch.com/v1): markets, venues, bookable slots and rollups of sell-through and modeled reve…
!Uses an older MCP version (2025-06-18). It works today, but it isn't on the July 2026 version (2026-07-28) yet.
note
!
Every tool is described1 warning
!search: Inputs with no description: maxResults
note
!
Follows MCP best practices (not scored yet)1 tip (not scored)
!Very common tool names: search, fetch. Next to other servers' tools the AI may mix them up; a short prefix helps (like "github_search" instead of "search").
note
✓
ConnectsConnected in 425 ms
pass
✓
Lists its toolsFound 4 tools
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
✓about: Worked (80 ms)
✓search: Worked (105 ms)
✓fetch: Answered with an error, probably because of our sample input: No document "test". GET https://bowlingdata.co/api/agent lists this site's ids; every site's are listed at https://fronresearch.com/api/age…
✓data: Worked (219 ms)
pass
✓
Bad inputs give a clean errorAll good
✓search: Refused missing required input "query" with a clear error
✓search: Refused wrong type for "query" with a clear error
✓fetch: Refused missing required input "id" with a clear error
✓fetch: Refused wrong type for "id" with a clear error
✓data: Refused missing required input "endpoint" with a clear error
✓data: Refused wrong type for "endpoint" with a clear error
pass
✓
Tools work together2 chains working
✓about → fetch: fetch found what about returned (id = "sample/bowlingdata")
✓search → fetch: fetch found what search returned (id = "sample/bowlingdata")
pass
✓
Fast enoughAll good
✓Connecting took 425 ms
✓Listing tools took 66 ms
✓Average tool answer: 118 ms
✓data: Slowest tool: data (219 ms)
pass
✓
No secrets leakedChecked 10 error messages: no secrets or internal details
pass
✓
No known hidden instructions in tool answers (not scored yet)Read 15 answers from 4 tools: none of the hidden-instruction wordings we know were found. New wordings can get past this check.
pass
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.