All servers · Marketing & SEO
com.abbyseo/mcp-server
com.abbyseo/mcp-server · v0.2.0
Has write/delete toolsNo registry update 90+ days
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2024-11-05 |
| Rank score | — |
| Declared risk | Has destructive tools (destructiveHint) |
| Capabilities declared | prompts, tools |
| Tool definitions | 8 tools · with description 100% · input schema is an object 100% · read/destructive hints 100% |
Description written by the publisher, not verified
Scan any URL for on-page, technical & content SEO; 0-100 score with copy-paste fixes.
Connect
streamable-http · https://www.abbyseo.com/mcp
claude mcp add --transport http mcp-server https://www.abbyseo.com/mcp{
"mcpServers": {
"mcp-server": {
"url": "https://www.abbyseo.com/mcp"
}
}
}Tools as reported by the server
submit_scanwrite/deleteQueue 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 returnedget_scan_statusCheck 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 `errorget_scan_resultsFetch 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 `remediatpurchase_reportStart 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 toget_remediation_planRetrieve 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 inget_purchase_statusLightweight 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 plafind_my_reportsLook 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 {schow_to_useReturns 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 s
Website · JSON · Text for agents · Registry updated 2026-07-14