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
3 tools
Its own safety labels
3 read-only
Memory it takes
About 560 tokens of your AI's memory, just for its tool descriptions
Largest answer
About 61.3 KB in our test
Speed
Average answer in our test: 45 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 Dev.cards MCP server safe?
None of the hidden-instruction wordings we know were found in its 3 tool descriptions.
Its error messages showed no secrets or internal details.
All 3 of its tools are labeled read-only.
Overall it scored 89/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
3 tools, in the server's own words.
search_componentsread-only
Search the published Dev.cards UI components (hero sections, pricing tables, dashboards, forms, navigation and more) by text and implementation target.
get_componentread-only
Get metadata, the design specification, source references and the available implementations of one component by id.
get_component_coderead-only
Get the complete, pre-generated source files of one component for one tested target, with their SHA-256 hashes, setup instructions and pinned dependencies.
!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
!
Every tool is described1 warning
!get_component_code: Inputs with no description: framework, styling, language
note
!
Follows MCP best practices (not scored yet)1 tip (not scored)
!1 tool answers with structured data but doesn't declare its shape (outputSchema): search_components. If those answers change shape, nothing can catch it; with a schema, every answer is checked.
note
✓
ConnectsConnected in 594 ms
pass
✓
Lists its toolsFound 3 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
✓search_components: Worked (70 ms)
✓get_component: Answered with an error, probably because of our sample input: {"error":{"code":"UNKNOWN_COMPONENT","message":"Unknown component test","alternatives":{"components":["assurance-row","brief-composer","bri…
✓get_component_code: Answered with an error, probably because of our sample input: {"error":{"code":"UNKNOWN_COMPONENT","message":"Unknown component test","alternatives":{"components":["assurance-row","brief-composer","bri…
pass
✓
Bad inputs give a clean errorAll good
✓search_components: Refused wrong type for "q" with a clear error
✓get_component: Refused missing required input "id" with a clear error
✓get_component: Refused wrong type for "id" with a clear error
✓get_component_code: Refused missing required input "id" with a clear error
✓get_component_code: Refused wrong type for "id" with a clear error
pass
✓
Tools work together2 chains working
✓search_components → get_component: get_component found what search_components returned (id = "assurance-row")
✓search_components → get_component_code: get_component_code found what search_components returned (id = "assurance-row")
No secrets leakedChecked 9 error messages: no secrets or internal details
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.