Remote MCP · Endpoint

sigelo MCP server

No. sigelo answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://sigelo.io/mcp

The last check completed an MCP handshake.

Registry name
io.github.csigelo/sigelo
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
331 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
One identity an AI agent owns: proves who it is offline, keeps its reputation, pays, messages agents
Listing
From the official MCP registry (active).
Recent checks of sigelo
CheckedResultHandshake
7 hours agoHandshake completed331 ms
4 days agoHandshake completed395 ms
14 days agoHandshake completed393 ms
15 days agoHandshake completed340 ms
15 days agoHandshake completed337 ms
17 days agoHandshake completed335 ms
18 days agoHandshake completed332 ms
19 days agoHandshake completed328 ms
20 days agoHandshake completed352 ms
21 days agoHandshake completed347 ms
23 days agoHandshake completed339 ms
26 days agoHandshake completed331 ms
28 days agoHandshake completed372 ms

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

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