Remote MCP · Endpoint

search-mcp MCP server

No. search-mcp answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://search.ioconnex.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.ioconnex/search-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
280 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Web search and clean-text page fetch for AI agents, with SSRF protection.
Listing
From the official MCP registry (active).
Recent checks of search-mcp
CheckedResultHandshake
1 hour agoHandshake completed280 ms
2 days agoHandshake completed206 ms
4 days agoHandshake completed335 ms
6 days agoHandshake completed295 ms
7 days agoHandshake completed300 ms
9 days agoHandshake completed350 ms
10 days agoHandshake completed274 ms
11 days agoHandshake completed174 ms
14 days agoHandshake completed279 ms
15 days agoHandshake completed283 ms
17 days agoHandshake completed406 ms
19 days agoHandshake completed304 ms
20 days agoHandshake completed301 ms
21 days agoHandshake completed130 ms
22 days agoHandshake completed272 ms

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

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