spintax.net MCP server
NPM · @SPINTAX/MCP · 2 COMPONENTS
Write, validate, render and analyze spintax templates. Backed by @spintax/core. No auth.
Available components
Last scanned (9 hours ago)
Scores higher than 93% of npm servers
Category Developer Tools
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
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Cryptographically verified build provenance (signed, bound to investblog/spintax-js). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 16 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 854 tokens (~213/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
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.
- 5 Nov 26 0
- Package version: 0.4.2 → 0.4.4 functional
- 28 Oct 26 +1
- Stability: 0.97 → pass security
- 27 Oct 26 −1
- Stability: pass → 0.97 functional
- 23 Oct 26 0
- Package version: 0.4.2 → 0.4.4 functional
- 21 Oct 26 +1
- Stability: 0.97 → pass security
- 19 Oct 26 −1
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: pass → 0.93 functional
- Package version: 0.4.2 → 0.4.4 functional
- Package version: 0.4.2 → 0.4.3 functional
- 17 Oct 26 +3
- Stability: 0.83 → pass security
- 15 Oct 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.
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 5 Nov 2026 · Analysed npm/@spintax/mcp@0.4.4
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.4.4 |
| Rekor log index | 3319548825 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:4c8618c4f402bc223638cf09039c0bb926f86a3662f367566baadf2a16f6e74f819d16626b21304d2695f9583dc0f8542b1005646ab497f478690d2f6 |
Background: How many MCP packages publish verified provenance →
Dependencies 2 packages
| Packages resolved | 2 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
analyze_spintax Analyze a spintax template ~158
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.
| Name | Type | Req | Description |
|---|---|---|---|
| knownVariables | array | – | – |
| locale | string | – | Locale for {plural …} arity, e.g. "en" (2-form), "ru" (3-form: ru/uk/be/sr/hr/bs) or "ar" (6-form). Omit for the 2-form default. |
| template | string | yes | Spintax template source. #include is disabled on this server. |
| Name | Type | Req | Description |
|---|---|---|---|
| constructs | object | yes | – |
| defs | array | yes | – |
| diagnostics | array | yes | – |
| includes | array | yes | – |
| refs | array | yes | – |
| sets | array | yes | – |
No examples provided.
render_spintax Render spintax variants ~206
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | – | Variable map, e.g. {"CITY": "Prague"}. Overrides #set/#def definitions. |
| count | integer | – | Number of variants (1–50). |
| locale | string | – | Locale for {plural …} arity, e.g. "en" (2-form), "ru" (3-form: ru/uk/be/sr/hr/bs) or "ar" (6-form). Omit for the 2-form default. |
| seed | string|number | – | Deterministic RNG seed; omit for random output. |
| template | string | yes | Spintax template source. #include is disabled on this server. |
| Name | Type | Req | Description |
|---|---|---|---|
| variants | array | yes | – |
No examples provided.
spintax_authoring_guide How to write a spintax template ~186
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; for ar, the six plural forms and their order. Returns text to read, not a template.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Language you will author in, e.g. "en" or "ru". Selects the grammar rules and the worked examples. Omit for the language-neutral rules only. |
| variationLevel | string | – | How much markup to use. Omit to decide for yourself — the guide then states no level. |
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | – |
| promptVersion | string | yes | Version of the rules TEXT (@spintax/authoring-prompt PROMPT_VERSION). Moves when the wording changes in a way that can change what a model writes. |
| rules | string | yes | The authoring rules, as text to read. |
No examples provided.
validate_spintax Validate a spintax template ~185
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.
| Name | Type | Req | Description |
|---|---|---|---|
| knownVariables | array | – | Variable names the caller will supply at render time (case-insensitive). |
| locale | string | – | Locale for {plural …} arity, e.g. "en" (2-form), "ru" (3-form: ru/uk/be/sr/hr/bs) or "ar" (6-form). Omit for the 2-form default. |
| template | string | yes | Spintax template source. #include is disabled on this server. |
| Name | Type | Req | Description |
|---|---|---|---|
| diagnostics | array | yes | – |
| errorCount | integer | yes | – |
| valid | boolean | yes | True when no error-severity diagnostics. |
| warningCount | integer | yes | – |
No examples provided.
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
claude mcp add net-spintax-mcp -- npx -y @spintax/mcp
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 89 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 735 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 5 November 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.