topiclint
Validates MQTT topic strings against the Sparkplug B topic grammar and reviews sets of Unified Namespace topic paths for naming consistency; operates locally without connecting to a broker.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
topiclint
topiclint checks MQTT topic strings before they reach a broker or a namespace design review. It lints individual topics against the Sparkplug B topic grammar (Sparkplug 3.0), and it reviews a whole set of Unified Namespace (UNS) topic paths for naming consistency — the kind of drift (mixed casing, uneven depth, near-duplicate siblings) that makes a namespace hard to browse, query, and hand over. One binary serves a command-line interface and a stdio MCP server.
Everything is local and offline. There is no broker connection, no network access, no API key, and no account. The linter validates grammar only: it does not decode payloads or check that a device exists. The naming check judges consistency only: it does not know your plant and will not design a namespace for you.
Install
npx @reneturcios/topiclint lint spBv1.0/Plant1/NBIRTH/Edge1Or run the container image:
docker run -i ghcr.io/cloudcorprecords/topiclintThe container defaults to the MCP server (see below); pass CLI arguments to use it as a CLI instead.
Related MCP server: dxpert UNS Tools: Sparkplug B & Unified Namespace Linter for IIoT
CLI
topiclint lint spBv1.0/Plant1/NBIRTH/Edge1 spBv1.0/Plant1/DDATA/Edge1/Dev1
topiclint check enterprise/site1/line1 enterprise/site1/line2
topiclint --versionEach topic or path is one argument; a single argument may also be
a newline-delimited list. Both commands print a JSON report. A
report full of findings is still a successful run — findings are
the output, not an error. Exit codes: 0 on success, 1 on a
runtime error, 2 for usage errors.
What the Sparkplug lint checks
For every topic: the spBv1.0 namespace level; the message type
(one of NBIRTH, NDEATH, DBIRTH, DDEATH, NDATA, DDATA,
NCMD, DCMD, plus STATE); the level count (node messages and
STATE carry exactly four levels, device messages exactly five);
the legacy Sparkplug 2.2 STATE form (STATE/<host_id> with no
namespace), reported as its own failure; publish-side MQTT
wildcards (+ / #); empty levels; and identifier characters in
the group, node, and device levels — whitespace fails, and
characters outside [A-Za-z0-9_-] warn, because both break
downstream consumers that split, quote, or map topics.
Each result carries the parsed topic parts (namespace, group id,
message type, edge node id, device id) plus ordered findings with
levels fail / warn / pass / info.
What the UNS check looks for
Across the whole set: duplicate paths, empty levels, whitespace in
segments, and stray MQTT wildcards all fail. Siblings under the
same parent whose names differ only by case fail as a
case-collision — they read as one node but are two. Inconsistent
hierarchy depth and mixed casing styles (lower, upper,
snake_case, kebab-case, PascalCase, camelCase) warn. The
report opens with a one-line summary, then the per-issue findings.
MCP server
One bin serves both faces. The mcp subcommand starts a stdio MCP
server:
npx -y @reneturcios/topiclint mcpMCP client configuration:
{
"mcpServers": {
"topiclint": {
"command": "npx",
"args": ["-y", "@reneturcios/topiclint", "mcp"]
}
}
}Tools
Both tools take a single topics argument: a single string, a
newline-delimited string, or an array of topic strings.
Tool | Input | What it returns |
|
| Per-topic parsed parts plus ordered findings, with pass/fail counts and a summary. |
|
| A summary line plus per-issue findings for the whole path set. |
Development
npm install
npm run build # tsc -> dist/
npm test # node test runner over test/*.test.ts, no network
npm run dev # run the CLI from source via tsxLicense
MIT — see LICENSE.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Independent static checks for supported tag and alarm CSV import formats; no HMI or PLC access.
Validate JSON-LD structured data against the Schema.org vocabulary. Free; never fetches URLs.
Audit public webpages and supplied markup for HTML, CSS, SEO, JSON-LD, and link issues.
Validate JSON, YAML, XML and CSV with exact line/column errors and silent-corruption warnings.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables users to validate MCP servers, skills, extensions, and packages for schema, security, functional, and semantic quality directly from their MCP client.MIT
- AlicenseAqualityBmaintenanceFree Industry 4.0 / IIoT tools, no API key or account: lint MQTT Sparkplug B topics, check a Unified Namespace (UNS) for naming and hierarchy problems, and run an industrial AI-readiness diagnostic for manufacturing digital transformation and smart-factory projects. Works in Claude Code, Codex and any MCP client.3130 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables local glTF/GLB asset validation against versioned profiles via MCP, returning actionable reports.MIT
- AlicenseNot gradedqualityBmaintenanceProvides MCP tools for local code validation with execution evidence, enabling users to run planned checks on projects and receive JSON results that distinguish passing, failing, and incomplete outcomes.462 npmMIT