mcpField
S
seoscoreapi-mcp

seoscoreapi-mcp

Local
seoscoreapi.comBusiness & Marketing0Updated 1w ago

About seoscoreapi-mcp

seoscoreapi-mcp gives MCP clients access to SEO Score API audits and monitoring for SEO, content, and website teams. Its tools cover SEO, accessibility, AI readability, backlinks, and brand citation tracking.

Key features

  1. 01Single-page and batch SEO audits
  2. 02Deep audits and multi-page crawls
  3. 03Accessibility and AI readability checks
  4. 04Score history and scheduled monitoring
  5. 05Backlink and brand citation tracking
  6. 06Page comparisons and competitor audits

Use cases

  1. 01Find page issues and prioritized fixes
  2. 02Track score changes and monitoring alerts
  3. 03Review WCAG issues and AI readability
  4. 04Monitor brand citations in LLM responses

MCP support

The MCP server exposes SEO Score API capabilities as standard MCP tools, using SEO_SCORE_API_KEY for authentication. It uses stdio transport and connects to MCP-aware AI tools.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"seoscoreapi-seoscoreapi": {
"command": "npx",
"args": [
"-y",
"seoscoreapi-mcp"
],
"env": {
"SEO_SCORE_API_KEY": "<SEO_SCORE_API_KEY>"
}
}
}
}
Run commandnpx -y seoscoreapi-mcp
Environment variables to set
SEO_SCORE_API_KEYSecretSEO Score API key (free at https://seoscoreapi.com, no card)

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmseoscoreapi-mcp1.4.1

Tools

45

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
urlstringYesThe URL to audit. Must include the protocol (https://...).
include_core_web_vitalsbooleanNoAlso measure Core Web Vitals (LCP, INP, CLS, FCP, TTFB) with Google PageSpeed Insights and return them under core_web_vitals. Adds about 10 seconds the first time a URL is measured (cached 24 hours). Needs an API key. Leave off unless the user asks about page speed or Core Web Vitals.

Details

From the project README

SEO 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.

Quick start

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

ToolWhat it doesPlan
auditFull 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_auditAudit up to 10 URLs at once (include_core_web_vitals optional)Starter ($5/mo)
usageCurrent plan + monthly usage + remaining quotaFree
report_urlPublic shareable HTML report for a domainFree
add_monitorAdd a URL to scheduled re-audit + alertsStarter
list_monitorsList monitored URLsStarter
historyTime-series of past scores for a URLStarter
history_domainsEvery domain audited by this key with 30-day trendStarter
backlinksObserved backlinks for a domain (audit-fed graph; honest data caveat in every response)Basic ($15/mo)
deep_auditDeep 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_auditQueue a Deep Site Audit and return its job_id at once (optional webhook_url)same
get_deep_auditStatus of a Deep Site Audit job, with the result once completedsame
deep_audit_usageDeep Site Audits used and remaining this monthsame
remove_monitorRemove a URL from score monitoringStarter
compareStructured diff across 2-5 URLsBasic ($15/mo)
competitive_auditHead-to-head against a competitor's page for a keywordPro ($39/mo)
accessibility_auditADA / WCAG 2.1 AA audit: score, lawsuit risk, violations with fixes (include_trackers optional)Paid plans; own monthly allowance
ai_readabilityHow well AI/LLM systems can consume a pageAny key
trackersThird-party trackers and pixels a page loadsAny key (one audit)
conversionConversion score: headline, CTA, trust, forms, objectionsAny key (one audit); full fix list on paid plans
quick_winsPage-2 quick wins from Search Console rows or CSV you pass inAny key (one audit)
llms_txtGenerate an llms.txt file for a domainNo key needed; curated version on Basic+
geo_auditGEO audit: how visible a page is to LLMsBasic
geo_brand_probeHow often LLMs mention a brandBasic
add_geo_monitor / list_geo_monitors / geo_monitor_history / remove_geo_monitorGEO monitoringBasic
crawl_siteMulti-page site crawl (broken pages, redirects, duplicates, orphans, slow pages); waits for the resultPro, Ultra, or a Deep Audit credit
start_crawl / get_crawlStart a crawl and poll it yourselfsame
citation_starter_prompts / citation_suggest_promptsPrompts to track for AI citationsAny key; not metered
create_citation_tracker / list_citation_trackers / get_citation_tracker / update_citation_tracker / delete_citation_trackerTrack a brand across ChatGPT, Gemini, Perplexity and ClaudeStarter ($5/mo)
run_citation_tracker / get_citation_run / citation_tracker_historyRun a tracker, read a run, read the trendStarter; metered in checks
citation_checkOne-off citation check for a brand and one promptPaid plans; metered per check
citation_topupsTop-up packs and the account's check balanceAny key
citation_topup_checkoutStripe Checkout link for a top-up pack (charges nothing until the user pays it)Paid plans
citation_auto_reloadRead the auto-reload settingAny key; read-only
Not exposed, on purpose
  • Report files (GET /audit/export): the PDF is binary and an MCP tool result is text. The audit tool 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_reload reads it.
  • Account actions (/signup, /verify, /upgrade, /rotate-key) and the public scoreboard opt-out.

Configuration

Env varDefaultPurpose
SEO_SCORE_API_KEY(none)Your API key
SEO_SCORE_BASE_URLhttps://seoscoreapi.comAPI host
SEO_SCORE_DEEP_AUDIT_URLSEO_SCORE_BASE_URLDeep 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

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.