_ registry / mcp streamable-http · checked 3h ago

shipwork

https://shipwork.io

Registry code: 12c9fe077f1a29e9

api record

Shipwork inspects public websites the way Google and AI crawlers see them. Start with run_site_audit for a whole-site picture; use run_check for one question. Report must-fix items first. Calls run as the Shipwork account this address belongs to, with its weekly allowance.

endpoint
https://shipwork.io/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is shipwork live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is shipwork free to use?
Yes — the hub reached it with no key and no payment.
What tools does shipwork have?
5 tools: check_url_status, run_site_audit, score_site, generate_sitemap, run_check.
Is shipwork safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.7%· all time 99.7%

latency
447ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 348 checks · signed record
  • down → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
used for
  • run a site seo audit
  • check url status and redirects
  • generate a sitemap for a site
  • get an seo health score
takes → gives
web pages → data, code
tools
5 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 5 tools
5 never probed 0 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • check_url_status reads unknown 6h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "urls"
      ],
      "properties": {
        "urls": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 100
        }
      }
    }
    arguments 15 lines
  • run_site_audit reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "A public site or page, e.g. example.com or https://example.com/page"
        }
      }
    }
    arguments 12 lines
  • score_site reads unknown never probed

    A 0-100 SEO health score and letter grade for a site, with the top fixes and a shareable result page.

    mcp-tool

    {
      "type": "object",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "A public site or page, e.g. example.com or https://example.com/page"
        }
      }
    }
    arguments 12 lines
  • generate_sitemap reads unknown never probed

    Crawl a site from its home page and return sitemap.xml of its indexable pages, with the reason each other page was left out.

    mcp-tool

    {
      "type": "object",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "A public site or page, e.g. example.com or https://example.com/page"
        }
      }
    }
    arguments 12 lines
  • run_check reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name",
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "A public site or page, e.g. example.com or https://example.com/page"
        },
        "name": {
          "type": "string",
          "description": "Check name, e.g. headers"
        }
      }
    }
    arguments 17 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 12c9fe077f1a29e9.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/12c9fe077f1a29e9/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/12c9fe077f1a29e9/badge.svg)](https://brick.blue/agent/12c9fe077f1a29e9?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.