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

REMOTE · SPINTAX.NET · 2 COMPONENTS · SCANNED SEP 21

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

Available components

remote · spintax.net 84 npm · @spintax/mcp 88
0 this week 84 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security66
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability87
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 2189 tokens (~70/item across 31 items; 4 tools + 27 resources), lean.Pass
  • 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 6 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 is a hosted endpoint at https://spintax.net/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · spintax.net

# add to Claude Code
claude mcp add --transport http net-spintax-mcp 'https://spintax.net/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "net-spintax-mcp": {
      "url": "https://spintax.net/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "net-spintax-mcp": {
      "type": "http",
      "url": "https://spintax.net/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.net-spintax-mcp]
url = "https://spintax.net/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "net-spintax-mcp": {
      "type": "remote",
      "url": "https://spintax.net/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add net-spintax-mcp --url 'https://spintax.net/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  net-spintax-mcp:
    url: "https://spintax.net/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "net-spintax-mcp": {
      "Transport": "http",
      "Url": "https://spintax.net/mcp"
    }
  }
}
# add to Vellum
assistant mcp add net-spintax-mcp -t streamable-http -u 'https://spintax.net/mcp'
// mcp.json
{
  "mcpServers": {
    "net-spintax-mcp": {
      "type": "http",
      "url": "https://spintax.net/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 13 Sept 26 0
    • Server version: 1.1.1 → 1.1.2 functional
  • 12 Sept 26 0
    • Server version: 1.1.0 → 1.1.1 functional
  • 3 Sept 26 +1
    • Stability: 0.97 → pass security
  • 31 Aug 26 +1

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

  • 29 Aug 26 +1

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

  • 27 Aug 26 +1

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

  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 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 · Probed https://spintax.net/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=spintax.net CN=WE1,O=Google Trust Services,C=US 14 Sept 2026 13 Dec 2026 ECDSA 256 ECDSA-SHA256 8d7c5e2408d42f0e1318f46051d2c542
SANs: spintax.net
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of spintax.net. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
net. present 37331 13 Verified
spintax.net. present 2371 13 Verified
spintax.net. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=15552000; includeSubDomains; preload

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://spintax.net/mcp Verified 200
http (plaintext) http://spintax.net/mcp HTTPS enforced 301 https://spintax.net/mcp
MCP tools · 4 exposed · ~721 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 ~157

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––
localestring–Locale 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 (max 8192 characters). #include is disabled on this server.
NameTypeReqDescription
constructsobjectyes–
defsarrayyes–
diagnosticsarrayyes–
includesarrayyes–
refsarrayyes–
setsarrayyes–

No examples provided.

render_spintax ~205

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.

NameTypeReqDescription
contextobject–Variable map, e.g. {"CITY": "Prague"}. Overrides #set/#def definitions.
countinteger–Number of variants (1–20).
localestring–Locale 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|number–Deterministic RNG seed; omit for random output.
templatestringyesSpintax template source (max 8192 characters). #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
localestring–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.
variationLevelstring–How 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 ~184

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
knownVariablesarray–Variable names the caller will supply at render time (case-insensitive).
localestring–Locale 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 (max 8192 characters). #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 hosted endpoint (https://spintax.net/mcp).

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

spintax.net MCP server scores 84 out of 100 on VerifyMCP. 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 721 tokens of context every time the server is loaded.

Does the spintax.net MCP server server require authentication?

No. We connected to spintax.net MCP server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

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.