net.spintax/mcp · v1.2.2 · communication
spintax.net MCP server is healthy: it completed an MCP handshake in 2064 ms and exposes 4 tools.
Write, validate, render and analyze spintax templates. Backed by @spintax/core. No auth.
Endpoint: https://spintax.net/mcp (streamable-http)
No repository listed · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 4 |
| Latency | 2064 ms |
| Last checked (UTC) | 2026-10-15T12:50:08.172Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-15T12:50:08.172Z | Healthy | 2064 |
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 knownVari |
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. |
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. |
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 as |