Remote MCP · Endpoint

Mongo ObjectId shape MCP server

No. Mongo ObjectId shape answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/objectid-shape/mcp

The last check completed an MCP handshake.

Registry name
io.github.sadri-dridi/objectid-shape
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
20 ms
Tools exposed
31 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Mongo ObjectId shape
Listing
From the official MCP registry (active).
Recent checks of Mongo ObjectId shape
CheckedResultHandshake
1 day agoHandshake completed20 ms
4 days agoHandshake completed13 ms
5 days agoHandshake completed33 ms
7 days agoHandshake completed35 ms
8 days agoHandshake completed105 ms
9 days agoHandshake completed14 ms
12 days agoHandshake completed16 ms
13 days agoHandshake completed171 ms
15 days agoHandshake completed30 ms
16 days agoHandshake completed20 ms
17 days agoHandshake completed12 ms
19 days agoHandshake completed12 ms
19 days agoHandshake completed12 ms
20 days agoHandshake completed21 ms
21 days agoHandshake completed14 ms
23 days agoHandshake completed12 ms

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

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 Mongo ObjectId shape and makes no claim about it beyond what these checks measured.