Not reviewed
No score, grade or rank. This listing is facts from the official MCP registry and our own checks, and it stays out of the rankings until the panel reviews it.
Seven tools over the tabnas parsing engine: parse, validate, diagnose, fixtures, compare.
Facts
- MCP registry
dev.tabnas/mcp· 0.1.17- Endpoint
https://mcp.tabnas.dev/mcp- Packages
npm@tabnas/mcp stdio- Source
- github.com/tabnas/mcp
- Website
- tabnas.dev/mcp
- npm / week
- 174
- GitHub stars
- 0
- Registry entry
- updated 3 Oct 2026
From the official MCP registry, the package registries and our own checks. JSON · Markdown
Why it's listed
- It's published in the registry under tabnas.dev, a namespace the registry only gives to whoever proves they control that domain.
Being indexed says nothing about quality, and nobody can pay for it. Is this yours? Ask for a review.
Tools it lists 7 · about 1,410 tokens of context · checked 57 minutes ago
| Tool | What it does | Hint |
|---|---|---|
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… | |
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… | |
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… | |
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 /… | |
list_plugins | List every bundled tabnas plugin descriptor (tabnas.plugin.json of each fleet repo), sorted by name. Returns {plugins:[...]}. | |
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. | |
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:… |
What https://mcp.tabnas.dev/mcp answered to tools/list, asked without credentials. answered without the initialize handshake. The token figure is the size of the list as sent, divided by four; a model sees about that much before it calls anything. Full definitions, input schemas included, are in the listing's JSON under mcpTools.
How its tools read to an agent 0 errors · 13 warnings · 1 note
- warnTC11test_grammar1 parameter without a description: options
- warnTC13compare_grammarsa (object with no properties), b (object with no properties), options (object with no properties)
- warnTC13explain_parse_errorgrammar (object with no properties)
- warnTC13parsegrammar (object with no properties), options (object with no properties)
- warnTC13test_grammargrammar (object with no properties)
- warnTC13validate_grammargrammar (object with no properties)
- warnTC16compare_grammarsno readOnlyHint or destructiveHint
- warnTC16describe_pluginno readOnlyHint or destructiveHint
- warnTC16explain_parse_errorno readOnlyHint or destructiveHint
- warnTC16list_pluginsno readOnlyHint or destructiveHint
- warnTC16parseno readOnlyHint or destructiveHint
- warnTC16test_grammarno readOnlyHint or destructiveHint
- warnTC16validate_grammarno readOnlyHint or destructiveHint
- noteTC24server7 of 7 tools have no outputSchema
The checks from /check and anchor check, run each day on the list above: about 1,410 tokens of definitions. Not part of the score yet. Check your own server.