tabnas

Name: tabnas
Author: dev.tabnas

MCP serverMCP

Seven tools over the tabnas parsing engine: parse, validate, diagnose, fixtures, compare.

by dev.tabnasrepository ↗homepage ↗v0.1.20MIT

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"tabnas-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability109/109 checks ok

when	check	result	http	latency	detail
4 h ago	mcp initialize	ok	200	16 ms	server tabnas 0.1.20 · protocol 2025-06-18 · 7 tools
11 h ago	mcp initialize	ok	200	15 ms	server tabnas 0.1.20 · protocol 2025-06-18 · 7 tools
17 h ago	mcp initialize	ok	200	59 ms	server tabnas 0.1.20 · protocol 2025-06-18 · 7 tools
23 h ago	mcp initialize	ok	200	15 ms	server tabnas 0.1.20 · protocol 2025-06-18 · 7 tools
29 h ago	mcp initialize	ok	200	32 ms	server tabnas 0.1.20 · protocol 2025-06-18 · 7 tools
2 d ago	mcp initialize	ok	200	40 ms	server tabnas 0.1.20 · protocol 2025-06-18 · 7 tools
2 d ago	mcp initialize	ok	200	12 ms	server tabnas 0.1.19 · protocol 2025-06-18 · 7 tools
2 d ago	mcp initialize	ok	200	18 ms	server tabnas 0.1.19 · protocol 2025-06-18 · 7 tools
2 d ago	mcp initialize	ok	200	54 ms	server tabnas 0.1.19 · protocol 2025-06-18 · 7 tools
3 d ago	mcp initialize	ok	200	33 ms	server tabnas 0.1.19 · protocol 2025-06-18 · 7 tools

Tools observed via MCP handshake

parse — Parse input with the tabnas engine. Returns {ok:true, tree} or, on parse failure, {ok:false, diagnostic} — the structured diagnostic described by resource tabna
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 ref
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-cod
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 esc
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?

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

tabnasparsermcpmodel-context-protocolcligrammaragent

kind Official MCP Registry

name Official MCP Registry

license npm registry

repoUrl Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

npm registry@tabnas/mcp

first seen 1 mo ago · fetched 20 h agoopen ↗

Official MCP Registrydev.tabnas/mcp

first seen 1 mo ago · fetched 11 h agoopen ↗

Field history (12 recent events)

11 h ago · declared · version → "0.1.20"
19 h ago · observed · packageFacts → {"name":"@tabnas/mcp","registry":"npm","publishedAt":"2026-10-08T09:18:23.817Z","latestVersion":"0.1.20","weeklyDownload
2 d ago · observed · packageFacts → {"name":"@tabnas/mcp","registry":"npm","publishedAt":"2026-10-07T06:30:56.158Z","latestVersion":"0.1.19","weeklyDownload
3 d ago · observed · packageFacts → {"name":"@tabnas/mcp","registry":"npm","publishedAt":"2026-10-06T11:51:42.446Z","latestVersion":"0.1.18","weeklyDownload
3 d ago · declared · version → "0.1.18"
6 d ago · observed · packageFacts → {"name":"@tabnas/mcp","registry":"npm","publishedAt":"2026-10-03T20:42:52.974Z","latestVersion":"0.1.17","weeklyDownload
14 d ago · declared · version → "0.1.16"
15 d ago · observed · packageFacts → {"name":"@tabnas/mcp","registry":"npm","publishedAt":"2026-09-23T22:43:18.991Z","latestVersion":"0.1.16","weeklyDownload
1 mo ago · declared · description → "Seven tools over the tabnas parsing engine: parse, validate, diagnose, fixtures, compare."
1 mo ago · declared · name → "tabnas"
1 mo ago · declared · summary → "Seven tools over the tabnas parsing engine: parse, validate, diagnose, fixtures, compare."
1 mo ago · declared · publisherName → "dev.tabnas"

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from