Skip to content

seo-mcp server

com.metricspot/seo-mcpmetricspot.comstreamable-httpv0.1.1Scanned

Six tools for SEO and AI-readability audits. 91 checks, 11 score modules.

6 tools: 2 change things and 4 only read.

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

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 seo-mcp server can do

The seo-mcp server is published by metricspot.com, a domain the MCP Registry verified. It has 6 tools. It can create or change data (2 tools: run_audit_anonymous and run_audit), but cannot delete data. 4 tools only read.

2 tools bring in text other people can write (list_audits and get_audit_pdf); 2 tools can send data out of your system (run_audit_anonymous and run_audit).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 10, 2026, version 0.1.1.

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.

6 tools

Changes things 2Claude Code: ask
  • run_auditQueue a full SEO + AI-readability audit (includes Core Web Vitals from Google PSI and organic traffic if Google is linked).Can send data outNo findings

    Why it is in this group

    • The name "run_audit" says "run": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Queue a full SEO + AI-readability audit (includes Core Web Vitals from Google PSI and organic traffic if Google is linked). Returns the audit envelope immediately with `status: queued` and an `audit_id`. Poll `get_audit` with the returned `audit_id` until `status` becomes `complete` (typical 10-30s). Counts against the user's plan allowance. Requires an API key as a Bearer token. Quota and per-domain cooldowns mirror the dashboard.
  • run_audit_anonymousRun a one-shot SEO + AI-readability audit on any public URL.Can send data outNo findings

    Why it is in this group

    • The name "run_audit_anonymous" says "run": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Run a one-shot SEO + AI-readability audit on any public URL. Returns scores across 11 modules and ~90 checks, plus actionable findings with rule docs. Limited to 1 audit per IP per 24 hours — for higher volume, get an API key at https://app.metricspot.com/settings/api-keys and use `run_audit`. Synchronous: blocks until the audit completes. Does NOT include Core Web Vitals (use `run_audit` for full PSI scoring). No auth required.
Only reads 4Show 4 read-only tools
  • get_auditFetch a previously-run audit by id.No findings

    Why it is in this group

    • The name "get_audit" says "get": a word for reading.
    Description, as the server wrote it
    Fetch a previously-run audit by id. Returns module scores (0-100), total score, all findings with severity, recommendation text, and links to the HTML report. Use this to poll a queued `run_audit` until `status: complete`. Requires an API key.
  • get_audit_pdfReturn a signed download URL for the branded PDF report for a given audit id.Reads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe description's first sentence says "return" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Return a signed download URL for the branded PDF report for a given audit id. If no PDF has been rendered yet, queues a render and returns `status: queued` — poll the same tool again, or fetch the URL directly once ready. Requires an API key.
  • get_organic_trafficIf the user has linked GA4 + Google Search Console, return the 28-day organic traffic snapshot for an audit: session count, daily trend, top landing pages, top queries, and indexin…No findings

    Why it is in this group

    • The name "get_organic_traffic" says "get": a word for reading.
    Description, as the server wrote it
    If the user has linked GA4 + Google Search Console, return the 28-day organic traffic snapshot for an audit: session count, daily trend, top landing pages, top queries, and indexing health. Returns `connected: false` if Google is not linked. Cached 24h server-side. Requires an API key.
  • list_auditsList the user's audits (most recent first, deduplicated by URL).Reads text others writeNo findings

    Why it is in this group

    • The name "list_audits" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "list" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    List the user's audits (most recent first, deduplicated by URL). Returns `audit_id`, `url`, `status`, `total_score`, `created_at`. Default limit 24, max 100. Use the returned `audit_id` with `get_audit` for full findings. Requires an API key.

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 write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
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 20, 2026, 18:42 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
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://mcp.metricspot.com/mcp: tools/list returned 6 tools to an anonymous client, including run_audit_anonymous (write), run_audit (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

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 0.1.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http seo https://mcp.metricspot.com/mcp
claude mcp add --transport http seo https://mcp.metricspot.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__seo__get_audit",
      "mcp__seo__list_audits",
      "mcp__seo__get_audit_pdf",
      "mcp__seo__get_organic_traffic"
    ],
    "ask": [
      "mcp__seo__run_audit_anonymous",
      "mcp__seo__run_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 seo. Review it before you use it.

Capability tags behind 4 rules
  • mcp__seo__run_audit_anonymous outbound
  • mcp__seo__run_audit outbound
  • mcp__seo__list_audits untrusted-input
  • mcp__seo__get_audit_pdf 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/com.metricspot/seo-mcp/verify?hash=25ffb55d38b9a84b576a76a9e1fb11864b87c75c912fad02c43d64ab99bb421d" | jq -e '.changed == false'

Pinned hash 25ffb55d38b9, from Nov 10, 2026, 21:17 UTC.

Watch

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

https://radar.anlyon.com/servers/com.metricspot/seo-mcp/changes.xml

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

Badge

Anlyon Radar badge for com.metricspot/seo-mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/com.metricspot/seo-mcp.svg)](https://radar.anlyon.com/servers/com.metricspot/seo-mcp)

Source: MCP Registry · repository. Synced Oct 21, 2026, 17:59 UTC.

seo-mcp server: questions and answers

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

Is the seo-mcp server safe?

No scan can promise that. What its definitions show: 6 tools, 2 of which can change, send or delete something, and 0 findings 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-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-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-mcp server have?

6 tools: 2 write, 4 read. run_audit_anonymous, run_audit, get_audit, list_audits, get_audit_pdf and get_organic_traffic.

Does the seo-mcp server need sign-in or OAuth?

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

Does the seo-mcp server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): run_audit_anonymous and run_audit.

Has the seo-mcp server changed its tools?

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