Skip to content
External endpointresponds

mcp-server

Scan any URL for 20 SEO checks; get a 0-100 score with prioritized fix recommendations.

Endpoint URL
https://www.abbyseo.com/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:08 AM UTC
Check
MCP initialize · 8s limit
Latency
173 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
com.abbyseo/mcp-server

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
abbyseo
Version
0.1.1
Capability keys
prompts, tools
Tool names
submit_scan, get_scan_status, get_scan_results, purchase_report, get_remediation_plan, get_purchase_status, find_my_reports, how_to_use
Instructions excerpt

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 g

Reported Aug 17, 2026, 05:08 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 344ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 182ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 118ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 173ms