Google Search Console integration for Model Context Protocol (MCP)
Nothing to run from here
AbbySEO is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
8
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
SEO scanner that audits any URL across 20 technical and on-page checks and returns an executable fix plan.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http abbyseo-mcp https://www.abbyseo.com/mcp
# 2 — ask your agent for something these tools do
# submit_scan, get_scan_status, get_scan_results and 5 more
AbbySEO costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
ACAll 1 server
abbyseo.com1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http abbyseo-mcp https://www.abbyseo.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | yes | 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. | |
| url | string | yes | Full URL of the page to scan (https://example.com). http:// or https:// scheme will be added if missing. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scan_id | string | yes | Scan ID from a prior submit_scan call. |
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 s
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scan_id | string | yes | Scan ID from a prior submit_scan call. The scan must be in 'complete' status. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scan_id | string | yes | Scan ID from submit_scan. The scan must be 'complete'. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scan_id | string | yes | Scan ID that was purchased via purchase_report. |
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 => payme
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scan_id | string | yes | Scan ID from submit_scan / purchase_report. |
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 pai
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | yes | The email address the user used when scanning or purchasing. |
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.
No parameter schema on file.
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install AbbySEO or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.2.0.
0.2.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish AbbySEO can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.