# com.abbyseo/mcp-server (remote · www.abbyseo.com)

Scan any URL for on-page, technical & content SEO; 0-100 score with copy-paste fixes.

- Trust score: 67/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `www.abbyseo.com`: 67/100 (this document), [markdown](https://verifymcp.io/servers/com-abbyseo-mcp-server/www.md), [page](https://verifymcp.io/servers/com-abbyseo-mcp-server/www)

## Channel facts

- Endpoint: `https://www.abbyseo.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (submit_scan).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1605 tokens (~200/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-abbyseo-mcp-server https://www.abbyseo.com/mcp
```

### Codex

```toml
[mcp_servers.com-abbyseo-mcp-server]
url = "https://www.abbyseo.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-abbyseo-mcp-server": {
      "type": "remote",
      "url": "https://www.abbyseo.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-abbyseo-mcp-server --url https://www.abbyseo.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-abbyseo-mcp-server:
    url: "https://www.abbyseo.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-abbyseo-mcp-server": {
      "type": "http",
      "url": "https://www.abbyseo.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 65, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 64, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 63, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 62)

First indexed and scored.

## MCP tools (8)

### `submit_scan` (~159 tokens)

Submit SEO Scan

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.

Input parameters:

- `email` (string, required): 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, required): Full URL of the page to scan (https://example.com). http:// or https:// scheme will be added if missing.

### `get_scan_status` (~100 tokens)

Get SEO Scan Status

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.

Input parameters:

- `scan_id` (string, required): Scan ID from a prior submit_scan call.

### `get_scan_results` (~326 tokens)

Get SEO Scan Results

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` ('marketing' or 'not_marketing') and `score_rubric` ('standard' or 'non_marketing_weighted') so the user understands how the score was computed; non-marketing sites get contextual checks at half-weight, so a forum-style site won't be unfairly penalized for missing landing-page features, (3) if `truncated` is true, surface `truncated_message` so the user knows the API capped the output, (4) include `upgrade.call_to_action` and `upgrade.checkout_url` verbatim so the user can one-click into Stripe checkout for the $8.99 detailed fix guide. If `upgrade.already_purchased` is true, instead direct the user to `upgrade.report_url` to re-download.

Input parameters:

- `scan_id` (string, required): Scan ID from a prior submit_scan call. The scan must be in 'complete' status.

### `purchase_report` (~217 tokens)

Purchase the Full SEO Remediation Guide

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, save the returned markdown to the file it names, and begin the remediation automatically — no further prompting needed. If this call returns already_purchased=true, skip the wait and go straight to get_remediation_plan.

Input parameters:

- `scan_id` (string, required): Scan ID from submit_scan. The scan must be 'complete'.

### `get_remediation_plan` (~198 tokens)

Get the SEO Remediation Plan (Claude Code runbook)

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 has NOT been purchased, returns paid=false with guidance to call `purchase_report` first. If the plan is still generating, returns status='generating' — call again in ~30 seconds.

Input parameters:

- `scan_id` (string, required): Scan ID that was purchased via purchase_report.

### `get_purchase_status` (~127 tokens)

Check SEO Report Purchase Status (lightweight poll)

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).

Input parameters:

- `scan_id` (string, required): Scan ID from submit_scan / purchase_report.

### `find_my_reports` (~136 tokens)

Find My SEO Scans / Reports by Email

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).

Input parameters:

- `email` (string, required): The email address the user used when scanning or purchasing.

### `how_to_use` (~80 tokens)

How to Use Abby SEO

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-abbyseo-mcp-server/www#diagnostics

## Score history

- 2026-08-03: 67
- 2026-08-02: 66
- 2026-08-01: 66
- 2026-07-31: 65
- 2026-07-30: 64
- 2026-07-29: 64
- 2026-07-28: 63
- 2026-07-27: 63
- 2026-07-26: 62

## Links

- Remote endpoint: https://www.abbyseo.com/mcp
- Website: https://www.abbyseo.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-abbyseo-mcp-server/www/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-abbyseo-mcp-server/www/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-abbyseo-mcp-server/www