Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Router defaults, PSTI/CRA compliance checks, and MAC lookup via the hosted ssid.ai MCP service.
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.
You 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": {
"routerbase": {
"command": "npx",
"args": [
"-y",
"@reneturcios/routerbase",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add routerbase -- npx -y @reneturcios/routerbase mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"routerbase": {
"command": "npx",
"args": [
"-y",
"@reneturcios/routerbase",
"mcp"
]
}
}
}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": {
"routerbase": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@reneturcios/routerbase",
"mcp"
]
}
}
}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.
These 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 6, 2026
The registry name was verified with the GitHub account CloudCorpRecords, which owns the repo
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.0) reached the registry 4 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Docker on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Opencu
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.
Independent local computer-use engine and MCP server for macOS, Windows, Linux and Android
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.
routerbase answers three kinds of questions about home routers: what a model's factory login defaults are (gateway, login host, username/password, credential type, reset steps, and the manufacturer source the record cites), whether a model complies with the UK PSTI and EU CRA rules against universal default passwords, and who made the network hardware behind a MAC address. One binary serves a command-line interface and a stdio MCP server.
The data lives in a hosted service. routerbase is a local stdio server that forwards each call as a JSON-RPC tools/call request to the ssid.ai MCP endpoint at https://ssid.ai/mcp/http; that wire shape is a documented reconstruction from the service's public description. Point it elsewhere with SSID_API_BASE (a host or a full endpoint URL).
Read tools are free with no key. Setting SSID_API_KEY raises the rate limits and is sent as a Bearer token when present. submit_correction is different: the upstream gates that write tool behind its Pro tier, so without SSID_API_KEY routerbase refuses with an explanation and sends nothing — a correction is never reported as submitted when it was not.
For lookup_mac, the address classification is worked out locally, for real: the address is parsed and normalised (colon, hyphen, dot, and bare-hex forms are accepted), the multicast and locally-administered bits of the first octet decide between multicast, randomized, and universal, and anything unparseable is invalid. Only the vendor/OUI part comes from the upstream call, and an invalid address is never sent upstream.
npx @reneturcios/routerbase lookup_mac 00:1A:2B:3C:4D:5E
Or run the container image:
docker run -i ghcr.io/cloudcorprecords/routerbase
The container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead.
routerbase get_router_defaults --slug <slug>
routerbase get_router_defaults --brand --model routerbase check_router_compliance --slug routerbase lookup_mac 00:1A:2B:3C:4D:5E routerbase submit_correction --slug --field gateway_ip \ --proposed-value 192.168.0.1 --source-url https://example.com/manual
routerbase --version
Successful commands print the result as JSON. Exit codes: 0 on success, 1 when a call fails (including an upstream error or the correction key gate), 2 for usage errors. get_router_defaults needs either --slug or both --brand and --model; anything less is an honest error, not a guess.
One bin serves both faces. The mcp subcommand starts a stdio MCP server:
npx -y @reneturcios/routerbase mcp
MCP client configuration:
{
"mcpServers": { "routerbase": { "command": "npx", "args": ["-y", "@reneturcios/routerbase", "mcp"], "env": { "SSID_API_KEY": "your key, optional for read tools" } } } }
| Tool | Input | What it returns |
|---|---|---|
get_router_defaults | slug, or brand + model | The manufacturer-cited factory login record for the model. |
check_router_compliance | slug (required) | The model's standing under UK PSTI / EU CRA universal-default-password rules. |
lookup_mac | mac (required) | Local classification (universal / randomized / multicast / invalid), the normalised address and OUI, plus the upstream vendor payload. |
submit_correction | slug, field, proposedValue, sourceUrl (all required) | Queues a cited correction for verification. Requires SSID_API_KEY (Pro tier). |
npm install
npm run build # tsc -> dist/ npm test # node test runner over test/*.test.ts, no network (fake fetch fixtures) npm run dev # run the CLI from source via tsx
MIT — see LICENSE.