Remote MCP · Endpoint

99 Data Rooms MCP server

No. 99 Data Rooms answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://mcp.99datarooms.com/mcp

The last check completed an MCP handshake.

Registry name
com.99datarooms/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
884 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Read-only facts about 99 Data Rooms, a UK virtual data room: docs, glossary, pricing, use cases.
Listing
From the official MCP registry (active).
Recent checks of 99 Data Rooms
CheckedResultHandshake
34 minutes agoHandshake completed884 ms
8 days agoHandshake completed1.20 s
9 days agoHandshake completed945 ms
11 days agoHandshake completed744 ms
12 days agoHandshake completed1.43 s
12 days agoHandshake completed774 ms
14 days agoHandshake completed1.15 s
14 days agoHandshake completed805 ms
16 days agoHandshake completed1.51 s
19 days agoHandshake completed1.06 s
21 days agoHandshake completed566 ms
24 days agoHandshake completed568 ms
26 days agoHandshake completed491 ms
28 days agoHandshake completed643 ms

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

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