GEO SEO Records vs ogfetch
GEO SEO Records is an MCP server published by seorecords.com. Marketplaces we read that list it: 1 (Official MCP Registry). ogfetch is an MCP server published by ogfetch.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  GEO SEO Records | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.2 No figure published Not marked · First seen |
Listed Version: 1.0.0 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | GEO SEO Records | ogfetch |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Last release (differs) | 2026-11-09 | Not published |
| Where it runs (differs) | Remote server (api.seorecords.com/mcp/geo) | Remote server (ogfetch.dev/v1/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository | Not stated | Not stated |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen (differs) | 2026-10-16 | 2026-11-03 |
| Endpoint at the last check (differs) | Responded 13 h ago | Status out of date: last check 33 h ago returned HTTP 405 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
GEO SEO Records
Gets a website ready for AI assistants: robots.txt fixed, llms.txt drafted (access pass).
ogfetch
URL to JSON metadata: title, Open Graph, favicon, tech stack. Agents self-signup and pay in USDC.
How to run each
GEO SEO Records As a remote MCP server
claude mcp add --transport http geo-seo-records https://api.seorecords.com/mcp/geo --header "x-access-key: <YOUR_X_ACCESS_KEY>"Requires: x-access-key header
ogfetch As a remote MCP server
claude mcp add --transport http ogfetch https://ogfetch.dev/v1/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints responded at the last daily check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: GEO SEO Records · What it can do: ogfetch · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.