Remote MCP · Endpoint

Shipwork SEO Checks MCP server

No. Shipwork SEO Checks answered an MCP handshake 18 minutes ago.

UpLast checked 18 minutes ago

Server URL

https://shipwork.io/mcp/%7Btoken%7D

The last check completed an MCP handshake.

Registry name
io.shipwork/seo-checks
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
469 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Inspect public websites for technical SEO, indexing, sitemap, redirect, and schema issues.
Listing
From the official MCP registry (active).
Recent checks of Shipwork SEO Checks
CheckedResultHandshake
18 minutes agoHandshake completed469 ms
9 days agoHandshake completed338 ms
9 days agoHandshake completed247 ms
11 days agoHandshake completed242 ms
12 days agoHandshake completed444 ms
13 days agoHandshake completed334 ms
14 days agoHandshake completed254 ms
14 days agoHandshake completed82 ms
16 days agoHandshake completed94 ms
19 days agoHandshake completed521 ms
21 days agoHandshake completed44 ms
24 days agoHandshake completed293 ms
26 days agoHandshake completed230 ms
28 days agoHandshake completed291 ms

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

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