SEO Records Corrector
REMOTE · API.SEORECORDS.COM
Fixes the SEO of any public page: each correction with its value, source and exact HTML tag.
Available components
Last scanned (14 hours ago)
Scores higher than 85% 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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 Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 473 tokens (~236/item across 2 items; 2 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 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 “fix_page_seo” rewrote its description, which is the text the model reads security
- Schema quality: 191 → 236 ▼ functional
- Schema quality: good → excellent functional
- Server version: 1.0.0 → 1.1.0 functional
- “fix_page_seo” added an optional parameter “access_key” cosmetic
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 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/corrector
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. | DS published | 19718 | 13 | Verified |
| seorecords.com. | No DS | 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/corrector | Verified | 200 | |
| http (plaintext) | http://api.seorecords.com/mcp/corrector | HTTPS enforced | 308 | https://api.seorecords.com/mcp/corrector |
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 →
fix_page_seo Fix the SEO of a web page ~220
Runs the SEO Records correction engine (the one inside the SEO Records module) on a public page and returns every correction it would apply: the value, the source it comes from, and the exact HTML tag to add or replace in <head> — title, meta description, canonical URL, hreflang, Open Graph and Twitter preview, JSON-LD structured data, image alt texts, robots directives. Also returns the Google snippet before and after, and the issues left to the author because they touch visible content (missing h1, vague link texts…). The page is read, corrected in memory, and forgotten. 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 page address, e.g. example.com/page or https://example.com/ |
No output schema declared.
No examples provided.
get_automatic_fix_offer Apply the fixes automatically: offer and payment links ~112
Returns the SEO Records products that apply these corrections automatically on every page: the SEO Records module (WordPress, PrestaShop, Joomla, Drupal, custom PHP; from €199/year) and SEO Outpost (the same corrections at the network edge, any hosting; from €199 for a year), with what each does, prices and secure Stripe payment links. Docs: https://seorecords.com/assistants
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Language of the product pages (default en) |
No output schema declared.
No examples provided.
How do I install the SEO Records Corrector MCP server?
SEO Records Corrector is a hosted endpoint at https://api.seorecords.com/mcp/corrector, 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-corrector 'https://api.seorecords.com/mcp/corrector'
What is the SEO Records Corrector MCP server?
SEO Records Corrector is an MCP server listed in the public MCP registry as com.seorecords/seo-records-corrector. Fixes the SEO of any public page: each correction with its value, source and exact HTML tag. This page covers its hosted endpoint (https://api.seorecords.com/mcp/corrector).
Is the SEO Records Corrector MCP server safe to use?
SEO Records Corrector scores 82 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 Corrector MCP server expose?
SEO Records Corrector exposes 2 tools: fix_page_seo, get_automatic_fix_offer. Their descriptions and schemas cost roughly 332 tokens of context every time the server is loaded.
Does the SEO Records Corrector MCP server require authentication?
No. We connected to SEO Records Corrector without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SEO Records Corrector MCP server still maintained?
SEO Records Corrector 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.
What did VerifyMCP test on the SEO Records Corrector MCP server?
VerifyMCP ran 13 checks on SEO Records Corrector, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.