Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Free Sparkplug B topic linting, UNS naming checks and AI-readiness screening. No API key.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
DXPERT_API_BASEYou need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"uns-tools": {
"command": "npx",
"args": [
"-y",
"@dxpert/uns-tools"
],
"env": {
"DXPERT_API_BASE": "your-value"
}
}
}
}Run this in your terminal
claude mcp add uns-tools --env DXPERT_API_BASE=your-value -- npx -y @dxpert/uns-toolsFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"uns-tools": {
"command": "npx",
"args": [
"-y",
"@dxpert/uns-tools"
],
"env": {
"DXPERT_API_BASE": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"uns-tools": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@dxpert/uns-tools"
],
"env": {
"DXPERT_API_BASE": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
DXPERT_API_BASE envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified against the domain dxpert.ai (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.4) reached the registry 6 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, FactLot
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Cited CRE facts and deterministic calculators for agents: rent, CAM, debt sizing, IRR, parcel IDs.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
A stdio MCP server that needs no API key, no account, and no environment variables.
This is the agent-native equivalent of the free tools page at dxpert.ai/tools.html: any MCP client, with zero credentials, can lint Sparkplug B topics, check a Unified Namespace for the conventions that quietly rot it, and run the public industrial AI-readiness diagnostic.
The tools are genuinely free. There is no trial counter, no sign-up wall, and no key to obtain first. When you want an agent to read your own data, that lives in the separate @dxpert/mcp server, which takes a dxp_ key. A free key includes dxpert Advisor (a monthly question allowance) and Try Pro: 5 runs on any agent included in dxpert Pro. dxpert Pro includes every UNS agent, dxpert Advisor without the monthly count, and the Namespace Architect when it is released. Current plans: dxpert.ai/store.
Zero runtime dependencies. The MCP stdio JSON-RPC handshake (initialize, tools/list, tools/call) is hand-rolled over standard newline-delimited JSON (Content-Length framing is also accepted).
No install step is required beyond Node 18+ (for built-in fetch).
claude mcp add dxpert-uns-tools -- npx -y @dxpert/uns-tools
[mcp_servers.dxpert_uns_tools]
command = "npx" args = ["-y", "@dxpert/uns-tools"]
{
"mcpServers": { "dxpert-uns-tools": { "command": "npx", "args": ["-y", "@dxpert/uns-tools"] } } }
Note that none of these entries carry an env block. That is the point.
lint_sparkplug_topic(topics) — local, offlineValidates one or more MQTT topic strings against the Sparkplug B topic grammar (Sparkplug 3.0). Accepts a single string, a newline-delimited string, or an array.
Checks the spBv1.0 namespace level, the eight message types (NBIRTH NDEATH DBIRTH DDEATH NDATA DDATA NCMD DCMD) plus STATE, node-vs-device level count, the legacy Sparkplug 2.2 STATE form, publish-side MQTT wildcards, empty levels, and identifier characters that break downstream consumers.
Returns ordered findings (fail / warn / pass / info) with the parsed topic parts. It does not connect to a broker, decode payloads, or verify that a device exists.
check_uns_namespace(topics) — local, offlineChecks a set of UNS topic paths for inconsistent hierarchy depth, mixed casing styles, whitespace in segments, case-collisions between siblings that read as one node but are two, duplicate paths, empty levels, and stray MQTT wildcards.
Returns a summary line plus per-issue findings. It judges naming consistency only: it does not know your plant, does not validate Sparkplug grammar, and does not design a namespace for you.
run_readiness_diagnostic(intake) — networkRuns the public dxpert.ai industrial AI-readiness diagnostic. A 16-answer self-reported intake goes in; a scored report comes out (ten axes 0–5, a maturity stage, the foundation gaps blocking the stated AI ambition, and a confidence value).
Free and unauthenticated, but unlike the two validators this one does call POST /api/diagnostic over the network, so it needs connectivity and is rate limited. Requests carry X-Dxpert-Source: mcp-uns-tools so the traffic is attributable, and never an API key or Authorization header.
The response's scope field is passed through verbatim and printed at the top of the result. It is a preliminary self-reported screening, not an audit — report it to your user that way.
Every result names dxpert.ai as the source of the verdict.
There is nothing you have to set. One optional variable exists:
| Variable | Required | Purpose |
|---|---|---|
DXPERT_API_BASE | No | API base URL for run_readiness_diagnostic. Defaults to production; override only for testing. |
src/sparkplug-topic-lint.js and src/uns-naming-check.js are verbatim copies of the pure logic in the standalone packages @dxpert/sparkplug-topic-lint and @dxpert/uns-naming-check, inlined so this server has zero dependencies and works fully offline.
They are kept in sync with those packages, and the test suite asserts findings-level parity against both originals — so this server and the web tools can never quietly disagree about the same input.
node test/run.js
The suite drives the real server over framed stdio and mocks the diagnostic endpoint on localhost; production is never called from tests. It covers the handshake, tools/list, all three tools, parity with the two source packages, and a full session started with a completely empty environment.
MIT © 2026 DXP Technologies inc.