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
- 571 ms
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Benchmark-first release surface with a read-only MCP endpoint and operator CLI.
- Repository
- https://github.com/igor-holt/sear
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 571 ms |
| 1 day ago | Handshake completed | 1.30 s |
| 2 days ago | Handshake completed | 457 ms |
| 3 days ago | Handshake completed | 465 ms |
| 4 days ago | Handshake completed | 714 ms |
| 5 days ago | Handshake completed | 811 ms |
| 6 days ago | Handshake completed | 989 ms |
| 9 days ago | Handshake completed | 404 ms |
| 11 days ago | Handshake completed | 524 ms |
| 14 days ago | Handshake completed | 660 ms |
| 16 days ago | Handshake completed | 456 ms |
| 18 days ago | Handshake completed | 561 ms |
| 20 days ago | Handshake completed | 1.72 s |
| 22 days ago | Handshake completed | 1.18 s |
| 24 days ago | Handshake completed | 670 ms |
| 26 days ago | Handshake completed | 472 ms |
| 28 days ago | Handshake completed | 595 ms |
| 29 days ago | Handshake completed | 399 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
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.