Shipwork SEO Checks is a remote MCP server that gives an AI agent 5 tools, among them check_url_status, generate_sitemap, run_check. It answers at https://shipwork.io/mcp/{token} over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 27 September 2026; the last check, on 11 November 2026, succeeded.
Inspect public websites for technical SEO, indexing, sitemap, redirect, and schema issues.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
check_url_status | For each URL: the status code, every redirect hop, the final URL, and whether the final page is noindex or canonicalised elsewhere. Up to 100 URLs. Inputs: urls |
generate_sitemap | Crawl a site from its home page and return sitemap.xml of its indexable pages, with the reason each other page was left out. Inputs: url |
run_check | 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. Inputs: name, url |
run_site_audit | 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. Inputs: url |
score_site | A 0-100 SEO health score and letter grade for a site, with the top fixes and a shareable result page. Inputs: url |
Every block below points at https://shipwork.io/mcp/{token}. Pick your client and copy.
claude mcp add --transport http shipwork-seo-checks https://shipwork.io/mcp/{token}{
"mcpServers": {
"shipwork-seo-checks": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://shipwork.io/mcp/{token}"]
}
}
}{
"mcpServers": {
"shipwork-seo-checks": {
"url": "https://shipwork.io/mcp/{token}"
}
}
}{
"servers": {
"shipwork-seo-checks": {
"type": "http",
"url": "https://shipwork.io/mcp/{token}"
}
}
}{
"context_servers": {
"shipwork-seo-checks": {
"url": "https://shipwork.io/mcp/{token}"
}
}
}{
"mcpServers": {
"shipwork-seo-checks": {
"serverUrl": "https://shipwork.io/mcp/{token}"
}
}
}{
"mcpServers": {
"shipwork-seo-checks": {
"url": "https://shipwork.io/mcp/{token}"
}
}
}name: Shipwork SEO Checks
version: 0.0.1
schema: v1
mcpServers:
- name: Shipwork SEO Checks
type: streamable-http
url: https://shipwork.io/mcp/{token}{
"mcpServers": {
"shipwork-seo-checks": {
"httpUrl": "https://shipwork.io/mcp/{token}"
}
}
}{
"mcpServers": {
"shipwork-seo-checks": {
"type": "http",
"url": "https://shipwork.io/mcp/{token}"
}
}
}{
"mcpServers": {
"shipwork-seo-checks": {
"url": "https://shipwork.io/mcp/{token}"
}
}
}goose://extension?url=https%3A%2F%2Fshipwork.io%2Fmcp%2F%7Btoken%7D&type=streamable_http&id=shipwork-seo-checks&name=Shipwork%20SEO%20Checks
It answered our last check on 11 November 2026 in 285 ms. Over 4 checks since 27 September 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by shipwork.io and served from shipwork.io, the vendor's own domain: https://shipwork.io/mcp/{token}.
5, as returned by the server's own tools/list on 16 November 2026: check_url_status, generate_sitemap, run_check, run_site_audit, score_site.
It answered our last check on 11 November 2026 in 285 ms. Over 4 checks since 27 September 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://shipwork.io/mcp/{token}. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.shipwork. Endpoint host: shipwork.io. ARD identifier: urn:air:io.shipwork:mcp:seo-checks.
First indexed 26 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.