28/28 Agent Service Desk: Fix & Verify

At a glance

Runs where

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 590 tokens of your AI's memory, just for its tool descriptions

Speed

Average answer in our test: 172 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 our latest test, 7 Nov 2026.

Is 28/28 Agent Service Desk: Fix & Verify 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 95/100 on 7 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.

What QAmcp can and can't see · How to tell if an MCP server is safe · Hidden instructions · Prompt injection

Known security advisories

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.

Test results

Safe mode: only tools labeled read-only were run. How the test works

• !
  Ready for the newest MCP version

  1 warning

  • !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
• ✓
  ConnectsConnected in 1.7 s
  pass
• ✓
  Lists its toolsFound 3 tools
  pass
• ✓
  Every tool is describedAll 3 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 inputs

  All good

  • ✓checkDomain: Answered with an error, probably because of our sample input: invalid_domain: Enter a full domain name such as example.com (IP addresses are not checked).
  • ✓quoteFixVerify: Answered with an error, probably because of our sample input: invalid_domain: Enter a full domain name such as example.com (IP addresses are not checked).
  • ✓verifyFixVerify: Answered with an error, probably because of our sample input: Invalid arguments: token missing; send next.verify.arguments from the quote
  pass
• ✓
  Bad inputs give a clean error

  All good

  • ✓checkDomain: Refused missing required input "domain" with a clear error
  • ✓checkDomain: Refused wrong type for "domain" with a clear error
  • ✓quoteFixVerify: Refused missing required input "domain" with a clear error
  • ✓quoteFixVerify: Refused wrong type for "domain" with a clear error
  • ✓verifyFixVerify: Refused missing required input "domain" with a clear error
  • ✓verifyFixVerify: Refused wrong type for "domain" with a clear error
  pass
• ✓
  Fast enough

  All good

  • ✓Connecting took 1.7 s
  • ✓Listing tools took 167 ms
  • ✓Average tool answer: 172 ms
  • ✓checkDomain: Slowest tool: checkDomain (180 ms)
  pass
• ✓
  No secrets leakedChecked 9 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
• –
  Tools work togetherNo safe tool returned data to start a chain from, so chains were not tested (not counted either way)
  not tested

Test it yourself

Free and open source. Same checks, same score.

Show this score on GitHub

Free for every server in the directory. Paste this into your README: the badge shows the score from our latest test.

Score over time

• 7 Nov 202695

One test so far. New tests will show here.

Reviews

Coming soon: reviews from people who use 28/28 Agent Service Desk: Fix & Verify, signed in with GitHub, one per person. Reviews never change the score.