SEO Records
REMOTE · API.SEORECORDS.COM
SEO check of any website and AI crawler access test (access pass), and the full Audit.
Available components
Last scanned (2 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 31 Oct 26 +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.
- 29 Oct 26 +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.
- 28 Oct 26 0
- 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 security
- “check_ai_crawler_access” reworded the description of “access_key” cosmetic
- “check_website_seo” reworded the description of “access_key” cosmetic
- 27 Oct 26 0
- 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 security
- Schema quality: 193 → 224 ▼ functional
- Server version: 1.2.0 → 1.3.0 functional
- “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 cosmetic
- 26 Oct 26 +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.
- 24 Oct 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://api.seorecords.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.seorecords.com | CN=YR2,O=Let's Encrypt,C=US | 31 Oct 2026 | 29 Jan 2027 | RSA 2048 | SHA256-RSA | 649d7072e4fd5c2e3461d4dbab3c5a7ce1c |
| SANs: api.seorecords.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.seorecords.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| seorecords.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.seorecords.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.seorecords.com/mcp | HTTPS enforced | 308 | https://api.seorecords.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_ai_crawler_access Can AI assistants read this website? ~177
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
| Name | Type | Req | Description |
|---|---|---|---|
| access_key | string | – | Access key (pass_…) of this connector, shown after buying its 24-hour pass or monthly subscription. Required. |
| url | string | yes | The website address, e.g. example.com |
No output schema declared.
No examples provided.
check_website_seo SEO check of a website ~193
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
| Name | Type | Req | Description |
|---|---|---|---|
| access_key | string | – | Access key (pass_…) of this connector, shown after buying its 24-hour pass or monthly subscription. Required. |
| url | string | yes | The website address, e.g. example.com or https://example.com/ |
No output schema declared.
No examples provided.
get_full_audit_checkout Payment link for the full Audit SEO Records ~198
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
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The website to audit |
No output schema declared.
No examples provided.
get_product_offer SEO Records products: offer and payment links ~216
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
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Language of the product pages (default en) |
| product | string | yes | Product id, or all |
No output schema declared.
No examples provided.
read_audit_report Read a purchased Audit SEO Records report ~148
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
| Name | Type | Req | Description |
|---|---|---|---|
| report | string | yes | The report link (https://seorecords.com/audit?id=…) or its identifier |
No output schema declared.
No examples provided.
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.
remote · api.seorecords.com
claude mcp add --transport http com-seorecords-seo-records 'https://api.seorecords.com/mcp'
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.