# site-spec (npm · site-spec-mcp)

MCP server: audit any website for SEO, accessibility, and AI-searchability, then auto-fix it.

- Trust score: 82/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- npm · `site-spec-mcp`: 82/100 (this document), [markdown](https://verifymcp.io/servers/ariaxhan-site-spec/site-spec-mcp.md), [page](https://verifymcp.io/servers/ariaxhan-site-spec/site-spec-mcp)

## Channel facts

- Registry: `npm`
- Package: `site-spec-mcp`
- Version: `0.3.2`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 24 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

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

### Claude

```bash
claude mcp add ariaxhan-site-spec -- npx -y site-spec-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "ariaxhan-site-spec": {
      "command": "npx",
      "args": [
        "-y",
        "site-spec-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ariaxhan-site-spec": {
      "command": "npx",
      "args": [
        "-y",
        "site-spec-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add ariaxhan-site-spec -- npx -y site-spec-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ariaxhan-site-spec": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "site-spec-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ariaxhan-site-spec --command npx --arg -y --arg site-spec-mcp
```

### Hermes

```yaml
mcp_servers:
  ariaxhan-site-spec:
    command: "npx"
    args: ["-y", "site-spec-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "ariaxhan-site-spec": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "site-spec-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add ariaxhan-site-spec -t stdio -c npx -a -y site-spec-mcp
```

### Other

```json
{
  "mcpServers": {
    "ariaxhan-site-spec": {
      "command": "npx",
      "args": [
        "-y",
        "site-spec-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 82, +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.

### 2026-09-17 (score 81, +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.

### 2026-09-15 (score 80, +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.

### 2026-09-13 (score 79, +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.

### 2026-09-10 (score 78, +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.

### 2026-09-08 (score 77, +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.

### 2026-09-06 (score 76, +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.

### 2026-09-04 (score 75, +4)

- [functional improvement] Stability: unverified → 0.27

## MCP tools (4)

### `audit_site` (~228 tokens)

Audit a website's invisible foundation

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.

Input parameters:

- `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, required): The site to audit: a URL (https://example.com, or bare example.com), or a path to a local directory of built output.

### `fix_issue` (~256 tokens)

Auto-fix one audit finding

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.

Input parameters:

- `check_id` (string, required): 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, required): 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).

### `compile_spec` (~227 tokens)

Compile business data into a SiteSpec and a deployable site

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.

Input parameters:

- `business` (object, required): 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.

### `list_checks` (~70 tokens)

List every audit check

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.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/ariaxhan-site-spec/site-spec-mcp#diagnostics

## Score history

- 2026-09-20: 82
- 2026-09-19: 82
- 2026-09-18: 81
- 2026-09-17: 81
- 2026-09-16: 80
- 2026-09-15: 80
- 2026-09-14: 79
- 2026-09-13: 79
- 2026-09-12: 78
- 2026-09-11: 78
- 2026-09-10: 78
- 2026-09-09: 77
- 2026-09-08: 77
- 2026-09-07: 76
- 2026-09-06: 76
- 2026-09-05: 75
- 2026-09-04: 75
- 2026-09-03: 71
- 2026-09-02: 71
- 2026-09-01: 71
- 2026-08-31: 71
- 2026-08-30: 70
- 2026-08-29: 71
- 2026-08-28: 71
- 2026-08-27: 56

## Common questions

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

## Links

- npm package: https://www.npmjs.com/package/site-spec-mcp
- Socket report: https://socket.dev/npm/package/site-spec-mcp
- Repository: https://github.com/ariaxhan/site-spec
- Changelog RSS feed: https://verifymcp.io/servers/ariaxhan-site-spec/site-spec-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ariaxhan-site-spec/site-spec-mcp.json
- HTML version of this page: https://verifymcp.io/servers/ariaxhan-site-spec/site-spec-mcp