site-spec

Name: site-spec
Author: ariaxhan

by ariaxhanversion 0.3.2i★ –iRuns on your computer

Registry nameio.github.ariaxhan/site-spec

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Marketing & social media

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

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

Run this in your terminal

claude mcp add site-spec -- npx -y site-spec-mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "site-spec": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "site-spec-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account ariaxhan, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Marketing & social mediai

More stars than 0% of the other 3569 servers in this category
Published to the registry more recently than 28% of the other 3569 servers in this category
Basic checks equal to or better than 100% of the other 3569 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is site-spec safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.3.2) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: MCP YouTube Transcript, Google Analytics MCP, BibiGPT YouTube Video Summarizer

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

MCP YouTube Transcript

by jkawamoto

An MCP server retrieving transcripts of YouTube videos

Runs on your computer★ 495MITUpdated 10 days ago

Install

Google Analytics MCP

by surendranb

GA4 MCP server for AI agents: schema discovery, server-side aggregation, analysis-ready defaults.

Runs on your computer★ 244MITUpdated 10 days ago

Install

BibiGPT YouTube Video Summarizer

by JimmyLv

AI video summarizer: summarize and transcribe YouTube, Bilibili, TikTok and podcast videos.

Runs in the cloud★ 137MITUpdated 11 days ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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 list_checks to learn the check ids and audit_site on a URL.

claude mcp add site-spec -- npx -y site-spec-mcp

