Skip to content

tabnas MCP server

dev.tabnas/mcptabnas.devstreamable-httpv0.1.20Scanned

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

7 tools: 2 change things and 5 only read.

Tools: 0 delete, 0 irreversible, 2 write, 5 read.
  • Reads private data · 1
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the tabnas MCP server can do

The tabnas MCP server is published by tabnas.dev, a domain the MCP Registry verified. It has 7 tools. It can create or change data (2 tools: parse and test_grammar), but cannot delete data. 5 tools only read.

1 tool reads private data (list_plugins).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 11, 2026, version 0.1.20.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Changes things 2Claude Code: ask
  • parseParse input with the tabnas engine.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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, which defines no rules and produces an undefined tree for every input.
  • test_grammarRun 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 exp…No findings

    Why it is in this group

    • The description's first verb is "run": a word for a change.
    Description, as the server wrote it
    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 than 10000 rows.
Only reads 5Show 5 read-only tools
  • compare_grammarsGrammar 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?No findings

    Why it is in this group

    • The name "compare_grammars" says "compare": a word for reading.
    Description, as the server wrote it
    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}. confidence:'low' with a stated reason is a successful run, not a failure — language inclusion is undecidable in general, so anything outside the decidable subset is reported not-proven rather than incompatible. Supply `corpus` (real inputs) for the tier that measures what your documents actually do.
  • describe_pluginThe full descriptor for one plugin, by package name ('@tabnas/csv') or bare fleet name ('csv').No findings

    Why it is in this group

    • The name "describe_plugin" says "describe": a word for reading.
    Description, as the server wrote it
    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_errorParse input and explain the failure.No findings

    Why it is in this group

    • The name "explain_parse_error" says "explain": a word for reading.
    Description, as the server wrote it
    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 know (e.g. a plugin-declared code).
  • list_pluginsList every bundled tabnas plugin descriptor (tabnas.plugin.json of each fleet repo), sorted by name.Reads private dataNo findings

    Why it is in this group

    • The name "list_plugins" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "repo": it reads repositories.
    Description, as the server wrote it
    List every bundled tabnas plugin descriptor (tabnas.plugin.json of each fleet repo), sorted by name. Returns {plugins:[...]}.
  • validate_grammarValidate a serialized GrammarSpec.No findings

    Why it is in this group

    • The name "validate_grammar" says "validate": a word for reading.
    Description, as the server wrote it
    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 `unknown_rule`. Returns {ok:true, v} (v = declared builtin config-schema version, absent means 1) or {ok:false, errors:[{path,message}]}. Security: a grammar carrying a `ref` key, or any function reference that is not a $-suffixed engine builtin, is rejected — validating a grammar never runs supplied code.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:52 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.tabnas.dev/mcp: tools/list returned 7 tools to an anonymous client, including parse (write), test_grammar (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.1.20. Values in angle brackets are yours to fill in.

claude mcp add --transport http tabnas https://mcp.tabnas.dev/mcp
claude mcp add --transport http tabnas https://mcp.tabnas.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__tabnas__validate_grammar",
      "mcp__tabnas__explain_parse_error",
      "mcp__tabnas__list_plugins",
      "mcp__tabnas__describe_plugin",
      "mcp__tabnas__compare_grammars"
    ],
    "ask": [
      "mcp__tabnas__parse",
      "mcp__tabnas__test_grammar"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as tabnas. Review it before you use it.

Capability tags behind 1 rule
  • mcp__tabnas__list_plugins private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/dev.tabnas/mcp/verify?hash=836cb5d31981243473439739fefd0ff67d10ab524d23bd6f0d2045be4a37b6c9" | jq -e '.changed == false'

Pinned hash 836cb5d31981, from Nov 11, 2026, 09:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/dev.tabnas/mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for dev.tabnas/mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/dev.tabnas/mcp.svg)](https://radar.anlyon.com/servers/dev.tabnas/mcp)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:12 UTC.

tabnas MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the tabnas MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the tabnas MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the tabnas MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the tabnas MCP server have?

7 tools: 2 write, 5 read. parse, test_grammar, validate_grammar, explain_parse_error, list_plugins, describe_plugin and compare_grammars.

Does the tabnas MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the tabnas MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the tabnas MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.