Remote MCP · Endpoint

SeaWeb MCP server

Yes, as of 1 hour ago: the check failed for an unclassified reason.

DownLast checked 1 hour ago

Server URL

https://api.seaweb.tech/mcp

The last check failed: the check failed for an unclassified reason.

Registry name
tech.seaweb/seaweb
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
43 tools
Uptime, last 30 days
52.6% from 19 checks
Described by its publisher as
Read-only web search for AI agents; does not book, reserve or take payment. Stores your preferences.
Website
https://seaweb.tech/
Listing
From the official MCP registry (active).
Recent checks of SeaWeb
CheckedResultHandshake
1 hour agoFailed - the check failed for an unclassified reason—
1 day agoFailed - the check failed for an unclassified reason—
2 days agoFailed - the check failed for an unclassified reason—
3 days agoFailed - the check failed for an unclassified reason—
4 days agoFailed - the check failed for an unclassified reason—
5 days agoFailed - the check failed for an unclassified reason—
6 days agoFailed - the check failed for an unclassified reason—
8 days agoFailed - the check failed for an unclassified reason—
11 days agoFailed - the check failed for an unclassified reason—
13 days agoHandshake completed539 ms
15 days agoHandshake completed1.52 s
18 days agoHandshake completed789 ms
20 days agoHandshake completed1.00 s
22 days agoHandshake completed815 ms
24 days agoHandshake completed829 ms
26 days agoHandshake completed1.70 s
27 days agoHandshake completed1.42 s
28 days agoHandshake completed870 ms
29 days agoHandshake completed1.38 s

The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 20 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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.