Gemini 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](https://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 ./fixed

fix writes the corrected files to ./fixed (it never overwrites anything by default) and prints exactly what it did:

✓ Fixed automatically (8)

audit/robots-stale-token robots.txt — Removed deprecated crawler block "anthropic-ai". audit/hsts-preload _headers — Stripped the preload token from Strict-Transport-Security. audit/canonical-missing admin/index.html — Inserted . audit/og-missing admin/index.html — Added Open Graph card from the page's title + description. audit/noindex admin/index.html — Removed accidental noindex from .

✎ Scaffolded — needs your facts (2) audit/llms-missing llms.txt — Scaffolded from page titles/descriptions; fill the TODO facts. audit/jsonld-missing index.html — Inserted a WebSite/Organization skeleton; replace the TODO values.

⚠ Needs manual attention (3) audit/google-fonts-cdn index.html — Self-host the woff2 files to stop the IP leak (GDPR). audit/img-dims-missing index.html — without width/height (layout shift). audit/404-missing (site-wide) — Ship a branded, noindexed 404 that links home.

fixed 8, scaffolded 2, manual 3 wrote 4 file(s) to ./fixed

Drop audit into CI with a non-zero exit on errors to gate deploys. Both commands work on a build/output directory too — just pass a path instead of a URL.

Use it from your coding agent (MCP)

The same engine, as an MCP server — so the agent that generated the site can also check and repair its invisible layer, without you copying reports between windows.

claude mcp add site-spec -- npx -y site-spec-mcp

Codex ( ~/.codex/config.toml )

[mcp_servers.site-spec]

command = "npx" args = ["-y", "site-spec-mcp"]

Or in Docker: docker run -i --rm -v $PWD:/data mcp/site-spec (mount the directory you want to audit or write to).

Four tools:

Tool	What it does
`audit_site`	Crawl a live URL (or read a local build directory) and return every finding: check id, severity, file, and whether it can be auto-fixed.
`fix_issue`	Apply the deterministic repair for one check id and return the diff — or write it, for a local directory.
`compile_spec`	Turn verified business facts into a validated SiteSpec and the deployable files it renders to.
`list_checks`	Enumerate every check the engine can raise, with a one-line description and its fix availability.

The server calls the engine in-process. It never shells out to the CLI and never hops to the hosted worker — all three are siblings over one library.

flowchart LR

A["MCP client (Claude Code, Codex)"] -- stdio JSON-RPC --> B["site-spec-mcp"] B --> C["@site-spec/core/io fetchSite · readSiteDir"] C -- "file map" --> D["@site-spec/core auditFiles · fixFiles · buildSite"] D -- "findings / files" --> B B -- "JSON" --> A

Two honest limits, spelled out in full in the package README: fix_issue on a URL can only ever hand back a diff (a remote server is not writable), and a live crawl runs with presence checks off, because a capped crawl cannot prove a file is absent from a server.

Details — what it checks, how it fixes, the philosophy, install

What it checks

Seven areas. Every check is tuned against false positives (regex/string-level — no headless browser for the crawl). Findings are error (breaks something) or warning (worth a look), each with a concrete fix.

Area	What it catches
SEO / findability	missing / description / canonical · accidental `noindex` (both and the `X-Robots-Tag` header) · missing Open Graph cards · zero-or-many · a sitemap that lists pages which don't exist
Accessibility	images with no `alt` · zoom-blocking viewport (`user-scalable=no`) · images with no width/height (layout shift)
Privacy & security	mixed content · trackers + cookies with no consent/disclosure story · Google Fonts from Google's CDN (a ruled GDPR violation) · header hygiene (HSTS preload risk, report-only CSP that reports nowhere, dead FLoC / `X-XSS-Protection` config) · inline `onclick=` handlers that block a future CSP
Performance	hero/LCP image set to `loading="lazy"` · no `Cache-Control`
Structured data	invalid JSON-LD (crawlers drop the whole block) · self-serving `aggregateRating`/`review` markup (a Google penalty since 2019)
Integrity	dangling assets that 404 · broken internal links
AI searchability	`robots.txt` blocking AI answer agents (`OAI-SearchBot`, `ChatGPT-User`, `Claude-User`, `PerplexityBot`…) · dead crawler tokens · missing `llms.txt` · missing/broken structured data · client-rendered shells AI crawlers see as blank

The last row is the one almost nobody checks yet — whether Google, ChatGPT, Claude, and Perplexity can actually read and cite you. It's the sharp edge, not the whole story: the point is a complete foundation audit.

How `fix` decides

Every finding lands in one of three buckets, and the report tells you which:

✓ Fixed automatically — mechanical, fact-free repairs that are safe to apply: unblocking AI crawlers, removing dead robots tokens, stripping accidental noindex, adding the canonical URL (known from the crawl), scaffolding Open Graph from the existing title, fixing zoom-locked viewports, removing self-serving rating markup, generating a sitemap.xml from the crawled pages, header hygiene.
✎ Scaffolded — things that need *your* real facts: llms.txt, a JSON-LD entity, a meta description. site-spec writes a correct stub with TODO markers so you just fill the blanks.
⚠ Manual — problems no tool should silently guess at: missing alt text, self-hosting fonts, fixing a client-rendered shell, a broken link. You get a precise instruction, never a silent edit.

fix is non-destructive by default (writes to an output dir). Pass --write to edit a local directory in place.

The philosophy

Correctness is a policy, not a prompt. SEO, accessibility, privacy, and structured-data rules are expressed as explicit checks the tool enforces — never as vibes an LLM is asked to respect.
Deterministic. The audit engine is pure: same input → the same report, byte-for-byte. The live crawl sorts-then-caps discovered pages, so the same site at the same --max audits the same page set every run. No network, no randomness inside the engine.
Fix, don't lecture. A finding that can be repaired safely gets repaired. One that needs a human says exactly what the human must do.
Source-agnostic. It audits the output, not the toolchain. AI, framework, CMS, hand-coded — all the same to it.

site-spec started as a deterministic *compiler* that builds sites with a correct

foundation by construction (the build command and the docs/ still cover it).

The durable value turned out to be the inverse: not generating whole sites, but

auditing and repairing the foundation of sites that already exist.

The full CLI

site-spec audit <dir|url> [--max N] [--json] [--report report.md]

site-spec fix [--out dir] [--write] [--max N] [--json] site-spec build --out [--target cloudflare|netlify|vercel|static]

--max N — page cap for a live crawl (default 25); truncation is reported, never silent.
--report report.md — write the audit as a shareable Markdown document.
--json — the full structured report for scripting/CI.

Install / develop

git clone https://github.com/ariaxhan/site-spec.git

cd site-spec npm install npm test # unit + golden tests npm run verify # html-validate + JSON-LD + axe over the demo output

Packages

Package	Responsibility
`site-spec` (npm)	The published CLI — `audit` · `fix` · `build`. Self-contained; this is what `npx site-spec` runs.

| @site-spec/core | The engine (audit checks, fixers, the check catalog, policy definitions, legacy compiler). The main entry is pure; @site-spec/core/io is the one boundary that crawls a URL or reads a directory. Bundled into the CLI and the MCP server; not

Only the beginning is shown; read the rest in the repo

site-spec

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Marketing & social mediai

Common questions

Alternatives

MCP YouTube Transcript

Google Analytics MCP

BibiGPT YouTube Video Summarizer

README from the maker

site-spec

For agents

The problem

The solution

Try it without installing anything

How to use

2. Fix it — auto-repair the mechanical issues, scaffold the rest

Use it from your coding agent (MCP)

What it checks

How fix decides

The philosophy

The full CLI

Install / develop

Packages

How `fix` decides