Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.vpatser1/seo-audit-tool

NPM · SEO-AUDIT-TOOL · SCANNED SEP 24

SEO page audits with 0-100 scoring, keyword analysis, link checking, sitemap validation

Available components

0 this week 81 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
Schema Quality & AI Usability86
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 405 tokens (~81/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.vpatser1/seo-audit-tool MCP server?

io.github.vpatser1/seo-audit-tool runs locally as an npm package, launched with npx -y seo-audit-tool. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · seo-audit-tool

# add to Claude Code
claude mcp add vpatser1-seo-audit-tool -- npx -y seo-audit-tool
// .cursor/mcp.json
{
  "mcpServers": {
    "vpatser1-seo-audit-tool": {
      "command": "npx",
      "args": [
        "-y",
        "seo-audit-tool"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "vpatser1-seo-audit-tool": {
      "command": "npx",
      "args": [
        "-y",
        "seo-audit-tool"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add vpatser1-seo-audit-tool -- npx -y seo-audit-tool
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "vpatser1-seo-audit-tool": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "seo-audit-tool"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add vpatser1-seo-audit-tool --command npx --arg -y --arg seo-audit-tool
# ~/.hermes/config.yaml
mcp_servers:
  vpatser1-seo-audit-tool:
    command: "npx"
    args: ["-y", "seo-audit-tool"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "vpatser1-seo-audit-tool": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "seo-audit-tool"
      ]
    }
  }
}
# add to Vellum
assistant mcp add vpatser1-seo-audit-tool -t stdio -c npx -a -y seo-audit-tool
// mcp.json
{
  "mcpServers": {
    "vpatser1-seo-audit-tool": {
      "command": "npx",
      "args": [
        "-y",
        "seo-audit-tool"
      ]
    }
  }
}
Changelog

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.

  • 24 Sept 26 +1
    • Stability: 0.97 → pass security
  • 22 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 17 Sept 26 +1
    • Stability: 0.97 → pass security
  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 −3
    • Stability: pass → 0.80 functional
Diagnostics

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 24 Sept 2026 · Analysed npm/seo-audit-tool@1.1.4

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~405 tokens

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 →

Tool Tokens
analyze_keywords ~81

Analyze text content to extract keyword phrases and density metrics. Produces top 1-gram, 2-gram, and 3-gram keyword phrases with frequency counts and density percentages, TF-IDF approximation scores, suggested focus keywords, and related keyword suggestions.

NameTypeReqDescription
textstringyesThe text content to analyze for keywords (plain text, not HTML)

No output schema declared.

No examples provided.

analyze_sitemap ~67

Parse and validate an XML sitemap. Counts URLs, checks for duplicates, validates lastmod date formats, detects future dates, analyzes URL patterns, and verifies XML structure. Supports both sitemap files and sitemap index files.

NameTypeReqDescription
urlstringyesThe URL of the sitemap.xml file to analyze

No output schema declared.

No examples provided.

audit_page ~87

Perform a comprehensive SEO audit on a URL. Analyzes title tag, meta description, heading structure (H1-H6), image alt text coverage, internal/external link counts, page load size, mobile-friendliness indicators, and schema.org structured data. Returns a score from 0-100 with detailed recommendations.

NameTypeReqDescription
urlstringyesThe URL of the page to audit

No output schema declared.

No examples provided.

check_links ~79

Crawl all links on a page and check their status. Identifies broken links (4xx, 5xx), classifies internal vs external links, checks for nofollow/noopener attributes, and detects redirect chains. Checks up to 100 unique links with concurrent requests.

NameTypeReqDescription
urlstringyesThe URL of the page to check links on

No output schema declared.

No examples provided.

compare_pages ~91

Compare SEO metrics of two URLs side by side. Fetches both pages in parallel and compares title tags, meta descriptions, heading counts, image alt coverage, link counts, page size, viewport tags, structured data, and overall SEO scores. Identifies the winner and provides improvement recommendations.

NameTypeReqDescription
url_astringyesThe first URL to compare
url_bstringyesThe second URL to compare

No output schema declared.

No examples provided.

Common questions

What is the io.github.vpatser1/seo-audit-tool MCP server?

io.github.vpatser1/seo-audit-tool is an MCP server listed in the public MCP registry as io.github.vpatser1/seo-audit-tool. SEO page audits with 0-100 scoring, keyword analysis, link checking, sitemap validation. This page covers its npm package (seo-audit-tool).

Is the io.github.vpatser1/seo-audit-tool MCP server safe to use?

io.github.vpatser1/seo-audit-tool scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 2026. It declares no install or post-install scripts. 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 io.github.vpatser1/seo-audit-tool MCP server expose?

io.github.vpatser1/seo-audit-tool exposes 5 tools: audit_page, analyze_keywords, check_links, analyze_sitemap, compare_pages. Their descriptions and schemas cost roughly 405 tokens of context every time the server is loaded.

Is the io.github.vpatser1/seo-audit-tool MCP server still maintained?

io.github.vpatser1/seo-audit-tool is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.vpatser1/seo-audit-tool MCP server under?

io.github.vpatser1/seo-audit-tool declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.