Remote MCP · Endpoint

Scanverity Public Market Discovery MCP server

No. Scanverity Public Market Discovery answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://scanverity.com/mcp-discovery

The last check completed an MCP handshake.

Registry name
com.scanverity/public-market-discovery
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
367 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Free Polymarket search; EUR100 written reports or one-rule QA; EUR500 five-rule QA by quote.
Listing
From the official MCP registry (active).
Recent checks of Scanverity Public Market Discovery
CheckedResultHandshake
34 minutes agoHandshake completed367 ms
9 days agoHandshake completed340 ms
10 days agoHandshake completed360 ms
11 days agoHandshake completed337 ms
12 days agoHandshake completed423 ms
14 days agoHandshake completed349 ms
14 days agoHandshake completed347 ms
15 days agoHandshake completed332 ms
17 days agoHandshake completed343 ms
19 days agoHandshake completed331 ms
21 days agoHandshake completed362 ms
24 days agoHandshake completed352 ms
26 days agoHandshake completed335 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Scanverity Public Market Discovery and makes no claim about it beyond what these checks measured.