Site MCP server
io.github.bounded-systems/site-mcp·v0.2.0Read-only MCP server over robertdelanghe.dev's Sigstore-verified static API (stdio).
0 stars29 downloads/wk
Reviews
Write oneNobody has reviewed Site yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Site tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it
- Code scan11 source files scanned25/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 12 days ago15/15
- Maintainer identityregistry namespace matches repository owner7/10
How Site compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 91/100
- higher than 85% of 48,255 servers
- Downloads a week
- 29
- more than 16% of 12,191 servers with a package
Install Site in Claude Code, Cursor or VS Code
Runs npx -y @bounded-systems/site-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add site-mcp -- npx -y @bounded-systems/site-mcp
What the publisher says
From the Site repository's README, as published. We do not edit it. Read it on GitHub
@bounded-systems/site-mcp
A local, read-only MCP server (and a matching CLI) over robertdelanghe.dev's signed static API.
It exposes the site's identity data — profile, writing, the GitHub corpus, the résumé credential, the OpenAPI doc — to any MCP client (Claude Desktop, Claude Code, etc.), and verifies every response byte-for-byte against the site's Sigstore-signed sha256 manifest before handing it back. If the bytes a client would receive don't match the signed manifest, it refuses to return them.
It runs locally over stdio — the client spawns it as a subprocess. There is no hosted server and no network listener, which preserves the site's static / no-attack-surface posture.
A thin implementation of a generic core
This package is now thin. All of the reusable machinery — the verifying fetch client, the sha256 manifest + Sigstore checks, and the VerbSpec → MCP (tools + resources) / VerbSpec → CLI projection — lives in @bounded-systems/static-mcp. site-mcp supplies only:
getconformance, getcorpus, each authored once as a @bounded-systems/verbspec VerbSpec;
- the verbs (src/verbs.ts) — listposts, getpost,
site://… resources;
- the resource catalog (src/catalog.ts) — the
expected signer identity; and
- the config values (src/config.ts) — the origin and
hands the spec to the core.
- the entry (src/index.ts) — which picks a surface and
src/verbs.ts ─┐
src/catalog.ts ├─▶ buildSiteSpec(config) ─▶ @bounded-systems/static-mcp
src/config.ts ─┘ serveVerifiedStaticMcp(spec, config) (MCP, stdio)
runStaticCli(spec, config, argv) (CLI)Two surfaces, one definition. verbspec projects each verb to both an
MCP tool and a CLI subcommand. The exact same verb set backs site-mcp's MCP
tools and its CLI commands — no second definition, no drift.
Install / run
Requires Node ≥ 18.17. site-mcp's verbspec dependency is published to JSR, so installs resolve it through JSR's npm bridge — the included .npmrc sets @jsr:registry=https://npm.jsr.io. (Consuming from a fresh environment, add that one line to your npm config.)
# MCP server over stdio (what an MCP client launches):
npx -y @bounded-systems/site-mcp
# CLI — the SAME verbs, printing the verified JSON:
npx -y @bounded-systems/site-mcp list_posts
npx -y @bounded-systems/site-mcp get_conformance # the index
npx -y @bounded-systems/site-mcp get_conformance accessibility # one area
npx -y @bounded-systems/site-mcp get_conformance --full # every criterion
npx -y @bounded-systems/site-mcp get_corpus # the index
npx -y @bounded-systems/site-mcp get_corpus topics # one full list
npx -y @bounded-systems/site-mcp get_post agent-authored-code-driftThe MCP server logs a readiness line to stderr (stdout is the MCP channel):
site-mcp ready (stdio) → https://robertdelanghe.dev; signature mode=offMCP client configuration
{
"mcpServers": {
"robertdelanghe": {
"command": "npx",
"args": ["-y", "@bounded-systems/site-mcp"],
"env": { "SITE_MCP_SIGNATURE_MODE": "warn" }
}
}
}Resources
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Site: common questions
- Is Site MCP server safe?
- Yes, by our scan: it is graded A (91/100). Read the Site safety report
- How do I install Site?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Site need an API key?
- No secret keys are declared. It reads 1 setting from the environment.
- Is Site maintained?
- The last commit was 50 days ago (2026-09-14). The latest release is v0.2.0.
- How does Site compare with other MCP servers?
- safety score 91/100 (higher than 85% of 48,255 servers); downloads a week 29 (more than 16% of 12,191 servers with a package). Full comparison.