# SEO Records Corrector (remote · api.seorecords.com)

Fixes the SEO of any public page: each correction with its value, source and exact HTML tag.

- Trust score: 82/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api.seorecords.com`: 82/100 (this document), [markdown](https://verifymcp.io/servers/com-seorecords-seo-records-corrector/mcp-corrector.md), [page](https://verifymcp.io/servers/com-seorecords-seo-records-corrector/mcp-corrector)

## Channel facts

- Endpoint: `https://api.seorecords.com/mcp/corrector`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 473 tokens (~236/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 67/100
  - Stability observed for 20 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the SEO Records Corrector MCP server?

SEO Records Corrector is a hosted endpoint at https://api.seorecords.com/mcp/corrector, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-seorecords-seo-records-corrector 'https://api.seorecords.com/mcp/corrector'
```

### Cursor

```json
{
  "mcpServers": {
    "com-seorecords-seo-records-corrector": {
      "url": "https://api.seorecords.com/mcp/corrector"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-seorecords-seo-records-corrector": {
      "type": "http",
      "url": "https://api.seorecords.com/mcp/corrector"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-seorecords-seo-records-corrector]
url = "https://api.seorecords.com/mcp/corrector"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-seorecords-seo-records-corrector": {
      "type": "remote",
      "url": "https://api.seorecords.com/mcp/corrector",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-seorecords-seo-records-corrector --url 'https://api.seorecords.com/mcp/corrector' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-seorecords-seo-records-corrector:
    url: "https://api.seorecords.com/mcp/corrector"
```

### Netclaw

```json
{
  "McpServers": {
    "com-seorecords-seo-records-corrector": {
      "Transport": "http",
      "Url": "https://api.seorecords.com/mcp/corrector"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-seorecords-seo-records-corrector -t streamable-http -u 'https://api.seorecords.com/mcp/corrector'
```

### Other

```json
{
  "mcpServers": {
    "com-seorecords-seo-records-corrector": {
      "type": "http",
      "url": "https://api.seorecords.com/mcp/corrector"
    }
  }
}
```

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-11-05 (score 82, +1)

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

### 2026-11-03 (score 81, +1)

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

### 2026-11-01 (score 80, +1)

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

### 2026-10-30 (score 79, +1)

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

### 2026-10-28 (score 78, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “fix_page_seo” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 191 → 236
- [functional] Schema quality: good → excellent
- [functional] Server version: 1.0.0 → 1.1.0
- [cosmetic] “fix_page_seo” added an optional parameter “access_key”

### 2026-10-27 (score 78, +1)

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

### 2026-10-25 (score 77, +1)

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

### 2026-10-23 (score 76, +1)

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

## MCP tools (2)

### `fix_page_seo` (~220 tokens)

Fix the SEO of a web page

Runs the SEO Records correction engine (the one inside the SEO Records module) on a public page and returns every correction it would apply: the value, the source it comes from, and the exact HTML tag to add or replace in <head> — title, meta description, canonical URL, hreflang, Open Graph and Twitter preview, JSON-LD structured data, image alt texts, robots directives. Also returns the Google snippet before and after, and the issues left to the author because they touch visible content (missing h1, vague link texts…). The page is read, corrected in memory, and forgotten. Requires this connector's access pass (€9.90 for 24 hours, or €29 per month). Docs: https://seorecords.com/assistants

Input parameters:

- `access_key` (string): Access key (pass_…) of this connector, shown after buying its 24-hour pass or monthly subscription. Required.
- `url` (string, required): The page address, e.g. example.com/page or https://example.com/

### `get_automatic_fix_offer` (~112 tokens)

Apply the fixes automatically: offer and payment links

Returns the SEO Records products that apply these corrections automatically on every page: the SEO Records module (WordPress, PrestaShop, Joomla, Drupal, custom PHP; from €199/year) and SEO Outpost (the same corrections at the network edge, any hosting; from €199 for a year), with what each does, prices and secure Stripe payment links. Docs: https://seorecords.com/assistants

Input parameters:

- `language` (string): Language of the product pages (default en)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-seorecords-seo-records-corrector/mcp-corrector#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 81
- 2026-11-03: 81
- 2026-11-02: 80
- 2026-11-01: 80
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 78
- 2026-10-28: 78
- 2026-10-27: 78
- 2026-10-26: 77
- 2026-10-25: 77
- 2026-10-24: 76
- 2026-10-23: 76
- 2026-10-22: 75
- 2026-10-21: 75
- 2026-10-20: 74
- 2026-10-19: 74
- 2026-10-18: 74
- 2026-10-17: 73
- 2026-10-16: 73

## Common questions

### What is the SEO Records Corrector MCP server?

SEO Records Corrector is an MCP server listed in the public MCP registry as com.seorecords/seo-records-corrector. Fixes the SEO of any public page: each correction with its value, source and exact HTML tag. This page covers its hosted endpoint (https://api.seorecords.com/mcp/corrector).

### Is the SEO Records Corrector MCP server safe to use?

SEO Records Corrector scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the SEO Records Corrector MCP server expose?

SEO Records Corrector exposes 2 tools: fix_page_seo, get_automatic_fix_offer. Their descriptions and schemas cost roughly 332 tokens of context every time the server is loaded.

### Does the SEO Records Corrector MCP server require authentication?

No. We connected to SEO Records Corrector without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the SEO Records Corrector MCP server still maintained?

SEO Records Corrector is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the SEO Records Corrector MCP server?

VerifyMCP ran 13 checks on SEO Records Corrector, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://api.seorecords.com/mcp/corrector
- Website: https://seorecords.com/assistants
- Changelog RSS feed: https://verifymcp.io/servers/com-seorecords-seo-records-corrector/mcp-corrector.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-seorecords-seo-records-corrector/mcp-corrector/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-seorecords-seo-records-corrector/mcp-corrector.json
- HTML version of this page: https://verifymcp.io/servers/com-seorecords-seo-records-corrector/mcp-corrector