SEO Audit MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| audit_pageA | Technical SEO and AI-search readiness audit of one public URL: title, meta description, headings, canonical, robots, Open Graph, JSON-LD structured data, images, links, word count and a prioritised issue list. |
| check_linksB | Fetches a page and checks the HTTP status of its links. Reports broken (4xx/5xx/unreachable), redirected and slow links. |
| check_site_filesB | For a site origin: reads robots.txt (and which AI crawlers it blocks), finds and counts sitemap URLs, samples a few for status, and checks for /llms.txt used by AI assistants. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a distinct primary target: link statuses, site-level files, and single-page audits. However, audit_page also says it covers links, so an agent may be unsure whether to use check_links or audit_page when only link health is needed.
All three tools follow a consistent verb_noun snake_case pattern: check_links, check_site_files, audit_page. No naming ambiguity or mixed conventions.
Three tools is on the low side but each is substantial and multi-purpose within SEO auditing. The set is focused and earns its place, though it could reasonably support a few more checks.
Core audit areas are covered: on-page metadata, structured data, link health, robots.txt/sitemaps, and llms.txt. Notable gaps remain for common SEO needs such as performance/Core Web Vitals, security headers, multi-page crawling, and detailed redirect-chain analysis.