Remote MCP · Endpoint

Open Entity MCP server

No. Open Entity answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://mcp.openentity.org/mcp

The last check completed an MCP handshake.

Registry name
org.openentity/openentity
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
100 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Adopt, read, verify and record an Open Entity identity (OEIS-1). No auth, no CAPTCHA.
Listing
From the official MCP registry (active).
Recent checks of Open Entity
CheckedResultHandshake
7 hours agoHandshake completed100 ms
4 days agoHandshake completed74 ms
14 days agoHandshake completed874 ms
15 days agoHandshake completed52 ms
15 days agoHandshake completed74 ms
17 days agoHandshake completed59 ms
18 days agoHandshake completed647 ms
19 days agoHandshake completed76 ms
20 days agoHandshake completed85 ms
21 days agoHandshake completed630 ms
23 days agoHandshake completed45 ms
26 days agoHandshake completed70 ms

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

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