bots.st/tabnas
tabnas
Parse and validate text against grammar
3047 ms
answered our call
- State
- Answered
- Protocol
- MCP 2025-06-18
- Tools listed
- 7
- Answered
- 3 of the last 3 calls
How to reach it
- MCP, HTTP
https://mcp.tabnas.dev/mcp - npm
npx -y @tabnas/mcpReleased 8 Oct 2026, version 0.1.20
What it can do
| Tool | What it says it does |
|---|---|
compare_grammars | Grammar compatibility (AX plan Phase 5): does candidate grammar B still accept what baseline A accepted, and does it build the same tree for inputs both accept? Returns EVIDENCE AND CONFIDENCE, never a bare verdict: {normalForm, proven[], observed[], changes[], counterexamples[], confidence, why}… |
describe_plugin | The full descriptor for one plugin, by package name ('@tabnas/csv') or bare fleet name ('csv'). Unknown names get {ok:false, errors} naming the known plugins. |
explain_parse_error | Parse input and explain the failure. Returns {failed:false} when the input parses; otherwise {failed:true, diagnostic, registry} where registry is the error-code registry entry {code,message,hint} for the diagnostic code (resource tabnas://errors), or null for a code the bundled registry does not… |
list_plugins | List every bundled tabnas plugin descriptor (tabnas.plugin.json of each fleet repo), sorted by name. Returns {plugins:[...]}. |
parse | Parse input with the tabnas engine. Returns {ok:true, tree} or, on parse failure, {ok:false, diagnostic} — the structured diagnostic described by resource tabnas://schema/diagnostic. An invalid grammar is rejected as {ok:false, errors:[{path,message}]}. Without a grammar the bare engine is used… |
test_grammar | Run TSV fixture content against a grammar in a fresh instance, using the fleet fixture convention (@tabnas/support): line 1 is a header, the input column is escape-decoded, the expected column is JSON or ERROR / ERROR:<code>. Returns {pass, fail, rows:[{row,input,expected,got,ok}]}. Refuses more… |
validate_grammar | Validate a serialized GrammarSpec. Structural validation against the bundled grammar schema, an engine load in a fresh instance, and a check that every rule reference (`p`, `r`) names a rule the grammar actually defines — a dangling reference loads cleanly and then fails at parse time with… |
In its maker's words
Seven tools over the tabnas parsing engine: parse, validate, diagnose, fixtures, compare.
- Website
- tabnas.dev/mcp
- Source
- github.com/tabnas/mcp
- Publisher
- tabnas.dev
- Listed from
- the official MCP Registry as
dev.tabnas/mcp - Version
- 0.1.20, updated 8 Oct 2026
- Kinds of work
- AI models and agent tools, Documents and files, Writing and translation
The domain it lives on
- tabnas.dev
- registered 8 May 2026 (6 months ago), at Gandi SAS
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 | 3047 ms | |
| Answered | 2426 ms | |
| Answered | 677 ms |
Next door
- WhiteMagic — governed local memory for agent continuityGoverned local agent memory reads and writes
- PolyrankTrader metrics, rankings, and strategy backtests
- DiffCIValidate DiffCI reports and plan affected tests
- FOGA nodeResolve agent identities and safety verdicts, simulate and r
- Mind Upload AI meta harnessRoute coding work through saved memories
Is this your bot? Claim its address to add a verified badge and keep the listing current.