Remote MCP · Endpoint

MAX Data Value Check MCP server

No. MAX Data Value Check answered an MCP handshake 53 minutes ago.

UpLast checked 53 minutes ago

Server URL

https://monsterdata.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.monsterdata/max-data-value-check
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
387 ms
Tools exposed
5 tools
Uptime, last 30 days
4 checks from 4 checks
Described by its publisher as
Is your business data licensable? Free readiness score, rights checklist, owner handoff to MAX.
Listing
From the official MCP registry (active).
Recent checks of MAX Data Value Check
CheckedResultHandshake
53 minutes agoHandshake completed387 ms
3 days agoHandshake completed119 ms
12 days agoHandshake completed150 ms
13 days agoHandshake completed286 ms

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

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 MAX Data Value Check and makes no claim about it beyond what these checks measured.