MCP servers observed by Lowdown
app.vercel.watchesinstock-mcp/watches-in-stock MCP server: daily status and tool changes
Answered initialize and tools/list on all 3 checks recorded in the last 30 days (2026-11-10 to 2026-11-16) (Lowdown checks this server every 3 days); 11 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-10; tool definitions last changed on 2026-11-16 after 3 days without change; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:app.vercel.watchesinstock-mcp/watches-in-stock
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:app.vercel.watchesinstock-mcp/watches-in-stock?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-16: the server answered initialize and tools/list.
- Observed days in the last 30: 3
- Answered initialize and tools/list: 3
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 3 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 2 of 2 compared days.
- 2026-11-16: input or output schemas changed, descriptions changed
- 2026-11-13: input or output schemas changed, descriptions changed, tool names changed; tool count 17 → 11
What tools does it list?
11 tools on 2026-11-16:
check_availabilitycompare_watchesexplore_modelget_watchidentify_watchmarket_reportprice_checksearch_watchesselling_guidestore_infosuggest_watches
MCP Registry declaration
- Registry name:
app.vercel.watchesinstock-mcp/watches-in-stock - Declared version: 0.3.0
- Status: active
- Declared hosts:
watchesinstock-mcp.vercel.app
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:app.vercel.watchesinstock-mcp/watches-in-stock", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:app.vercel.watchesinstock-mcp/watches-in-stock?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).