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

SEO check of any website and AI crawler access test (access pass), and the full Audit.

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

## Components

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

## Channel facts

- Endpoint: `https://api.seorecords.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.3.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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - 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**: 66/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1107 tokens (~221/item across 5 items; 5 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 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 MCP server?

SEO Records is a hosted endpoint at https://api.seorecords.com/mcp, 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 'https://api.seorecords.com/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "com-seorecords-seo-records": {
      "type": "http",
      "url": "https://api.seorecords.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-11-04 (score 81, +1)

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

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

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

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

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

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

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

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

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “check_ai_crawler_access” rewrote its description, which is the text the model reads
- [security] Tool “check_website_seo” rewrote its description, which is the text the model reads
- [cosmetic] “check_ai_crawler_access” reworded the description of “access_key”
- [cosmetic] “check_website_seo” reworded the description of “access_key”

### 2026-10-27 (score 77, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “check_ai_crawler_access” rewrote its description, which is the text the model reads
- [security] Tool “check_website_seo” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 193 → 224
- [functional] Server version: 1.2.0 → 1.3.0
- [cosmetic] “check_ai_crawler_access” added an optional parameter “access_key”
- [cosmetic] “check_website_seo” added an optional parameter “access_key”
- [cosmetic] Tool “check_website_seo” changed its title: Free SEO check of a website → SEO check of a website

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

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

### 2026-10-24 (score 76, +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.

## MCP tools (5)

### `check_website_seo` (~193 tokens)

SEO check of a website

Reads the public home page of a website and a few pages from its sitemap, the way a search engine does, and returns the SEO problems found (duplicate titles and descriptions, thin content, missing h1, noindex in sitemap, robots.txt, sitemap, http/www variants, compression, mixed content…), the Google snippet as it appears today and where Google cuts it, and the fixes the SEO Records corrector would apply. About 10–20 seconds, nothing is stored. 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 website address, e.g. example.com or https://example.com/

### `check_ai_crawler_access` (~177 tokens)

Can AI assistants read this website?

Checks whether ChatGPT, Claude, Perplexity, Copilot, Google (Gemini) and Mistral Le Chat can read a website: robots.txt rules for each AI crawler (certain), the home page requested as each crawler versus a normal browser (probable — real crawlers come from other IPs), and page-level blockers (noindex, nosnippet, JavaScript-only pages). Nothing is stored. 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 website address, e.g. example.com

### `get_full_audit_checkout` (~198 tokens)

Payment link for the full Audit SEO Records

Creates a secure Stripe payment page for the full Audit SEO Records of a website (whole site crawled, 152 signals with their URLs, PDF report, re-check in one click). One-time payment: €9.90 (1,000 pages), €19.90 (2,500), €29.90 (5,000), €39.90 (7,500), €49.90 (10,000). Nothing is charged until the user pays on the Stripe page. Intended for users who ask to buy the full audit. Docs: https://seorecords.com/assistants

Input parameters:

- `language` (string): Language of the payment page and report (default en)
- `pages` (integer): Audit size in pages: 1000, 2500, 5000, 7500 or 10000 (default 1000)
- `url` (string, required): The website to audit

### `get_product_offer` (~216 tokens)

SEO Records products: offer and payment links

Returns what a SEO Records product does, its platforms, its prices and its secure Stripe payment links (the user pays on Stripe). Products: seo-records-corrector (fixes SEO at serve time, WordPress/PrestaShop/Joomla/Drupal/PHP, from €199/year), seo-autopilot (writes descriptions, FAQs and internal links from real catalog data, PrestaShop, from €199/year), duo (both modules, from €339/year), seo-outpost (the corrector at the network edge, any hosting, from €199 for a year), geo-seo-records (opens and measures the AI assistants channel, from €490 for a year), effect-seo-records (monthly whole-site crawl and difference over a year, from €149 for a year); all returns every product. Docs: https://seorecords.com/assistants

Input parameters:

- `language` (string): Language of the product pages (default en)
- `product` (string, required): Product id, or all

### `read_audit_report` (~148 tokens)

Read a purchased Audit SEO Records report

Reads an Audit SEO Records report (or an Effect SEO Records monthly crawl) from the private link its buyer received (https://seorecords.com/audit?id=…): status and progress while the crawl runs; once finished, every signal found with its family, severity, number of pages and example URLs, the difference with the previous audit of the same site, and the yearly curve for Effect customers. Pages cited can then be fixed one by one with the SEO Records Corrector connector. Docs: https://seorecords.com/assistants

Input parameters:

- `report` (string, required): The report link (https://seorecords.com/audit?id=…) or its identifier

## Diagnostics

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

## Score history

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

## Common questions

### What is the SEO Records MCP server?

SEO Records is an MCP server listed in the public MCP registry as com.seorecords/seo-records. SEO check of any website and AI crawler access test (access pass), and the full Audit. This page covers its hosted endpoint (https://api.seorecords.com/mcp).

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

SEO Records scores 81 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 MCP server expose?

SEO Records exposes 5 tools: check_website_seo, check_ai_crawler_access, get_full_audit_checkout, get_product_offer, read_audit_report. Their descriptions and schemas cost roughly 932 tokens of context every time the server is loaded.

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

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

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

SEO Records 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.

## Links

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