QAmcpTest another server

Test certificate: buggy-test-serverhttp://127.0.0.1:4310/mcp

Server
buggy-test-server 0.0.1
MCP version
2025-11-25 · streamable HTTP
Tested
2026-10-20 · 16:14 UTC
Safety mode
Only tools labeled read-only were run
Logged in
No
Tester
QAmcp 0.1.12
Result
38/ 100
FAIL
10 of 10 checks · 5 of 9 tools run

Failures: fix these first 6

T-4.2

slow_report: Has no description, so the AI has to guess what it does

T-6.1

fetch_notes: Description contains hidden <IMPORTANT> block. This is a known trick to make AI do things the user didn't ask for.

T-7.4

slow_report: No answer within the time limit

T-8.7

slow_report: Hung on missing required input "id"

T-11.1

search_users: Error message shows what looks like a database password in a link

T-8.8

slow_report: Hung on wrong type for "id"

Notes: worth fixing 10

T-5.1

4 of 9 tools have no safety label (read-only or dangerous): list_projects, team_digest, get_or_create_user, delete_account

T-10.4

search_users: Slowest tool: search_users (3.0 s): users will notice the wait

T-4.1

search_users: Inputs with no description: name

T-5.2

delete_account: Name sounds like it deletes something, but it is not labeled dangerous

T-7.3

fetch_notes: Answered, but it gives the exact same answer to bad input as to good input, so it may be ignoring what it is sent

T-8.5

fetch_notes: Accepted missing required input "key" without complaining

and 4 more in the test items below

All test items

Open an item to see every result behind it.

T-1ConnectsConnected in 80 msPASS
T-1.1

Connected in 80 ms

T-2Ready for the newest MCP versionUses an older MCP version (2025-11-25). It works today, but it isn't on the July 2026 version (2026-07-28) yet.NOTE
T-2.1

Uses an older MCP version (2025-11-25). It works today, but it isn't on the July 2026 version (2026-07-28) yet.

T-3Lists its toolsFound 9 toolsPASS
T-3.1

Found 9 tools

T-4Every tool is describedslow_report: Has no description, so the AI has to guess what it doesFAIL
T-4.1

search_users: Inputs with no description: name

T-4.2

slow_report: Has no description, so the AI has to guess what it does

T-5Tools are labeled safe or dangerous4 of 9 tools have no safety label (read-only or dangerous): list_projects, team_digest, get_or_create_user, delete_accountNOTE
T-5.1

4 of 9 tools have no safety label (read-only or dangerous): list_projects, team_digest, get_or_create_user, delete_account

T-5.2

delete_account: Name sounds like it deletes something, but it is not labeled dangerous

T-6No hidden instructionsfetch_notes: Description contains hidden <IMPORTANT> block. This is a known trick to make AI do things the user didn't ask for.FAIL
T-6.1

fetch_notes: Description contains hidden <IMPORTANT> block. This is a known trick to make AI do things the user didn't ask for.

T-7Tools work with good inputsslow_report: No answer within the time limitFAIL
T-7.1

get_weather: Worked (5 ms)

T-7.2

search_users: Worked (3.0 s)

T-7.3

fetch_notes: Answered, but it gives the exact same answer to bad input as to good input, so it may be ignoring what it is sent

T-7.4

slow_report: No answer within the time limit

T-7.5

strict_lookup: Worked (22 ms)

T-8Bad inputs give a clean errorslow_report: Hung on missing required input "id"FAIL
T-8.1

get_weather: Refused missing required input "city" with a clear error

T-8.2

get_weather: Refused wrong type for "city" with a clear error

T-8.3

search_users: Refused missing required input "name" with a clear error

T-8.4

search_users: Refused wrong type for "name" with a clear error

T-8.5

fetch_notes: Accepted missing required input "key" without complaining

T-8.6

fetch_notes: Accepted wrong type for "key" without complaining

T-8.7

slow_report: Hung on missing required input "id"

T-8.8

slow_report: Hung on wrong type for "id"

T-8.9

strict_lookup: Refused missing required input "code" with a clear error

T-8.10

strict_lookup: Refused wrong type for "code" with a clear error

T-8.11

Errors are sent with an HTTP error status (like 400) instead of a normal MCP reply, so some AI apps may treat them as crashes: strict_lookup

T-9Tools work togetherNo tool's answer could be fed into another tool, so there were no chains to test (not counted either way)NOT TESTED

No tool's answer could be fed into another tool, so there were no chains to test (not counted either way)

T-10Fast enoughsearch_users: Slowest tool: search_users (3.0 s): users will notice the waitNOTE
T-10.1

Connecting took 80 ms

T-10.2

Listing tools took 6 ms

T-10.3

Average tool answer: 762 ms

T-10.4

search_users: Slowest tool: search_users (3.0 s): users will notice the wait

T-11No secrets leakedsearch_users: Error message shows what looks like a database password in a linkFAIL
T-11.1

search_users: Error message shows what looks like a database password in a link

T-11.2

search_users: Error message shows internal details: code stack trace, server file path

Tools not run, and why

QAmcp never runs a tool that could change something on your server. If you own it, --owner runs the unlabeled tools whose names clearly only read.