MCP server

Every call is authenticated and metered — including list_checks. Send your key in the x-api-key header:

x-api-key: seoast_sk_1a2b3c4d_YOUR_KEY_SECRET

Authorization: Bearer <key> is accepted as an alternative, for clients whose config only exposes a bearer field. If you send both, they must carry the same key — a disagreement between the two headers is rejected rather than resolved by precedence.

A call carrying no key at all falls back to the anonymous tier, metered per client address at 10 requests a day. A call carrying an unrecognised, malformed or revoked key is refused outright rather than quietly downgraded — presenting a credential that does not resolve is an error, not the absence of one. The tool result says which of those happened.

Add the server once from the terminal:

claude mcp add seoast https://seoast.ai/api/mcp \
  --transport http \
  --header "x-api-key: seoast_sk_1a2b3c4d_YOUR_KEY_SECRET"

Or commit it to the project so the whole team picks it up, by writing .mcp.json at the repository root:

{
  "mcpServers": {
    "seoast": {
      "type": "http",
      "url": "https://seoast.ai/api/mcp",
      "headers": {
        "x-api-key": "seoast_sk_1a2b3c4d_YOUR_KEY_SECRET"
      }
    }
  }
}

Confirm the connection with /mcp inside Claude Code. The server reports itself as seoast with two tools.

Add the server to ~/.cursor/mcp.json for every project, or to .cursor/mcp.json inside a single project:

{
  "mcpServers": {
    "seoast": {
      "url": "https://seoast.ai/api/mcp",
      "headers": {
        "x-api-key": "seoast_sk_1a2b3c4d_YOUR_KEY_SECRET"
      }
    }
  }
}

Cursor picks the file up on save; the server appears under Settings → MCP, where the two tools can be toggled individually.

Each tool call spends one request from the presented key's daily allowance, which resets at 00:00 UTC. Anonymous callers are metered against a hash of the client address the platform reports; where the platform reports none, the call is refused rather than served unmetered. An audit whose target host is unreachable still spends the request — the crawl was attempted, and metering after the fact would let the crawler be used for free.

Every successful tool result ends with the quota line — used, remaining, and the reset timestamp — so an agent can pace itself without a second call.

15 checks run against the server-rendered HTML of the URL you pass. Each one returns pass, warn, fail, or not measurable; a check that could not be measured is excluded from the score rather than counted as a zero, so the number always reads as a percentage of what was actually assessable.

• title — Title tag
• meta_description — Meta description
• canonical — Canonical URL
• robots_meta — Robots meta directives
• open_graph — Open Graph tags
• twitter_card — X (Twitter) card
• heading_hierarchy — Heading hierarchy
• image_alt — Image alt text
• image_dimensions — Image dimensions (layout shift)
• internal_linking — Internal linking
• structured_data — Structured data (JSON-LD)
• html_lang — HTML lang attribute
• viewport — Viewport meta tag
• content_readability — Content depth and readability
• h1_title_alignment — H1 and title alignment

Call list_checks for the full description of each one, including the thresholds it uses and its weight in the score.

A plain HTTP request is enough to confirm the endpoint and the key before wiring up a client. This lists the tools without spending quota, because tools/list is a protocol call rather than a tool call:

curl -sS https://seoast.ai/api/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "x-api-key: seoast_sk_1a2b3c4d_YOUR_KEY_SECRET" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'