Remote MCP · Endpoint

com.empryo/docs MCP server

No. com.empryo/docs answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://empryo.com/mcp

The last check completed an MCP handshake.

Registry name
com.empryo/docs
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
216 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Search and read Empryo's documentation. Read-only, no auth, no local access.
Listing
From the official MCP registry (active).
Recent checks of com.empryo/docs
CheckedResultHandshake
1 hour agoHandshake completed216 ms
2 days agoHandshake completed88 ms
4 days agoHandshake completed207 ms
5 days agoHandshake completed207 ms
7 days agoHandshake completed283 ms
8 days agoHandshake completed513 ms
9 days agoHandshake completed113 ms
12 days agoHandshake completed222 ms
13 days agoHandshake completed233 ms
15 days agoHandshake completed601 ms
16 days agoHandshake completed213 ms
17 days agoHandshake completed213 ms
18 days agoHandshake completed168 ms
19 days agoHandshake completed204 ms
20 days agoHandshake completed229 ms
21 days agoHandshake completed290 ms
22 days agoHandshake completed201 ms

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

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 com.empryo/docs and makes no claim about it beyond what these checks measured.