Server definition

Hash: sha256:777d9702df81769fa9beeb907160ab433470da1c7afdc50b5397ee3effe4f367
What it is: What a remote MCP server returned when asked what it offers: 8 tools

The blob, as servednamed by its sha256

{
  "instructions": "Abby SEO scans any site for 20 SEO checks and produces an executable fix plan. Returning user with no scan_id (scanned earlier or bought on the website)? Call find_my_reports(email) first to look it up. FREE tier: submit_scan(url, email) (ask the user for their email FIRST) → poll get_scan_status to 'complete' → get_scan_results returns the score + top issues ONLY. PAID tier ($8.99) unlocks the full plan covering ALL issues: purchase_report(scan_id) → show the user the Stripe checkout_url → poll get_purchase_status (~15s) until paid (don't wait for a new prompt) → get_remediation_plan(scan_id). Save its markdown as seo-remediation-plan.md and execute it: priority-ordered fixes, copy-ready replacements, '❓ ASK THE OWNER' stops (never invent brand, keyword, or contact details), re-scan via submit_scan to verify. Payment is browser-only — it can't be collected through these tools. New here? The 'getting_started' prompt (or the how_to_use tool) returns a plain-English usage guide with example requests — in Claude Code the prompt is /mcp__abbyseo__getting_started; if a client doesn't surface prompts, call how_to_use.",
  "tools": [
    {
      "description": "Look up a user's recent SEO scans by the email they used — for RETURNING users who don't have a scan_id handy (scanned/purchased earlier or on the website). In a fresh session where the user has no scan_id, START HERE: ask the user for that email, then call this. Returns up to 10 recent scans as {scan_id, url, scanned_at, paid, runbook_ready}. Then use the scan_id with get_remediation_plan (if paid+runbook_ready) or purchase_report (if not paid).",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "email": {
            "description": "The email address the user used when scanning or purchasing.",
            "format": "email",
            "type": "string"
          }
        },
        "required": [
          "email"
        ],
        "type": "object"
      },
      "name": "find_my_reports",
      "outputSchema": null
    },
    {
      "description": "Lightweight poll for whether a scan's paid remediation report is ready, WITHOUT downloading the full plan. Use this in the wait loop after `purchase_report`: call about every 15 seconds until both `paid` and `runbook_ready` are true, then call `get_remediation_plan` ONCE to fetch and execute the plan. `paid=false` => the user hasn't completed checkout yet; `paid=true, runbook_ready=false` => payment landed and the plan is still being generated (retry shortly).",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "scan_id": {
            "description": "Scan ID from submit_scan / purchase_report.",
            "type": "string"
          }
        },
        "required": [
          "scan_id"
        ],
        "type": "object"
      },
      "name": "get_purchase_status",
      "outputSchema": null
    },
    {
      "description": "Retrieve the full paid remediation plan for a purchased scan, as a Markdown runbook built for an AI coding agent to execute. **Save the returned `markdown` to a file named by `filename` (e.g. seo-remediation-plan.md) in the user's project, then work through it top to bottom.** It lists each issue in priority order with the exact fix, copy-ready replacement strings, explicit '❓ ASK THE OWNER' stops where you must get the owner's input (never invent brand names, keywords, phone numbers, or addresses), and a verification step (re-run `submit_scan` after each fix to confirm it passes). If the scan has NOT been purchased, returns paid=false with guidance to call `purchase_report` first. If the plan is still generating, returns status='generating' — call again in ~30 seconds.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "scan_id": {
            "description": "Scan ID that was purchased via purchase_report.",
            "type": "string"
          }
        },
        "required": [
          "scan_id"
        ],
        "type": "object"
      },
      "name": "get_remediation_plan",
      "outputSchema": null
    },
    {
      "description": "Fetch the full structured scan findings. Free tier returns the top 5 issues by severity (failed > warned > passed); paid customers see all checks. When summarizing results to the user, ALWAYS: (1) report the score and counts of failed/warned/passed checks, (2) surface each returned check's `remediation` text verbatim, (2b) for sophisticated users, mention each check's `when_doesnt_apply` context so they can dismiss findings that don't apply to their site type (e.g., link aggregators legitimately omit a visible H1; empty string means the rule is universally required), (2c) note `site_type` ('marketing' or 'not_marketing') and `score_rubric` ('standard' or 'non_marketing_weighted') so the user understands how the score was computed; non-marketing sites get contextual checks at half-weight, so a forum-style site won't be unfairly penalized for missing landing-page features, (3) if `truncated` is true, surface `truncated_message` so the user knows the API capped the output, (4) include `upgrade.call_to_action` and `upgrade.checkout_url` verbatim so the user can one-click into Stripe checkout for the $8.99 detailed fix guide. If `upgrade.already_purchased` is true, instead direct the user to `upgrade.report_url` to re-download.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "scan_id": {
            "description": "Scan ID from a prior submit_scan call. The scan must be in 'complete' status.",
            "type": "string"
          }
        },
        "required": [
          "scan_id"
        ],
        "type": "object"
      },
      "name": "get_scan_results",
      "outputSchema": null
    },
    {
      "description": "Check whether a queued scan has completed. Lightweight polling endpoint — call every 3-5 seconds with the `scan_id` returned by `submit_scan`. Scans typically complete in 5-15 seconds. When `status` is 'complete', call `get_scan_results` for the structured findings. When 'failed', surface the `error` field to the user.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "scan_id": {
            "description": "Scan ID from a prior submit_scan call.",
            "type": "string"
          }
        },
        "required": [
          "scan_id"
        ],
        "type": "object"
      },
      "name": "get_scan_status",
      "outputSchema": null
    },
    {
      "description": "Returns a plain-English usage guide for this server — example requests, what it asks the user for, and the available tools. Call this if the user asks how to use Abby SEO, or to orient yourself before starting. (Same content as the 'getting_started' prompt, exposed as a tool for clients that don't surface MCP prompts.) Takes no arguments.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {},
        "type": "object"
      },
      "name": "how_to_use",
      "outputSchema": null
    },
    {
      "description": "Start a purchase of the full paid SEO Remediation Guide for a COMPLETE scan ($8.99). Returns a Stripe `checkout_url` — payment CANNOT be collected through this tool. AUTONOMOUS FLOW: after calling this, do NOT stop and wait for a new user instruction. (1) Show the user `checkout_url` and ask them to complete payment in their browser. (2) Then poll `get_purchase_status` with the same scan_id about every 15 seconds: while `paid` is false the user hasn't finished — keep waiting (poll for up to a few minutes). (3) Once `paid` and `runbook_ready` are both true, call `get_remediation_plan` once, save the returned markdown to the file it names, and begin the remediation automatically — no further prompting needed. If this call returns already_purchased=true, skip the wait and go straight to get_remediation_plan.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "scan_id": {
            "description": "Scan ID from submit_scan. The scan must be 'complete'.",
            "type": "string"
          }
        },
        "required": [
          "scan_id"
        ],
        "type": "object"
      },
      "name": "purchase_report",
      "outputSchema": null
    },
    {
      "description": "Queue an SEO scan of a website URL. Returns a scan_id to poll. **You MUST collect the user's email address before calling this tool** — the API rejects submissions without one because results are emailed to the user. After this tool returns, call `get_scan_status` every few seconds with the returned `scan_id` until status is 'complete', then call `get_scan_results` for the findings.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "email": {
            "description": "REQUIRED. The user's email address. Scan results will be sent here. ASK THE USER for this if you don't already know it — do not invent a placeholder.",
            "format": "email",
            "type": "string"
          },
          "url": {
            "description": "Full URL of the page to scan (https://example.com). http:// or https:// scheme will be added if missing.",
            "format": "uri",
            "type": "string"
          }
        },
        "required": [
          "url",
          "email"
        ],
        "type": "object"
      },
      "name": "submit_scan",
      "outputSchema": null
    }
  ]
}

Verify it yourself

curl -s https://api.teppi.xyz/v1/evidence/sha256:777d9702df81769fa9beeb907160ab433470da1c7afdc50b5397ee3effe4f367 | sha256sum