Remote MCP · Endpoint

SeaWeb MCP server

No. SeaWeb answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.seaweb.tech/mcp

The last check completed an MCP handshake.

Registry name
tech.seaweb/seaweb
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.00 s
Tools exposed
43 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Read-only web search for AI agents; does not book, reserve or take payment. Stores your preferences.
Listing
From the official MCP registry (active).
Recent checks of SeaWeb
CheckedResultHandshake
1 hour agoHandshake completed1.00 s
2 days agoHandshake completed815 ms
4 days agoHandshake completed829 ms
5 days agoHandshake completed1.70 s
7 days agoHandshake completed1.42 s
8 days agoHandshake completed870 ms
9 days agoHandshake completed1.38 s
12 days agoHandshake completed1.50 s
13 days agoHandshake completed1.46 s
15 days agoHandshake completed952 ms
17 days agoHandshake completed1.07 s
18 days agoHandshake completed722 ms
19 days agoHandshake completed743 ms
20 days agoHandshake completed858 ms
21 days agoHandshake completed1.01 s
21 days agoHandshake completed661 ms
23 days agoHandshake completed668 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 SeaWeb and makes no claim about it beyond what these checks measured.