Is the Tabnas MCP server down?

mcp-registry/dev.tabnas/mcp · v0.1.20

Also listed as glama/tabnas/tabnas/mcp

As of 2026-10-26 18:04 UTC, the Tabnas MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

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

Point your MCP client at this streamable-http endpoint: https://mcp.tabnas.dev/mcp

Agent-readiness: B (81/100)

What to fix (3)

Auto-fix: 5 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fdev.tabnas%2Fmcp/fixes

{
  "name": "compare_grammars",
  "description": "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 inco",
  "inputSchema": {
    "type": "object",
    "required": [
      "a",
      "b"
    ],
    "properties": {
      "a": {
        "type": "object",
        "description": "Baseline grammar: the serialized GrammarSpec already deployed."
      },
      "b": {
        "type": "object",
        "description": "Candidate grammar: the serialized GrammarSpec proposed to replace it."
      },
      "depth": {
        "type": "integer",
        "maximum": 5,
        "minimum": 0,
        "description": "Derivation depth for generated inputs (default 3)."
      },
      "corpus": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "Inputs to replay through both grammars, comparing acceptance and tree shape."
      },
      "options": {
        "type": "object",
        "description": "TabnasOptions applied to both instances."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "describe_plugin",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "name"
    ],
    "properties": {
      "name": {
        "type": "string",
        "description": "Plugin name."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "explain_parse_error",
  "description": "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).",
  "inputSchema": {
    "type": "object",
    "required": [
      "input"
    ],
    "properties": {
      "input": {
        "type": "string",
        "description": "Source text to parse."
      },
      "grammar": {
        "type": "object",
        "description": "Serialized GrammarSpec (pure JSON, no functions). Schema: resource tabnas://schema/grammar. Grammars are validated before use; a `ref` key or a non-builtin function reference is rejected."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/dev.tabnas/mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/dev.tabnas/mcp"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~1,513 tokens).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 100.00% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• compare_grammars ~333 tokens
• test_grammar ~293 tokens
• parse ~262 tokens
• validate_grammar ~244 tokens
• explain_parse_error ~215 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.tabnas%2Fmcp.svg)](https://glimind.com/server/mcp-registry%2Fdev.tabnas%2Fmcp?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fdev.tabnas%2Fmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.tabnas%2Fmcp.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.tabnas%2Fmcp.svg
   :target: https://glimind.com/server/mcp-registry%2Fdev.tabnas%2Fmcp?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:15569891bdca40a9…, first seen 2026-10-17, included at leaf 11976 of 74,602. Version history · verify what your client received.

Tools (7)

• compare_grammars
• describe_plugin
• explain_parse_error
• list_plugins
• parse
• test_grammar
• validate_grammar

Compare: most reliable data servers · most reliable other servers · most reliable code servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Tabnas MCP server down right now?

As of 2026-10-26 18:04 UTC, the Tabnas MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Tabnas MCP server provide?

Tabnas MCP server advertises 7 tools, including compare_grammars, describe_plugin, explain_parse_error, list_plugins, parse.

How do I install Tabnas MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.tabnas.dev/mcp

Is the Tabnas MCP server safe to connect to an AI agent?

Glimind scanned all 7 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Tabnas MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.