Skip to content

RootMention SEO MCP server

io.github.burmanharry/rootmentionburmanharrystreamable-httpv1.0.0Scanned

Free SEO audit, SEO break-even calculator and RootMention service info for AI assistants.

3 tools: 2 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 2 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

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 RootMention SEO MCP server can do

The RootMention SEO MCP server is published by the GitHub account burmanharry. It has 3 tools. It can create or change data (2 tools: calculate_seo_break_even and run_seo_audit), but cannot delete data. 1 tool only reads.

2 tools bring in text other people can write (get_services and run_seo_audit).

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.

Last scanned Nov 18, 2026, version 1.0.0.

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.

3 tools

Changes things 2Claude Code: ask
  • calculate_seo_break_evenEstimate incremental orders and visits needed to cover monthly SEO spend.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Estimate incremental orders and visits needed to cover monthly SEO spend. A scenario calculation, not a forecast.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • run_seo_auditAudit a public homepage and up to two discovered product/collection pages.Reads text others write1 finding

    Why it is in this group

    • The name "run_seo_audit" says "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.

    Findings

    • Warn

      The server marks "run_seo_audit" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "run_seo_audit" says "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Audit a public homepage and up to two discovered product/collection pages. Requires user authorization. Respects robots.txt; returns findings inline without saving a report or sales lead. Maximum 35 seconds, three attempts per IP per hour, 30 shared audit attempts per hour.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 1Show 1 read-only tool
  • get_servicesRead RootMention service scope, pricing and public links.Reads text others writeNo findings

    Why it is in this group

    • The name "get_services" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "read" and "mention": it reads comments, which other people can write.
    Description, as the server wrote it
    Read RootMention service scope, pricing and public links.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false

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 or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
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.

Tools listed without sign-in

Looked at Nov 18, 2026, 16:19 UTC, unchanged since Nov 18, 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
2
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 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://rootmention.com/mcp: tools/list returned 3 tools to an anonymous client, including calculate_seo_break_even (write), run_seo_audit (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "run_seo_audit" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "run_seo_audit" says "run": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http rootmention https://rootmention.com/mcp
claude mcp add --transport http rootmention https://rootmention.com/mcp

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__rootmention__get_services"
    ],
    "ask": [
      "mcp__rootmention__calculate_seo_break_even",
      "mcp__rootmention__run_seo_audit"
    ],
    "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 rootmention. Review it before you use it.

Capability tags behind 2 rules
  • mcp__rootmention__get_services untrusted-input
  • mcp__rootmention__run_seo_audit untrusted-input

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/io.github.burmanharry/rootmention/verify?hash=9f87b485ff30793de01d1aada6886db52eeba89ba84e66731fdd80552b31e804" | jq -e '.changed == false'

Pinned hash 9f87b485ff30, from Nov 18, 2026, 03:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.burmanharry/rootmention/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.burmanharry/rootmention
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.burmanharry/rootmention.svg)](https://radar.anlyon.com/servers/io.github.burmanharry/rootmention)

Source: MCP Registry · repository. Synced Nov 18, 2026, 03:17 UTC.

RootMention SEO MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the RootMention SEO MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 2 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 RootMention SEO MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the RootMention SEO 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 RootMention SEO MCP server have?

3 tools: 2 write, 1 read. calculate_seo_break_even, run_seo_audit and get_services.

Does the RootMention SEO MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the RootMention SEO MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the RootMention SEO MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.