Remote MCP · Endpoint

Zephior Discovery MCP server

No. Zephior Discovery answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.zephior.com/mcp

The last check completed an MCP handshake.

Registry name
com.zephior/discovery
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
485 ms
Tools exposed
8 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Search public tender notices with sources, plus Zephior resources. Read-only, no authentication.
Listing
From the official MCP registry (active).
Recent checks of Zephior Discovery
CheckedResultHandshake
1 hour agoHandshake completed485 ms
9 days agoHandshake completed479 ms
9 days agoHandshake completed504 ms
11 days agoHandshake completed515 ms
12 days agoFailed - the request timed out—
13 days agoHandshake completed476 ms
14 days agoHandshake completed182 ms
14 days agoHandshake completed509 ms
16 days agoHandshake completed810 ms
19 days agoHandshake completed2.84 s
21 days agoHandshake completed478 ms
24 days agoHandshake completed486 ms
26 days agoHandshake completed178 ms
28 days agoHandshake completed475 ms

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

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