Skip to content

SEO Technical Audit MCP server

io.github.theharrisontruong-web/seo-audittheharrisontruong-webstreamable-httpv1.0.0Scanned

Technical SEO audit of any web page: indexing, meta, OG, schema. $1.00/call via x402.

2 tools: 2 change things.

Tools: 0 delete, 0 irreversible, 2 write, 0 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 Technical Audit MCP server can do

The SEO Technical Audit MCP server is published by the GitHub account theharrisontruong-web. It has 2 tools. It can create or change data (2 tools: audit_seo and audit_seo_lite), but cannot delete data. None of its tools only reads.

2 tools bring in text other people can write (audit_seo and audit_seo_lite); 2 tools can send data out of your system (audit_seo and audit_seo_lite).

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 17, 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.

2 tools

Changes things 2Claude Code: ask
  • audit_seoFull SEO technical audit of a single web page URL.Reads text others writeCan send data outNo 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.

    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.
    Description, as the server wrote it
    Full SEO technical audit of a single web page URL. Fetches the page server-side plus the origin's robots.txt and sitemap, and runs 13 weighted checks: robots.txt present, robots not blocking the page, no noindex directive, sitemap present and valid, title tag length, meta description length, canonical tag, viewport (mobile), H1 structure, Open Graph completeness, JSON-LD structured data, image alt coverage, and a fetch-performance signal. These are the technical failures that make a page invisible in search — a robots-blocked or noindexed page cannot rank at all, and a missing sitemap, title, or canonical quietly caps the rest. Returns machine-readable JSON: 0-100 score, A-F grade, a search-visibility risk level (Low/Moderate/Elevated/High) with the blocking checks named as triggers, per-check pass/partial/fail/unknown with evidence, a page block (status, bytes, fetch time, title, sitemap URL), and the top 3 prioritized fixes. HONEST LIMITS: this is a single-page snapshot — it does not crawl the site, and it uses no keyword, ranking, backlink, or Search Console data; no audit can guarantee ranking. Cost: $1.00 USDC on Base per call, paid via x402 — the caller's agent pays from its owner's approved wallet; no API key needed. Use this after a redesign or template change, before a launch, or to triage a sudden traffic drop.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
  • audit_seo_liteFREE lite SEO technical audit of a single web page URL.Reads text others writeCan send data outNo 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.

    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.
    Description, as the server wrote it
    FREE lite SEO technical audit of a single web page URL. Runs the same 13 checks as audit_seo but returns top-line results only: 0-100 score, A-F grade, search-visibility risk level, the page title, check counts, and the titles of the top gaps — per-check evidence and fixes are capped. Use this to triage whether a page needs the full audit_seo report, or call audit_seo directly for the complete evidence-backed scan.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: 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 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 17, 2026, 15:20 UTC, unchanged since Nov 17, 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://seo-al6bxcngia-ue.a.run.app/mcp: tools/list returned 2 tools to an anonymous client, including audit_seo (write), audit_seo_lite (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 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http seo-audit https://seo-al6bxcngia-ue.a.run.app/mcp
claude mcp add --transport http seo-audit https://seo-al6bxcngia-ue.a.run.app/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": [],
    "ask": [
      "mcp__seo-audit__audit_seo",
      "mcp__seo-audit__audit_seo_lite"
    ],
    "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-audit. Review it before you use it.

Capability tags behind 2 rules
  • mcp__seo-audit__audit_seo untrusted-input, outbound
  • mcp__seo-audit__audit_seo_lite 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/io.github.theharrisontruong-web/seo-audit/verify?hash=44771825ae05971b55534d1076af215a2b3fd41d0439bdf799d984b3b0690457" | jq -e '.changed == false'

Pinned hash 44771825ae05, from Nov 17, 2026, 02: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.theharrisontruong-web/seo-audit/changes.xml

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

Badge

Anlyon Radar badge for io.github.theharrisontruong-web/seo-audit
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.theharrisontruong-web/seo-audit.svg)](https://radar.anlyon.com/servers/io.github.theharrisontruong-web/seo-audit)

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

SEO Technical Audit MCP server: questions and answers

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

Is the SEO Technical Audit MCP server safe?

No scan can promise that. What its definitions show: 2 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 Technical Audit 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 Technical Audit 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 Technical Audit MCP server have?

2 tools: 2 write. audit_seo and audit_seo_lite.

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

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

Does the SEO Technical Audit 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): audit_seo and audit_seo_lite.

Has the SEO Technical Audit MCP server changed its tools?

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