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

Gets a website ready for AI assistants: robots.txt fixed, llms.txt drafted, citable gaps listed.

- Trust score: 72/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

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

## Channel facts

- Endpoint: `https://api.seorecords.com/mcp/geo`
- 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-10-17.

- **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**: 67/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 643 tokens (~160/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 GEO SEO Records MCP server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

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-10-17 (score 72, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-16 (score 72)

First indexed and scored.

## MCP tools (4)

### `check_ai_readiness` (~143 tokens)

GEO check of a page for AI assistants

Runs the GEO SEO Records engine on a public page and returns the gaps, weighted blocking / important / to decide, across six parts: the door (robots.txt rules for the robots that read for a person), the map (llms.txt present and verifiable), the answer (does the page answer under its title, declared questions), the citable (figures with a source or a date), the publisher identity, and the structure (blocks that stay true when quoted alone). Free. Docs: https://seorecords.com/assistants

Input parameters:

- `url` (string, required): The page address, e.g. example.com or https://example.com/page

### `open_robots_txt_to_ai` (~154 tokens)

Open robots.txt to AI assistants

Reads the site's robots.txt and tells, robot by robot (GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-User, Claude-SearchBot, PerplexityBot, Perplexity-User, DuckAssistBot, Meta, Common Crawl, Google-Extended, Applebot-Extended), whether it may read the site, separating robots that read for a person (live) from robots that harvest for training. Returns the corrected robots.txt that lets the live readers in while keeping the site's existing rules, ready to paste. Docs: https://seorecords.com/assistants

Input parameters:

- `url` (string, required): The website address, e.g. example.com

### `draft_llms_txt` (~117 tokens)

Draft the llms.txt of a website

Builds an llms.txt for a website from facts read on it — the site name and description from its home page, then pages from its sitemap with their titles and meta descriptions, grouped by section — and reviews the existing llms.txt if there is one (declared name, links, claims no machine can verify). The draft is ready to edit and publish at /llms.txt. Docs: https://seorecords.com/assistants

Input parameters:

- `url` (string, required): The website address, e.g. example.com

### `get_geo_offer` (~105 tokens)

GEO SEO Records: offer and payment links

Returns the GEO SEO Records module (WordPress, PrestaShop, network edge; from €490 for a year): what it applies (door, map, answer, publisher) and what it measures (assistant reads certified by IP range, demand read in the log, paying pages joined to revenue), with prices and secure Stripe payment links. Docs: https://seorecords.com/assistants

Input parameters:

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

## Diagnostics

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

## Score history

- 2026-10-17: 72
- 2026-10-16: 72

## Common questions

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

GEO SEO Records is an MCP server listed in the public MCP registry as com.seorecords/geo-seo-records. Gets a website ready for AI assistants: robots.txt fixed, llms.txt drafted, citable gaps listed. This page covers its hosted endpoint (https://api.seorecords.com/mcp/geo).

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

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

GEO SEO Records exposes 4 tools: check_ai_readiness, open_robots_txt_to_ai, draft_llms_txt, get_geo_offer. Their descriptions and schemas cost roughly 519 tokens of context every time the server is loaded.

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

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

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

GEO SEO Records is still listed as active in the MCP registry. We last reached this channel on 17 October 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/geo
- Website: https://seorecords.com/en/assistants
- Changelog RSS feed: https://verifymcp.io/servers/com-seorecords-geo-seo-records/mcp-geo.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-seorecords-geo-seo-records/mcp-geo.json
- HTML version of this page: https://verifymcp.io/servers/com-seorecords-geo-seo-records/mcp-geo