_ registry / mcp streamable-http · checked 1h ago

spintax-net

https://spintax.net

Registry code: 2b8fe71e06980fb4

api record

Spintax template tools backed by @spintax/core, the reference engine. validate_spintax returns diagnostics with line/column; render_spintax produces seeded variants; analyze_spintax reports variables, directives and construct counts; spintax_authoring_guide returns the authoring rules for a locale — call it BEFORE writing a template, the verifiers cannot teach what a template lacks. #include is disabled. Docs: https://spintax.net/llms.txt (Markdown mirrors of every page).

endpoint
https://spintax.net/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is spintax-net live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is spintax-net free to use?
Yes — the hub reached it with no key and no payment.
What tools does spintax-net have?
4 tools: analyze_spintax, validate_spintax, render_spintax, spintax_authoring_guide.
Is spintax-net safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.8%· all time 99.8%

latency
287ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 586 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
used for
  • validate a spintax template
  • render text variants from spintax
  • read spintax authoring rules
takes → gives
text → text
tools
4 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
1 open 3 never probed 1 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • spintax_authoring_guide reads open 9h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "locale": {
          "type": "string",
          "description": "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": {
          "enum": [
            "conservative",
            "balanced",
            "aggressive"
          ],
          "type": "string",
          "description": "How much markup to use. Omit to decide for yourself — the guide then states no level."
        }
      },
      "additionalProperties": false
    }
    arguments 19 lines
  • analyze_spintax reads unknown 9h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "template"
      ],
      "properties": {
        "locale": {
          "type": "string",
          "description": "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": {
          "type": "string",
          "maxLength": 8192,
          "description": "Spintax template source (max 8192 characters). #include is disabled on this server."
        },
        "knownVariables": {
          "type": "array",
          "items": {
            "type": "string"
          }
        }
      },
      "additionalProperties": false
    }
    arguments 24 lines
  • validate_spintax reads unknown 9h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "template"
      ],
      "properties": {
        "locale": {
          "type": "string",
          "description": "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": {
          "type": "string",
          "maxLength": 8192,
          "description": "Spintax template source (max 8192 characters). #include is disabled on this server."
        },
        "knownVariables": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Variable names the caller will supply at render time (case-insensitive)."
        }
      },
      "additionalProperties": false
    }
    arguments 25 lines
  • render_spintax reads unknown 23h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "template"
      ],
      "properties": {
        "seed": {
          "type": [
            "string",
            "number"
          ],
          "description": "Deterministic RNG seed; omit for random output."
        },
        "count": {
          "type": "integer",
          "default": 3,
          "maximum": 20,
          "minimum": 1,
          "description": "Number of variants (1–20)."
        },
        "locale": {
          "type": "string",
          "description": "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."
        },
        "context": {
          "type": "object",
          "description": "Variable map, e.g. {\"CITY\": \"Prague\"}. Overrides #set/#def definitions.",
          "additionalProperties": {
            "type": "string"
          }
        },
        "template": {
          "type": "string",
          "maxLength": 8192,
          "description": "Spintax template source (max 8192 characters). #include is disabled on this server."
        }
      },
      "additionalProperties": false
    }
    arguments 39 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 2b8fe71e06980fb4.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/2b8fe71e06980fb4/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/2b8fe71e06980fb4/badge.svg)](https://brick.blue/agent/2b8fe71e06980fb4?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.