# @spintax/mcp

Local MCP server for spintax templates — validate, render and analyze over stdio with @spintax/core, no network and no size caps. Ships the shared tool module and JSON-RPC dispatcher the hosted server at spintax.net/mcp is built to run from.

- **Type:** MCP server
- **Trust:** 85/100 (A), scored on the package rubric
- **Verification:** verified (build provenance)
- **Version:** 0.3.2
- **Author:** 301st
- **License:** MIT
- **npm:** @spintax/mcp
- **Endpoints:** streamable-http https://spintax.net/mcp
- **Source:** https://github.com/investblog/spintax-js
- **Endpoint health:** reachable (last checked 2026-09-21T21:02:31.342Z, 4 samples) — uptime is not a security property and is not part of the trust score
- **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport)

## Trust

85/100 (A), scored on the package rubric
- Publisher verified: no
- Build provenance: verified attestation
- npm trusted publishing (OIDC): yes
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 25 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-08-29T21:42:36.528Z
- **Version scanned:** 0.3.0
- **CVEs:** none found by OSV at scan time

## Tools

5 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `validate_spintax` — Static validation: returns diagnostics with severity, stable code, message and 1-based line/column. No "error"-severity diagnostic means the template is structu
- `render_spintax`
- `analyze_spintax` — Reports what the template needs and contains: refs (variables referenced), sets (#set macros, re-picked per reference), defs (#def, rolled once per render), inc
- `spintax_authoring_guide` — Read this BEFORE writing or editing a spintax template — it is the canonical authoring guide the whole spintax toolchain is written against, not a tutorial. Pas
- `spintax-local`

## Install

**Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"mcp\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@spintax/mcp\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Contained to extensive — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs locally and hosted; read-only tool surface.
- Floor 16, ceiling 34 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/%40spintax%2Fmcp
- Install plan: https://forgeregistry.com/api/v1/packages/%40spintax%2Fmcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40spintax%2Fmcp
- HTML page: https://forgeregistry.com/registry/%40spintax%2Fmcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.