ENDPOINT 1
https://www.abbyseo.com/mcp
MCP server metadata
- Name
- abbyseo
- Version
- 0.1.1
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.
Known tools 8
purchase_reportStart a purchase of the full paid SEO Remediation Guide for a COMPLETE scan ($8.
Potential side effectsget_remediation_planRetrieve the full paid remediation plan for a purchased scan, as a Markdown runbook built for an AI coding agent to execute.
Potential side effectsget_purchase_statusLightweight poll for whether a scan's paid remediation report is ready, WITHOUT downloading the full plan.
Inferred read-onlyfind_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).
Potential side effectshow_to_useReturns a plain-English usage guide for this server — example requests, what it asks the user for, and the available tools.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.abbyseo]
url = "https://www.abbyseo.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"abbyseo": {
"type": "http",
"url": "https://www.abbyseo.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: abbyseo
Remote MCP URL: https://www.abbyseo.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"abbyseo": {
"url": "https://www.abbyseo.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"abbyseo": {
"type": "http",
"url": "https://www.abbyseo.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "abbyseo",
"transport": "streamable-http",
"url": "https://www.abbyseo.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for abbyseo.com was fetched 2026-07-31T15:51:40.971Z and is being refreshed.
abbyseo.com is assessed as Neutral: No suspicious signals found, but no strong positive signal either
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.