Remote MCP · Endpoint

ship.page MCP server

No. ship.page answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://ship.page/mcp

The last check completed an MCP handshake.

Registry name
page.ship/ship-page
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
48 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Deploy HTML from any agent: POST markup, get a live URL. Static hosting API with MCP tools.
Listing
From the official MCP registry (active).
Recent checks of ship.page
CheckedResultHandshake
1 hour agoHandshake completed48 ms
2 days agoHandshake completed300 ms
4 days agoHandshake completed331 ms
5 days agoHandshake completed341 ms
7 days agoHandshake completed316 ms
8 days agoHandshake completed474 ms
9 days agoHandshake completed309 ms
12 days agoHandshake completed262 ms
13 days agoHandshake completed289 ms
15 days agoHandshake completed147 ms
17 days agoHandshake completed266 ms
18 days agoHandshake completed304 ms
19 days agoHandshake completed256 ms
20 days agoHandshake completed245 ms
21 days agoHandshake completed302 ms
21 days agoHandshake completed286 ms
23 days agoHandshake completed225 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 ship.page and makes no claim about it beyond what these checks measured.