Remote MCP · Endpoint

SEAR MCP server

No. SEAR answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://sear.genesisconductor.io/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.igor-holt/sear
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.72 s
Tools exposed
3 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Benchmark-first release surface with a read-only MCP endpoint and operator CLI.
Listing
From the official MCP registry (active).
Recent checks of SEAR
CheckedResultHandshake
1 hour agoHandshake completed1.72 s
2 days agoHandshake completed1.18 s
4 days agoHandshake completed670 ms
5 days agoHandshake completed472 ms
7 days agoHandshake completed595 ms
8 days agoHandshake completed399 ms
9 days agoHandshake completed383 ms
12 days agoHandshake completed400 ms
13 days agoHandshake completed576 ms
15 days agoHandshake completed725 ms
17 days agoHandshake completed1.19 s
18 days agoHandshake completed500 ms
19 days agoHandshake completed538 ms
20 days agoHandshake completed665 ms
20 days agoHandshake completed407 ms
21 days agoHandshake completed400 ms
23 days agoHandshake completed581 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 SEAR and makes no claim about it beyond what these checks measured.