Other · Remote MCP server
tabnas
Seven tools over the tabnas parsing engine: parse, validate, diagnose, fixtures, compare.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
dev.tabnas/mcp- Version
- 0.1.17
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-10-03
- Updated
- 2026-10-03
- Publisher
- dev.tabnas
- Namespace
- Namespace verified by the MCP Registry via the domain tabnas.dev · how
- Website
- tabnas.dev/mcp
- Repository
- github.com/tabnas/mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.tabnas.dev/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- tabnas 0.1.17 · protocol 2025-06-18
- Tools discovered
- 7:
parse,validate_grammar,explain_parse_error,test_grammar,list_plugins,describe_plugin,compare_grammars - Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | @tabnas/mcp | 0.1.17 | stdio |
How to connect tabnas
tabnas is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.tabnas.dev/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: @tabnas/mcp version 0.1.17. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @tabnas/mcp@0.1.17.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@tabnas/mcp@0.1.17"
]
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| T32 Lsp MCP ServerTRACE32 CMM LSP via MCP - parse, diagnostics, completions, hover, symbols. | Local · stdio |
| TablaFocusMCPMCP server for tabla learning: glossary, taals, composition, practice coaching, certification prep. | Local · stdio |
| Tableaugen MCPGenerate Tableau workbooks (.twb /.twbx) from natural language and a CSV. | Local · stdio |
| TablePredictBuild validated football table and World Cup group prediction links with TablePredict. | Remote · HTTPLive check: ✓ handshake |
| TabTreeTurn conversations into mind maps and whiteboards - in your TabTree account, or local files. | Local · stdio |
| Tabula MCPBar-first MCP server for Tabula chart authoring, PNG rendering, and editor handoff. | Remote · HTTPLive check: ✗ no handshake |
| Tabular RecipeTurn any recipe into a compact process table - every ingredient and step at a glance. | Remote · HTTPLive check: ✓ handshake |
| Tachibot MCPMulti-model AI orchestration with 31 tools, YAML workflows, and 5 token-optimized profiles. | Local · stdio |