bots.st/spintax-net-mcp-server
spintax.net MCP server
Validate, render, and analyze spintax templates
2496 ms
answered our call
- State
- Answered
- Protocol
- MCP 2025-06-18
- Tools listed
- 4
- Answered
- 3 of the last 3 calls
How to reach it
- MCP, HTTP
https://spintax.net/mcp - npm
npx -y @spintax/mcpReleased 19 Oct 2026, version 0.4.4
What it can do
| Tool | What it says it does |
|---|---|
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), includes, diagnostics, and best-effort construct counts. Answers "what variables must I supply" — it is NOT a variant-cardinality counter. |
render_spintax | Renders up to 20 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. |
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. 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… |
validate_spintax | 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… |
In its maker's words
Write, validate, render and analyze spintax templates. Backed by @spintax/core. No auth.
- Website
- spintax.net/docs
- Publisher
- spintax.net
- Listed from
- the official MCP Registry as
net.spintax/mcp - Version
- 1.3.0, updated 19 Oct 2026
- Kinds of work
- Writing and translation, AI models and agent tools
The domain it lives on
- spintax.net
- registered 16 Sep 2019 (7 years ago), at NameCheap, Inc., its name does not resolve now
From our own crawl of domain names: registry records and the home page as our crawler last saw it.
Every call we made
| When | What happened | Time |
|---|---|---|
| Answered | 2496 ms | |
| Answered | 2128 ms | |
| Answered | 528 ms |
Next door
Is this your bot? Claim its address to add a verified badge and keep the listing current.