site-spec
NPM · SITE-SPEC-MCP · SCANNED SEP 20
MCP server: audit any website for SEO, accessibility, and AI-searchability, then auto-fix it.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 24 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 781 tokens (~195/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the site-spec MCP server?
site-spec runs locally as an npm package, launched with npx -y site-spec-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · site-spec-mcp
claude mcp add ariaxhan-site-spec -- npx -y site-spec-mcp
{
"mcpServers": {
"ariaxhan-site-spec": {
"command": "npx",
"args": [
"-y",
"site-spec-mcp"
]
}
}
} {
"servers": {
"ariaxhan-site-spec": {
"command": "npx",
"args": [
"-y",
"site-spec-mcp"
]
}
}
} codex mcp add ariaxhan-site-spec -- npx -y site-spec-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ariaxhan-site-spec": {
"type": "local",
"command": [
"npx",
"-y",
"site-spec-mcp"
],
"enabled": true
}
}
} openclaw mcp add ariaxhan-site-spec --command npx --arg -y --arg site-spec-mcp
mcp_servers:
ariaxhan-site-spec:
command: "npx"
args: ["-y", "site-spec-mcp"] {
"McpServers": {
"ariaxhan-site-spec": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"site-spec-mcp"
]
}
}
} assistant mcp add ariaxhan-site-spec -t stdio -c npx -a -y site-spec-mcp
{
"mcpServers": {
"ariaxhan-site-spec": {
"command": "npx",
"args": [
"-y",
"site-spec-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +4
- Stability: unverified → 0.27 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/site-spec-mcp@0.3.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
audit_site Audit a website's invisible foundation ~228
Audit 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 policy, canonical and noindex signals, structured data, Open Graph, security and cache headers, accessibility semantics, and the tracker/cookie surface.
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | – | Only report these check ids (e.g. ["audit/noindex"]). Omit for every check. Call list_checks for the full set. |
| maxPages | integer | – | Cap the live crawl at this many pages. Default 25. Ignored for a local directory. |
| url | string | yes | The site to audit: a URL (https://example.com, or bare example.com), or a path to a local directory of built output. |
No output schema declared.
No examples provided.
compile_spec Compile business data into a SiteSpec and a deployable site ~227
Compile 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), `site` is deploy context (baseUrl, locales), and `spec` is the page structure; the files rendered are HTML, sitemap.xml, robots.txt, llms.txt, headers and icons. Validation runs at both the spec tier and the rendered tier, so an invalid site never produces output.
| Name | Type | Req | Description |
|---|---|---|---|
| business | object | yes | The site config object: { pack: "restaurant", brief: {...}, site: {...}, spec: {...}, foundation?: {...}, target?: "cloudflare" }. |
| out_dir | string | – | Write the compiled site to this directory. Omit to get the files in the response only. |
No output schema declared.
No examples provided.
fix_issue Auto-fix one audit finding ~256
Fix 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_checks marks which ones are, and unrepairable findings come back with the manual step spelled out.
| Name | Type | Req | Description |
|---|---|---|---|
| check_id | string | yes | The single check id to repair, e.g. "audit/robots-stale-token". See list_checks. |
| maxPages | integer | – | Cap the live crawl at this many pages. Default 25. Ignored for a local directory. |
| out_dir | string | – | Directory to write into when write is true. Defaults to overwriting the target directory. |
| url_or_path | string | yes | The site to fix: a URL (diff only), or a path to a local directory of built output. |
| write | boolean | – | Write the corrected files to disk. Local directory targets only; refused for a URL. Default false (dry run). |
No output schema declared.
No examples provided.
list_checks List every audit check ~70
List 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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the site-spec MCP server?
site-spec is an MCP server listed in the public MCP registry as io.github.ariaxhan/site-spec. MCP server: audit any website for SEO, accessibility, and AI-searchability, then auto-fix it. This page covers its npm package (site-spec-mcp).
Is the site-spec MCP server safe to use?
site-spec scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the site-spec MCP server expose?
site-spec exposes 4 tools: audit_site, fix_issue, compile_spec, list_checks. Their descriptions and schemas cost roughly 781 tokens of context every time the server is loaded.
Is the site-spec MCP server still maintained?
site-spec is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the site-spec MCP server under?
site-spec declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.