Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

spintax.net MCP server

NPM · @SPINTAX/MCP · 2 COMPONENTS · SCANNED SEP 21

Write, validate, render and analyze spintax templates. Backed by @spintax/core. No auth.

+16 this week 88 Trust /100
Trust breakdown (7 categories)

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
  • 0 of 2 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency71
Schema Quality & AI Usability69
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 822 tokens (~205/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 Management97
  • Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 92% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.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 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the spintax.net MCP server server?

spintax.net MCP server runs locally as an npm package, launched with npx -y @spintax/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 · @spintax/mcp

# add to Claude Code
claude mcp add net-spintax-mcp -- npx -y @spintax/mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "net-spintax-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@spintax/mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "net-spintax-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@spintax/mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add net-spintax-mcp -- npx -y @spintax/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "net-spintax-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@spintax/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add net-spintax-mcp --command npx --arg -y --arg @spintax/mcp
# ~/.hermes/config.yaml
mcp_servers:
  net-spintax-mcp:
    command: "npx"
    args: ["-y", "@spintax/mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "net-spintax-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@spintax/mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add net-spintax-mcp -t stdio -c npx -a -y @spintax/mcp
// mcp.json
{
  "mcpServers": {
    "net-spintax-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@spintax/mcp"
      ]
    }
  }
}
Changelog

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.

  • 21 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 −1
    • Stability: pass → 0.87 functional
  • 16 Sept 26 0
    • Stability: 0.97 → pass security
  • 15 Sept 26 +16
    • Malware scan: unverified → pass security
  • 13 Sept 26 0
    • Malware scan: unverified → pass security
    • Package version: 0.3.1 → 0.3.2 functional
  • 12 Sept 26 −14
    • Malware scan: pass → unverified security
    • Stability: 0.83 → unverified security
    • Tool safety: pass → unverified security
    • Capabilities: pass → unverified functional
    • Tool coverage: 100 → unverified functional
    • First check of Schema quality: unverified functional
    • Package version: 0.3.0 → 0.3.1 functional
  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 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 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 21 Sept 2026 · Analysed npm/@spintax/mcp@0.3.2

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo investblog/spintax-js
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/investblog/spintax-js/.github/workflows/release-mcp.yml@refs/tags/mcp-v0.3.2
Rekor log index 2821157406
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:0b7f231841b2df67b89081a0dee49536df360d303ab1f8dd32562a64e26974d23d1bc798f0afb6d1c63bcec3e6b12090db434006952d2992419b9f211

Background: How many MCP packages publish verified provenance →

Dependencies 2 packages
Packages resolved 2
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~703 tokens

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 →

Tool Tokens
analyze_spintax ~151

Reports what the template needs and contains: refs (variables referenced), sets (#set macros, re-picked per reference), defs (#def, rolled once per render), includes, diagnostics, and best-effort construct counts. Answers "what variables must I supply" — it is NOT a variant-cardinality counter.

NameTypeReqDescription
knownVariablesarray
localestringLocale for {plural …} arity, e.g. "en" (2-form) or "ru" (3-form: ru/uk/be/sr/hr/bs). Omit for the 2-form default.
templatestringyesSpintax template source. #include is disabled on this server.
NameTypeReqDescription
constructsobjectyes
defsarrayyes
diagnosticsarrayyes
includesarrayyes
refsarrayyes
setsarrayyes

No examples provided.

render_spintax ~199

Renders up to 50 variants. With a seed the output is deterministic (variant i uses seed "<seed>#<i>"); without one it is random. The engine is lenient: structural mistakes never throw, they surface in the output — run validate_spintax first.

NameTypeReqDescription
contextobjectVariable map, e.g. {"CITY": "Prague"}. Overrides #set/#def definitions.
countintegerNumber of variants (1–50).
localestringLocale for {plural …} arity, e.g. "en" (2-form) or "ru" (3-form: ru/uk/be/sr/hr/bs). Omit for the 2-form default.
seedstring|numberDeterministic RNG seed; omit for random output.
templatestringyesSpintax template source. #include is disabled on this server.
NameTypeReqDescription
variantsarrayyes

No examples provided.

spintax_authoring_guide ~175

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. Pass the locale you will author in: for ru/uk/be and sr/hr/bs it carries the agreement and case rules that decide whether the variants read as human writing, which is the hard part and the part a valid template can still get wrong. Returns text to read, not a template.

NameTypeReqDescription
localestringLanguage you will author in, e.g. "en" or "ru". Selects the grammar rules and the worked examples. Omit for the language-neutral rules only.
variationLevelstringHow much markup to use. Omit to decide for yourself — the guide then states no level.
NameTypeReqDescription
localestring
promptVersionstringyesVersion of the rules TEXT (@spintax/authoring-prompt PROMPT_VERSION). Moves when the wording changes in a way that can change what a model writes.
rulesstringyesThe authoring rules, as text to read.

No examples provided.

validate_spintax ~178

Static validation: returns diagnostics with severity, stable code, message and 1-based line/column. No "error"-severity diagnostic means the template is structurally sound — read the warnings before rendering, because some of them (plural.locale-missing) mean a block will not resolve. Pass knownVariables for names you will supply at render time to silence their variable.undefined warnings.

NameTypeReqDescription
knownVariablesarrayVariable names the caller will supply at render time (case-insensitive).
localestringLocale for {plural …} arity, e.g. "en" (2-form) or "ru" (3-form: ru/uk/be/sr/hr/bs). Omit for the 2-form default.
templatestringyesSpintax template source. #include is disabled on this server.
NameTypeReqDescription
diagnosticsarrayyes
errorCountintegeryes
validbooleanyesTrue when no error-severity diagnostics.
warningCountintegeryes

No examples provided.

Common questions

What is the spintax.net MCP server server?

spintax.net MCP server is listed in the public MCP registry as net.spintax/mcp. Write, validate, render and analyze spintax templates. Backed by @spintax/core. No auth. This page covers its npm package (@spintax/mcp).

Is the spintax.net MCP server server safe to use?

spintax.net MCP server scores 88 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 spintax.net MCP server server expose?

spintax.net MCP server exposes 4 tools: validate_spintax, render_spintax, analyze_spintax, spintax_authoring_guide. Their descriptions and schemas cost roughly 703 tokens of context every time the server is loaded.

Is the spintax.net MCP server server still maintained?

spintax.net MCP server is still listed as active in the MCP registry. We last reached this channel on 21 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 spintax.net MCP server server under?

spintax.net MCP server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.