Shipwork SEO Checks
REMOTE · SHIPWORK.IO
Inspect public websites for technical SEO, indexing, sitemap, redirect, and schema issues.
Available components
Last scanned (1 hour ago)
Scores higher than 0% of remote servers
Reachable. Last reached 27 Sep 2026.
Category Marketing and SEO
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security0
- TLS not yet verified: the listed URL is a template whose token variable has no value or default, so there was no address for us to check.Unverified
- Authorisation not yet verified: the listed URL is a template whose token variable has no value or default, so there was no address for us to check.Unverified
- HTTPS not yet verified: the listed URL is a template whose token variable has no value or default, so there was no address for us to check. View diagnostics → Unverified
- HSTS not yet verified: the listed URL is a template whose token variable has no value or default, so there was no address for us to check.Unverified
- DNSSEC not yet verified: the listed URL is a template whose token variable has no value or default, so there was no address for us to check.Unverified
Transport & Reachability0
- Transport not yet verified: the listed URL is a template whose token variable has no value or default, so there is no address for us to connect to. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 7 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 −65
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 26 Sept 26 65
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 19 Oct 2026 · Probed https://shipwork.io/mcp/{token}
Transports 1 probe
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| http (plaintext) | http://shipwork.io/mcp/%7Btoken%7D | Inconclusive |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_url_status Status codes for a list of URLs ~51
For each URL: the status code, every redirect hop, the final URL, and whether the final page is noindex or canonicalised elsewhere. Up to 25 URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| urls | array | yes | – |
No output schema declared.
No examples provided.
generate_sitemap Generate an XML sitemap ~60
Crawl a site from its home page and return sitemap.xml of its indexable pages, with the reason each other page was left out.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | A public site or page, e.g. example.com or https://example.com/page |
No output schema declared.
No examples provided.
run_check Run one named check ~93
Run a single named check (for example headers, meta, headings, markup, transport, tech, well-known, certificate, dns) on one address. The full list of names is in https://shipwork.io/openapi.json.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Check name, e.g. headers |
| url | string | yes | A public site or page, e.g. example.com or https://example.com/page |
No output schema declared.
No examples provided.
run_site_audit Audit a site ~82
Crawl a set of pages from outside the network and run every check that applies: indexing, robots.txt, sitemap, canonicals, structured data, internal links, AI crawler access and more. Returns each problem with the page and the fix.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | A public site or page, e.g. example.com or https://example.com/page |
No output schema declared.
No examples provided.
score_site Score a site 0-100 ~58
A 0-100 SEO health score and letter grade for a site, with the top fixes and a shareable result page.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | A public site or page, e.g. example.com or https://example.com/page |
No output schema declared.
No examples provided.
How do I install the Shipwork SEO Checks MCP server?
Shipwork SEO Checks is a hosted endpoint at https://shipwork.io/mcp/%7Btoken%7D, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · shipwork.io
claude mcp add --transport http io-shipwork-seo-checks 'https://shipwork.io/mcp/%7Btoken%7D'
What is the Shipwork SEO Checks MCP server?
Shipwork SEO Checks is an MCP server listed in the public MCP registry as io.shipwork/seo-checks. Inspect public websites for technical SEO, indexing, sitemap, redirect, and schema issues. This page covers its hosted endpoint (https://shipwork.io/mcp/{token}).
Is the Shipwork SEO Checks MCP server safe to use?
Shipwork SEO Checks scores 0 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Shipwork SEO Checks MCP server expose?
Shipwork SEO Checks exposes 5 tools: run_site_audit, score_site, check_url_status, generate_sitemap, run_check. Their descriptions and schemas cost roughly 344 tokens of context every time the server is loaded.
Does the Shipwork SEO Checks MCP server require authentication?
Its publisher declares no required credentials for Shipwork SEO Checks. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Shipwork SEO Checks MCP server still maintained?
Shipwork SEO Checks is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.