Provides AI assistants with direct access to SEO, GEO, and accessibility audits, backlink data, and site crawling capabilities.
Also known as SeoScoreAPI/seoscoreapi-mcp, seoscoreapi-mcp
- Stars
- 0
- Tools
- 29
- Downloads, 30 days
- —
- Latest version
- 1.5.0
- Last commit
- Nov 10, 2026
- License
- MIT
What is SEO Score API MCP?
SEO Score API provides AI assistants with direct access to SEO, GEO, and accessibility audits, backlink data, and site crawling capabilities. It exposes 29 tools, such as audit, batch_audit, usage.
Summary generated from the project's README
About SEO Score API MCP server
SEO Score API provides AI assistants with direct access to comprehensive web optimization data. Developers can connect this server to clients like Claude Desktop, Cursor, Windsurf, or Claude Code to perform SEO, GEO, and accessibility audits. The server supports both local installation via npx and remote connection through a hosted HTTP endpoint. Users can authenticate using an API key provided as an environment variable or a Bearer token header.
The toolset includes specific functions for deep site audits, backlink data analysis, and site crawling to identify broken links or orphan pages. It also features specialized capabilities for Generative Engine Optimization, such as checking brand mentions across LLMs and generating llms.txt files. Depending on the subscription plan, users can access advanced features like batch audits, competitive comparisons, and automated citation tracking across platforms like ChatGPT and Perplexity.
What you can do with it
- 1Perform comprehensive SEO auditsAsk your AI assistant to analyze a specific URL and identify the most important fixes for search engine optimization.
- 2Analyze competitor performanceRequest a comparison of AI readability scores across multiple different websites.
- 3Monitor brand citations in LLMsSet up a system to track how often a specific brand is mentioned by various AI models.
- 4Identify website technical errorsInstruct the AI to crawl a domain to find broken links, redirects, or duplicate pages.
Written from the project's README. Every use case is checked against a quote from it.
How to install SEO Score API MCP
Formats verified 10 Nov 2026Install SEO Score API MCP in Claude Code
$ claude mcp add --env SEO_SCORE_API_KEY=<YOUR_SEO_SCORE_API_KEY> seoscoreapi-mcp -- npx -y seoscoreapi-mcpInstall SEO Score API MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"seoscoreapi-mcp": {
"command": "npx",
"args": [
"-y",
"seoscoreapi-mcp"
],
"env": {
"SEO_SCORE_API_KEY": "<YOUR_SEO_SCORE_API_KEY>"
}
}
}
}Install SEO Score API MCP in VS Code
.vscode/mcp.json
{
"servers": {
"seoscoreapi-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"seoscoreapi-mcp"
],
"env": {
"SEO_SCORE_API_KEY": "<YOUR_SEO_SCORE_API_KEY>"
}
}
}
}Install SEO Score API MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"seoscoreapi-mcp": {
"command": "npx",
"args": [
"-y",
"seoscoreapi-mcp"
],
"env": {
"SEO_SCORE_API_KEY": "<YOUR_SEO_SCORE_API_KEY>"
}
}
}
}Install SEO Score API MCP in Codex
~/.codex/config.toml
[mcp_servers.seoscoreapi-mcp] command = "npx" args = ["-y", "seoscoreapi-mcp"] [mcp_servers.seoscoreapi-mcp.env] SEO_SCORE_API_KEY = "<YOUR_SEO_SCORE_API_KEY>"
Install SEO Score API MCP in Gemini CLI
~/.gemini/settings.json
{
"mcpServers": {
"seoscoreapi-mcp": {
"command": "npx",
"args": [
"-y",
"seoscoreapi-mcp"
],
"env": {
"SEO_SCORE_API_KEY": "<YOUR_SEO_SCORE_API_KEY>"
}
}
}
}SEO Score API MCP tools 29
Detected from the READMEauditbatch_auditusagereport_urladd_monitorlist_monitorshistoryhistory_domainsbacklinksdeep_auditstart_deep_auditget_deep_audit
| audit | — | |
| batch_audit | — | |
| usage | — | |
| report_url | — | |
| add_monitor | — | |
| list_monitors | — | |
| history | — | |
| history_domains | — | |
| backlinks | — | |
| deep_audit | — | |
| start_deep_audit | — | |
| get_deep_audit | — |
Show all 29 toolsShow fewer tools
deep_audit_usageremove_monitorcomparecompetitive_auditaccessibility_auditai_readabilitytrackersconversionquick_winsllms_txtgeo_auditgeo_brand_probecrawl_sitecitation_checkcitation_topupscitation_topup_checkoutcitation_auto_reload
| deep_audit_usage | — | |
| remove_monitor | — | |
| compare | — | |
| competitive_audit | — | |
| accessibility_audit | — | |
| ai_readability | — | |
| trackers | — | |
| conversion | — | |
| quick_wins | — | |
| llms_txt | — | |
| geo_audit | — | |
| geo_brand_probe | — | |
| crawl_site | — | |
| citation_check | — | |
| citation_topups | — | |
| citation_topup_checkout | — | |
| citation_auto_reload | — |
Configuration
SEO_SCORE_API_KEYRequiredSecretSEO Score API key (free at https://seoscoreapi.com, no card)
| Name | Description | |
|---|---|---|
| SEO_SCORE_API_KEY | SEO Score API key (free at https://seoscoreapi.com, no card) | RequiredSecret |
Automated checks
Ran Nov 12, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablePass
- Open source license (OSI)Pass
- Commit or release in the last yearPass
- Package name not close to a popular packagePass
- Remote endpoint uses HTTPSPass
- Destructive tools are labelledNot checked
- No hidden instructions to the modelPass
- No critical advisory in the package or its dependenciesPass
README
View on GitHubSEO Score API — Model Context Protocol Server
Give Claude Desktop, Claude Code, Cursor, Windsurf, or any MCP-aware AI tool direct access to the SEO Score API: full audits, backlink data, monitoring, and history.
Hosted server (no install)
Add https://seoscoreapi.com/mcp to any client that supports remote MCP servers
(Streamable HTTP). Sign in when the client asks (ChatGPT, Claude and other clients that
support MCP OAuth), or send your key as a header:
Authorization: Bearer ssa_your_key_here
Setup guides for each assistant: https://seoscoreapi.com/mcp-server
Local server (stdio)
npx -y seoscoreapi-mcp
Set your API key once and forget it:
export SEO_SCORE_API_KEY="ssa_your_key_here"
(Get a free key at https://seoscoreapi.com — no card required.)
Tools exposed
| Tool | What it does | Plan |
|---|---|---|
audit |
Full SEO audit on a URL — score, grade, 80+ checks, AI readability, prioritized fixes. include_core_web_vitals: true adds measured LCP, INP and CLS (about 10 seconds slower, needs a key) |
Free |
batch_audit |
Audit up to 10 URLs at once (include_core_web_vitals optional) |
Starter ($5/mo) |
usage |
Current plan + monthly usage + remaining quota | Free |
report_url |
Public shareable HTML report for a domain | Free |
add_monitor |
Add a URL to scheduled re-audit + alerts | Starter |
list_monitors |
List monitored URLs | Starter |
history |
Time-series of past scores for a URL | Starter |
history_domains |
Every domain audited by this key with 30-day trend | Starter |
backlinks |
Observed backlinks for a domain (audit-fed graph; honest data caveat in every response) | Basic ($15/mo) |
deep_audit |
Deep Site Audit: 9 dimensions, thousands of catalog checks + up to 150 AI checks; waits for the result (timeout_seconds, default 600) |
Pro ($39/mo), Ultra, or credits |
start_deep_audit |
Queue a Deep Site Audit and return its job_id at once (optional webhook_url) |
same |
get_deep_audit |
Status of a Deep Site Audit job, with the result once completed |
same |
deep_audit_usage |
Deep Site Audits used and remaining this month | same |
remove_monitor |
Remove a URL from score monitoring | Starter |
compare |
Structured diff across 2-5 URLs | Basic ($15/mo) |
competitive_audit |
Head-to-head against a competitor's page for a keyword | Pro ($39/mo) |
accessibility_audit |
ADA / WCAG 2.1 AA audit: score, lawsuit risk, violations with fixes (include_trackers optional) |
Paid plans; own monthly allowance |
ai_readability |
How well AI/LLM systems can consume a page | Any key |
trackers |
Third-party trackers and pixels a page loads | Any key (one audit) |
conversion |
Conversion score: headline, CTA, trust, forms, objections | Any key (one audit); full fix list on paid plans |
quick_wins |
Page-2 quick wins from Search Console rows or CSV you pass in | Any key (one audit) |
llms_txt |
Generate an llms.txt file for a domain | No key needed; curated version on Basic+ |
geo_audit |
GEO audit: how visible a page is to LLMs | Basic |
geo_brand_probe |
How often LLMs mention a brand | Basic |
add_geo_monitor / list_geo_monitors / geo_monitor_history / remove_geo_monitor |
GEO monitoring | Basic |
crawl_site |
Multi-page site crawl (broken pages, redirects, duplicates, orphans, slow pages); waits for the result | Pro, Ultra, or a Deep Audit credit |
start_crawl / get_crawl |
Start a crawl and poll it yourself | same |
citation_starter_prompts / citation_suggest_prompts |
Prompts to track for AI citations | Any key; not metered |
create_citation_tracker / list_citation_trackers / get_citation_tracker / update_citation_tracker / delete_citation_tracker |
Track a brand across ChatGPT, Gemini, Perplexity and Claude | Starter ($5/mo) |
run_citation_tracker / get_citation_run / citation_tracker_history |
Run a tracker, read a run, read the trend | Starter; metered in checks |
citation_check |
One-off citation check for a brand and one prompt | Paid plans; metered per check |
citation_topups |
Top-up packs and the account's check balance | Any key |
citation_topup_checkout |
Stripe Checkout link for a top-up pack (charges nothing until the user pays it) | Paid plans |
citation_auto_reload |
Read the auto-reload setting | Any key; read-only |
Not exposed, on purpose
- Report files (
GET /audit/export): the PDF is binary and an MCP tool result is text. Theaudittool returns the same data as JSON; use the REST API or the Python / Node SDK (audit_export/auditExport) for the file. - Turning auto-reload on. The API has no such endpoint for API keys: it authorizes
charges, so it is set from the dashboard only.
citation_auto_reloadreads it. - Account actions (
/signup,/verify,/upgrade,/rotate-key) and the public scoreboard opt-out.
Configuration
| Env var | Default | Purpose |
|---|---|---|
SEO_SCORE_API_KEY |
(none) | Your API key |
SEO_SCORE_BASE_URL |
https://seoscoreapi.com |
API host |
SEO_SCORE_DEEP_AUDIT_URL |
SEO_SCORE_BASE_URL |
Deep Audit host (POST /site-audit, GET /site-audit/{job_id}, GET /deep-audit/usage). SEO_SCORE_ENGINE_URL is still read as a fallback; the legacy https://engine.seoscoreapi.com keeps working. |
Claude Desktop
Edit ~/Library/Application Support/Claude/claude_desktop_config.json (Mac) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"seoscoreapi": {
"command": "npx",
"args": ["-y", "seoscoreapi-mcp"],
"env": {
"SEO_SCORE_API_KEY": "ssa_your_key_here"
}
}
}
}
Restart Claude Desktop. You'll see the SEO Score tools in the tool picker.
Claude Code
claude mcp add seoscoreapi -e SEO_SCORE_API_KEY=ssa_your_key_here -- npx -y seoscoreapi-mcp
Cursor
Open Cursor Settings → MCP Servers → Add a new server with the same JSON shape as Claude Desktop above.
Windsurf
Settings → Cascade → MCP Servers → paste the same configuration.
Any other MCP client
Run npx -y seoscoreapi-mcp as a stdio transport. The server speaks standard MCP and exposes all tools in the table above.
Example prompts
Once installed, talk to your AI assistant naturally:
"Audit https://stripe.com and tell me the top 3 things to fix."
"Run a batch audit on stripe.com, square.com, and adyen.com, then compare their AI readability scores."
"What backlinks have we seen pointing at my-startup.com?"
"Check the score history for our marketing site over the last 30 days."
"Run a deep audit on my-startup.com as a SaaS site and list the high-severity findings."
"Run an accessibility audit on our pricing page and list the critical WCAG failures."
"Crawl my-startup.com and show me the broken links and orphan pages."
"Build starter prompts for 'SEO audit API', create a citation tracker for Acme, and run it."
The tool the AI picks is shown in your client; you can always ask "what tools did you use?" to see the trace.
Why MCP?
MCP lets the AI reach data it wouldn't have — your actual site SEO scores, the backlink graph, your monitoring history — without any custom plumbing. Every prompt that says "audit this URL" goes from idea to result in one round-trip. Same source of truth as the REST API; no copying scores between tools.
Honest framing
The backlinks tool returns an audit-fed sample, not a comprehensive backlink index. Every response includes a data_caveat explaining exactly what the dataset is. We are not Ahrefs and don't pretend to be — we expose the unique, growing graph our customers' audits build for free.
Source
The MCP server is open source: https://github.com/SeoScoreAPI/seoscoreapi-mcp
License
MIT
SEO Score API MCP questions
How do I add SEO Score API MCP to Claude Code?
Run claude mcp add --env SEO_SCORE_API_KEY=<YOUR_SEO_SCORE_API_KEY> seoscoreapi-mcp -- npx -y seoscoreapi-mcp in your terminal. Add --scope user to make it available in every project.
How do I add SEO Score API MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does SEO Score API MCP provide?
It exposes 29 tools, including audit, batch_audit, usage, report_url, add_monitor.
What kind of audits can I perform?
You can perform full SEO audits, deep site audits, accessibility (ADA/WCAG) audits, GEO audits, and conversion audits.
Is the backlink data a complete index?
No, the backlinks tool provides an audit-fed sample rather than a comprehensive index.