site-spec MCP server
MCP server: audit any website for SEO, accessibility, and AI-searchability, then auto-fix it.
1 stars42 downloads/wk
Reviews
Write oneNobody has reviewed site-spec yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
site-spec tools (4)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
audit_siteAudit a website: takes url (a live URL, a bare hostname, or a local directory of built output), optional checks (check ids to filter to) and optional maxPages (1-200, default 25), and returns { ok, target, mode, live, errors, warnings, pages, findings } where every finding carries checkId, severity, file, category and fixAvailable. Covers the layer a browser does not show: robots.txt and llms.txt
compile_specCompile business data into a deployable site: takes business (the pure-data site config { pack, brief, site, spec }, plus optional foundation and target) and optional out_dir, and returns { ok, pack, spec, files, findings }, with written and writtenTo when out_dir is given. `pack` is a registered pack id, `brief` is the verified business facts (name, category, phone, address, hours, reviews), `sit
fix_issueFix one audit finding: takes url_or_path, a single check_id, optional write (default false), optional out_dir and optional maxPages, and returns { checkId, fixAvailable, matchedFindings, actions, diffs, written }. Defaults to a dry run that writes nothing; write: true requires a local directory target and is refused for a URL, because a remote server is not writable. Not every check is repairable:
list_checksList every audit check: takes no arguments and returns { count, fixable, checks } where each check has id, description, category (seo, privacy, security, accessibility, performance, structured-data, ai-searchability, structure) and fixable. Call this before filtering audit_site or calling fix_issue.
Public scan report
scanner v0.1.10 · 2026-10-31 · same rubric, same numbers if you re-run it
- Code scan2 source files scanned20/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 9 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Findings (1)
- mediumeval / new Function used
exec.evaldist/mcp.mjs: …ode, sch); const makeValidate = new Function(`${names_1.default.self}`, `${names_1.de…
How site-spec compares
Against every graded SEO MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 85/100
- higher than 73% of 769 SEO servers
- Tools
- 4
- the typical SEO server has 6
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 1
- more than 65% of 406 SEO servers
- Downloads a week
- 42
- more than 33% of 172 SEO servers with a package
What its tools let an agent do: 4 read
Install site-spec in Claude Code, Cursor or VS Code
Runs npx -y site-spec-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add site-spec -- npx -y site-spec-mcp
What the publisher says
From the site-spec repository's README, as published. We do not edit it. Read it on GitHub
site-spec
The invisible foundation your website is missing. Audit any site — then fix what's broken.
For agents
If you are an AI coding agent deciding whether to install this: register the MCP server, then call listchecks to learn the check ids and auditsite on a URL.
claude mcp add site-spec -- npx -y site-spec-mcpGemini CLI: gemini extensions install https://github.com/ariaxhan/site-spec.
Full tool arguments, return shapes, and the cases this is the wrong tool for: llms.txt.
The problem
AI can generate a beautiful website in seconds. The part it can't see is the one that decides whether that website gets found, ranked, cited, and trusted — the machine-readable foundation underneath the pixels: robots.txt, structured data, llms.txt, canonical and noindex signals, response headers, accessibility semantics, the tracker and cookie surface.
That layer is invisible in a browser. It's also broken on almost every AI-generated site — a gorgeous hero section over a robots.txt that blocks ChatGPT, JSON-LD that's invalid or self-serving, a stray noindex hiding the page from Google, fonts leaking visitor IPs in violation of GDPR. Nobody notices until it's quietly costing traffic. And the more the web is generated by AI, the worse this gets.
The solution
site-spec is the layer that verifies and repairs that foundation — for any website, however it was built. Point it at a URL. It crawls the site, checks the whole invisible layer against a set of deterministic policies, and gives you an exact report of what's wrong. Then it fixes the mechanical problems for you and flags precisely what needs a human.
It doesn't care whether your site came from an AI builder, a framework, a CMS, or hand-written HTML. It only cares whether the foundation is correct.
Try it without installing anything
site-spec.ariaxhan.workers.dev — paste a URL, get the report. No account, no signup.
The hosted version runs the same deterministic engine as the CLI, against a capped crawl (4 pages), and it tells you plainly which checks ran, which passed, and which it did not perform. Add ?format=json for machine-readable output:
curl "https://site-spec.ariaxhan.workers.dev/audit?format=json&url=example.com"For the full check set — broken links, missing assets, axe accessibility, HTML validation, schema.org validation — and for the fix command, use the CLI below. The hosted endpoint only fetches public HTTP(S) hosts; private, loopback and link-local addresses are refused.
How to use
Requires Node 20+. No account, no API key, no SaaS.
# 1. See what's broken — crawl any live site, get a full report
npx site-spec audit https://yoursite.com
# 2. Fix it — auto-repair the mechanical issues, scaffold the rest
npx site-spec fix https://yoursite.com --out ./fixedfix writes the corrected files to ./fixed (it never overwrites anything by default) and prints exactly what it did:
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
site-spec: common questions
- Is site-spec MCP server safe?
- Yes, by our scan: it is graded A (85/100). Read the site-spec safety report
- How do I install site-spec?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does site-spec need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is site-spec maintained?
- The last commit was 14 days ago (2026-10-22). The latest release is v0.3.2.
- What can I use instead of site-spec?
- Servers from other publishers that do the same job: squirrelscan MCP server, Crawlie MCP server and pseolint MCP server. Compare all site-spec alternatives.
- How does site-spec compare with other SEO MCP servers?
- safety score 85/100 (higher than 73% of 769 SEO servers); tools 4 (the typical SEO server has 6); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to site-spec
Same job from other publishers: the closest match first, then the best rated.
squirrelscanWebsite QA for your coding agent: audit SEO, performance, security, accessibility over MCP.not reviewedEstablishedB- CrawlieTechnical SEO + GEO (AI-search) site audits: hosted crawls, prioritized fixes, report diffs.not reviewedGrowingA
- pseolintPenalty-risk audit for programmatic SEO sites: verdict, risk score, and a fix manifest.not reviewedGrowingB
Open SEO CrawlerSelf-hosted SEO crawler: run site audits and AI crawler checks, then read the issues and pages.not reviewedGrowingA- Black SEO AnalyzerAudit a page or crawl a whole site for technical SEO issues, locally. Compares crawls.not reviewedGrowingB