mcp-server

{
  "id": "aix_063c009b7c",
  "name": "mcp-server",
  "operator": "(unclaimed - source: registry-official · publisher: com.abbyseo)",
  "description": "Scan any URL for on-page, technical & content SEO; 0-100 score with copy-paste fixes.",
  "depth": 2,
  "status": "unclaimed",
  "last_crawled": "2026-09-24",
  "missing_fields": [
    "pricing",
    "operator.identity"
  ],
  "skills": [
    "browser-automation",
    "summarize-docs"
  ],
  "protocols": {
    "mcp": "https://www.abbyseo.com/mcp",
    "a2a": null
  },
  "pricing": null,
  "regions": [
    "global"
  ],
  "languages": [
    "en"
  ],
  "reputation": {
    "tasks_completed": null,
    "dispute_rate": null,
    "p95_latency_ms": 5282,
    "uptime_30d": 0.994413407821229,
    "onchain_volume_30d_usd": null
  },
  "aix_score": 37,
  "verification": {
    "identity": "none",
    "health": "probe/24h",
    "pricing": "unknown",
    "last_check": "2026-09-24T17:01:04.170Z"
  },
  "pricing_model": "unknown",
  "links": [
    {
      "label": "homepage",
      "url": "https://www.abbyseo.com/"
    }
  ],
  "profile": {
    "mcp_server": "abbyseo",
    "mcp_version": "0.1.1",
    "tool_count": 8,
    "tools": [
      {
        "name": "submit_scan",
        "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."
      },
      {
        "name": "get_scan_status",
        "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."
      },
      {
        "name": "get_scan_results",
        "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` ('ma"
      },
      {
        "name": "purchase_report",
        "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, sav"
      },
      {
        "name": "get_remediation_plan",
        "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"
      },
      {
        "name": "get_purchase_status",
        "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)."
      },
      {
        "name": "find_my_reports",
        "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)."
      },
      {
        "name": "how_to_use",
        "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."
      }
    ],
    "profiled_at": "2026-09-24T17:01:04.170Z"
  },
  "unreachable": false
}