GEO SEO Records MCP Server

by seorecords Your server? Claim it

answering

GEO SEO Records is answering right now. Last checked 12 min ago. It exposes 4 tools.

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

Uptime history 8 hours of history

8 hours agonow

100.0%

Uptime 24h

28 of 28 checks

Tools

read from the server

318 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check GEO SEO Records every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add geo-seo-records --transport http https://api.seorecords.com/mcp/geo

~/Library/Application Support/Claude/claude_desktop_config.json

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

~/.codex/config.toml

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

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

draft

draft_llms_txt

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

geo

get_geo_offer

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

open

open_robots_txt_to_ai

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

readiness

check_ai_readiness

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

Endpoints

URL	Transport	State	Latency	Checked
https://api.seorecords.com/mcp/geo	streamable-http	answering	210 ms	12 min ago

Alternatives to GEO SEO Records

same job, measured the same way

AI SEO

by automatelab-tech

MCP server for AI-SEO auditing: schema, robots.txt, llms.txt, citation scoring, and AEO/GEO rewrites

65 installs/wk local only

GEO-bot

by feelswebman

Free check whether a website is technically open to AI assistants (AI crawlers, llms.txt, JSON-LD).

1 tools answering

AI Agent Search Optimization

by seyitkaangunes

Audit AI search readiness, generate llms.txt drafts, and build GEO/AEO prompt matrices for websites.

37 installs/wk local only

Citead GEO Score

by citead

Free GEO score of a web page or text: how easily AI assistants can quote it, with fixes. No key.

2 tools answering

Citely

by aicitely

Read-only GEO data: which AI assistants mention a brand and cite its domain.

answering

Causabi GEO Optimizer

by causabi

Audit a site for AI readiness (llms.txt, schema, AI-crawler access) and generate the fixes.

11 installs/wk local only

SEO & GEO

by ortamarco

Audit a page's SEO and its readiness for AI answer engines: meta, schema, robots, sitemaps, AI bots.

264 installs/wk local only

Blck Alpaca Agentic Audit & Knowledge Base

by blckalpaca

Audit a website for AI-agent readiness and GEO. Knowledge base on SEO, GEO and AI agents (de/en/sk).

5 tools answering

GEO SEO Records — questions

Answers built from our own checks of this server.

What can GEO SEO Records do?

It exposes 4 tools, read directly from the server on our last check. Among them: check_ai_readiness, draft_llms_txt, get_geo_offer, open_robots_txt_to_ai. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is GEO SEO Records working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 28 of 28 checks got a reply (100.0%), average response time 318 ms. The bar chart above shows every period we have measured.

How do I connect GEO SEO Records?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does GEO SEO Records need an API key?

No. GEO SEO Records completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is GEO SEO Records?

It answers our handshake in 318 ms on average, which is faster than 42% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.