mcpbeat Sign in

SEO Audit MCP Server

by deepseoanalysis Your server? Claim it
answering

SEO Audit is answering right now. Last checked 6 min ago.

Run SEO + AI-visibility (GEO) audits from Claude, Cursor & other AI clients.

Uptime history 91 days of history · worst day 53%
91 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
335 ms
Response time
average over 24h
API key
Access
streamable-http

SEO Audit missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

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

run in your terminal
claude mcp add seo-audit --transport http https://deepseoanalysis.com/api/mcp
Settings → Connectors → Add custom connector, then paste this address
https://deepseoanalysis.com/api/mcp
~/.codex/config.toml
[mcp_servers.seo-audit]
url = "https://deepseoanalysis.com/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "seo-audit": {
      "url": "https://deepseoanalysis.com/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "seo-audit": {
      "type": "http",
      "url": "https://deepseoanalysis.com/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but you need an API key from its owner to call it.

Endpoints

URLTransportStateLatencyChecked
https://deepseoanalysis.com/api/mcp streamable-http needs key 291 ms 6 min ago

Alternatives to SEO Audit

same job, measured the same way
Rankdelta
by alordincans

Open-source AI SEO over MCP: audits, ranks, keywords, backlinks + AI visibility (GEO).

answering
SurfacedBy AI Visibility & GEO Audit
by surfacedby

Free AI visibility and GEO audit: see what AI reads on your site and whether its answers cite you.

5 tools answering
Getintel
by tarang8811

Manage GetIntel AI visibility (GEO) from your own AI agent.

answering
SEO Growth
by openhelm

Autonomous SEO + GEO growth: keyword research, audits, content, AI answer-engine visibility.

answering
MaxAEO AI Visibility MCP
by maxaeo

Local-first MCP server for AI visibility, GEO/AEO, llms.txt, and AI crawler readiness audits.

71 installs/wk local only
AEO Scanner
by convrgent

AI visibility for ChatGPT/Perplexity/Claude — triple score (AEO+GEO+Agent) with fix code. Free.

121 installs/wk 4 tools answering
OmniForce
by rmb

AI-search visibility: GEO audits, tracked prompts, competitors, citations.

61 installs/wk 8 tools answering
SEOforGPT
by seoforgpt

AI visibility reports, competitor insights, readiness audits, and GEO content workflows.

answering

SEO Audit — questions

Answers built from our own checks of this server.

Why is there no tool list for SEO Audit?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is SEO Audit 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 335 ms. The bar chart above shows every period we have measured.
How do I connect SEO Audit?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own key: it refuses anonymous clients.
Does SEO Audit need an API key?
Yes. Every time we knock, SEO Audit answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is SEO Audit?
It answers our handshake in 335 ms on average, which is faster than 43% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.