Watches in Stock

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

11 tools

Its own safety labels

11 read-only

Memory it takes

About 2,700 tokens of your AI's memory, just for its tool descriptions

Largest answer

About 13.3 KB in our test

Speed

Average answer in our test: 734 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 Watches in Stock MCP server safe?

• None of the hidden-instruction wordings we know were found in its 11 tool descriptions.
• Its error messages showed no secrets or internal details.
• All 11 of its tools are labeled read-only.
• Overall it scored 88/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

11 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-11-25). It works today, but it isn't on the July 2026 version (2026-07-28) yet.
  note
• !
  Every tool is described

  2 warnings

  • !search_watches: Inputs with no description: condition, bracelet
  • !price_check: Inputs with no description: condition, bracelet
  note
• !
  Fast enough

  1 warning

  • !search_watches: Slowest tool: search_watches (6.0 s): users will notice the wait
  • and 3 more
  note
• ✓
  ConnectsConnected in 424 ms
  pass
• ✓
  Lists its toolsFound 11 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 inputs

  All good

  • ✓search_watches: Worked (6.0 s)
  • ✓market_report: Worked (409 ms)
  • ✓compare_watches: Answered with an error, probably because of our sample input: MCP error -32602: Input validation error: Invalid arguments for tool compare_watches: Invalid UUID at ids[0] Too small: expected array to h…
  • ✓get_watch: Answered with an error, probably because of our sample input: MCP error -32602: Input validation error: Invalid arguments for tool get_watch: Invalid UUID at id
  • ✓get_specialist_link: Answered with an error, probably because of our sample input: MCP error -32602: Input validation error: Invalid arguments for tool get_specialist_link: Invalid UUID at id
  • ✓get_sourcing_link: Worked (305 ms)
  • ✓check_availability: Answered with an error, probably because of our sample input: MCP error -32602: Input validation error: Invalid arguments for tool check_availability: Invalid UUID at ids[0]
  • ✓store_info: Worked (65 ms)
  • and 3 more
  pass
• ✓
  Bad inputs give a clean error

  All good

  • ✓search_watches: Refused wrong type for "query" with a clear error
  • ✓market_report: Refused wrong type for "query" with a clear error
  • ✓compare_watches: Refused missing required input "ids" with a clear error
  • ✓compare_watches: Refused wrong type for "ids" with a clear error
  • ✓get_watch: Refused missing required input "id" with a clear error
  • ✓get_watch: Refused wrong type for "id" with a clear error
  • ✓get_specialist_link: Refused missing required input "id" with a clear error
  • ✓get_specialist_link: Refused wrong type for "id" with a clear error
  • and 9 more
  pass
• ✓
  Tools work together

  3 chains working

  • ✓search_watches → get_watch: get_watch found what search_watches returned (id = "36fd8392-5581-4166-8a69-ee90fcb3bddf")
  • ✓search_watches → get_specialist_link: get_specialist_link found what search_watches returned (id = "36fd8392-5581-4166-8a69-ee90fcb3bddf")
  • ✓search_watches → check_availability: check_availability found what search_watches returned (ids = "36fd8392-5581-4166-8a69-ee90fcb3bddf")
  pass
• ✓
  No secrets leakedChecked 26 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 work

  All good (1 resource, 4 prompts)

  • ✓Opened 1 of 1 resources
  • ✓An address that does not exist gets a clean "not found" error
  • ✓Opened 4 of 4 prompts
  pass

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 202688

One test so far. New tests will show here.

Reviews

Coming soon: reviews from people who use Watches in Stock, signed in with GitHub, one per person. Reviews never change the score.