SEO Records Corrector MCP server
com.seorecords/seo-records-correctorseorecords.comstreamable-httpv1.0.2Scanned
Fixes the SEO of any public page, each fix with its value, source and HTML tag (access pass).
2 tools: 1 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 1
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the SEO Records Corrector MCP server can do
The SEO Records Corrector MCP server is published by seorecords.com, a domain the MCP Registry verified. It has 2 tools. It can create or change data (1 tool: fix_page_seo), but cannot delete data. 1 tool only reads.
1 tool brings in text other people can write (fix_page_seo); 1 tool can send data out of your system (fix_page_seo).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 9, 2026, version 1.0.2.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
2 tools
Changes things 1Claude Code: ask
fix_page_seoRuns 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, an…Reads text others writeCan send data out1 finding
Why it is in this group
- The description's first verb is "run": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Findings
- Warn
The server marks "fix_page_seo" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "run": a word for a change.
Description, as the server wrote it 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
Annotations the server declares
- title: Fix the SEO of a web page
- readOnlyHint: true
- openWorldHint: true
- idempotentHint: true
Only reads 1Show 1 read-only tool
get_automatic_fix_offerReturns 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…No findings
Why it is in this group
- The name "get_automatic_fix_offer" says "get": a word for reading.
Description, as the server wrote it 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
Annotations the server declares
- title: Apply the fixes automatically: offer and payment links
- readOnlyHint: true
- openWorldHint: false
- idempotentHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:22 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.seorecords.com/mcp/corrector: tools/list returned 2 tools to an anonymous client, including fix_page_seo (write)
Findings
Matches of fixed checks, with the text they matched.
- Warnfix_page_seo
The server marks "fix_page_seo" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "run": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:fix_page_seoChanges thingsdescriptioninputSchema
Install
Pinned to version 1.0.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http seo-records-corrector https://api.seorecords.com/mcp/correctorclaude mcp add --transport http seo-records-corrector https://api.seorecords.com/mcp/correctorRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__seo-records-corrector__get_automatic_fix_offer"
],
"ask": [
"mcp__seo-records-corrector__fix_page_seo"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as seo-records-corrector. Review it before you use it.
Capability tags behind 1 rule
- mcp__seo-records-corrector__fix_page_seo untrusted-input, outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.seorecords/seo-records-corrector/verify?hash=91da6350707364d6978c71ac614d85d002163ccadad4abe128d0b7bbd958bca8" | jq -e '.changed == false'Pinned hash 91da63507073, from Nov 9, 2026, 20:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.seorecords/seo-records-corrector/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.seorecords/seo-records-corrector)Source: MCP Registry. Synced Nov 9, 2026, 21:17 UTC.
SEO Records Corrector MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the SEO Records Corrector MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, 1 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the SEO Records Corrector MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the SEO Records Corrector MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the SEO Records Corrector MCP server have?
- 2 tools: 1 write, 1 read. fix_page_seo and get_automatic_fix_offer.
Does the SEO Records Corrector MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the SEO Records Corrector MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): fix_page_seo.
Has the SEO Records Corrector MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 3, 2026. Every change is on this page and in its Atom feed.