mcpbeat

SEO Page Analyzer MCP Server

io.github.Br0ski777/seo-analyzer
answering

SEO Page Analyzer is answering right now. Last checked 5 min ago. It exposes 2 tools. Last commit 19 Jul 2026.

SEO audit any URL: meta tags, headings, links, images, Schema.org, score 0-100. x402.

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
91 of 91 checks
2
Tools
read from the server
33 ms
Response time
average over 24h
0
Stars
last commit 19 Jul 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.

run in your terminal
claude mcp add seo-analyzer --transport http https://seo-analyzer.api.klymax402.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "seo-analyzer": {
      "url": "https://seo-analyzer.api.klymax402.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.seo-analyzer]
url = "https://seo-analyzer.api.klymax402.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "seo-analyzer": {
      "url": "https://seo-analyzer.api.klymax402.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "seo-analyzer": {
      "url": "https://seo-analyzer.api.klymax402.com/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

seo
seo_audit_batch
Use this when you need to compare SEO health across multiple pages at once (up to 10 URLs). Returns the same full audit as seo_audit_page for each URL in a single call. 1. results (array) -- each entry contains the full SEO audit (score, title, meta, headings, links, images, schema, issues) 2. summary -- average score, worst-performing URL, most common issues across all pages Example output: {"results":[{"url":"https://a.com","score":85},{"url":"https://b.com","score":62}],"summary":{"avgScore":73,"worstUrl":"https://b.com"}} Use this FOR competitor analysis, sitemap audits, or comparing landing pages side by side. Essential when benchmarking multiple pages in one workflow. Do NOT use for single URLs -- use seo_audit_page instead. Do NOT use for content extraction -- use web_scrape_batch instead.
seo_audit_page
Use this when you need to analyze a webpage's on-page SEO health. Returns a structured JSON audit with score 0-100 and prioritized recommendations. 1. score (number 0-100) -- overall SEO health score 2. title -- tag content, length, keyword presence 3. metaDescription -- content, length, truncation risk 4. canonical -- canonical URL and self-referencing check 5. headings -- H1/H2/H3 hierarchy, count, missing H1 flag 6. links -- internal count, external count, broken link flags 7. images -- total count, missing alt text count 8. schema -- Schema.org types detected (Article, Product, FAQ, etc.) 9. openGraph -- og:title, og:image, og:description completeness 10. performance -- page load time in ms, word count 11. issues -- prioritized array of problems with severity (critical/warning/info) Example output: {"score":72,"title":{"content":"My Page","length":7},"headings":{"h1":1,"h2":3},"images":{"total":5,"missingAlt":2},"issues":[{"severity":"critical","message":"Missing meta description"}]} Use this BEFORE optimizing any webpage, writing SEO recommendations, or auditing a client's site. Essential for competitive page-level analysis and content audits. Do NOT use for content extraction -- use web_scrape_to_markdown instead. Do NOT use for screenshots -- use capture_screenshot instead. Do NOT use for tech detection -- use website_detect_tech_stack instead. Do NOT use for domain-level data (WHOIS/DNS) -- use domain_lookup_intelligence instead.

Endpoints

URLTransportStateLatencyChecked
https://seo-analyzer.api.klymax402.com/mcp sse answering 14 ms 5 min ago

SEO Page Analyzer — questions

Answers built from our own checks of this server.

What can SEO Page Analyzer do?
It exposes 2 tools, read directly from the server on our last check. Among them: seo_audit_batch, seo_audit_page. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is SEO Page Analyzer working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 33 ms. The bar chart above shows every period we have measured.
How do I connect SEO Page Analyzer?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does SEO Page Analyzer need an API key?
No. SEO Page Analyzer completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is SEO Page Analyzer?
It answers our handshake in 33 ms on average, which is faster than 99% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is SEO Page Analyzer open source?
Yes — it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.