Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
50 starter MCP tools for AI compliance and trust: identity, escrow, SLA, EU AI Act.
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 …”.
Works in Claude on the web, desktop and mobile:
https://mcp.atomadic.tech/mcp/publicRun this in your terminal
claude mcp add --transport http aaaa-nexus https://mcp.atomadic.tech/mcp/publicPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"aaaa-nexus": {
"url": "https://mcp.atomadic.tech/mcp/public"
}
}
}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": {
"aaaa-nexus": {
"type": "http",
"url": "https://mcp.atomadic.tech/mcp/public"
}
}
}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.
ChatGPT connects only to servers on the internet:
https://mcp.atomadic.tech/mcp/publicMenu names can differ slightly by plan and over time.
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.
We have not read this server’s tool list yet; we check endpoints in rotation.
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 atomadictech, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
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 in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (0.5.2) reached the registry 10 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, dotnet-mcp
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.
MCP server for .NET symbols, XAML, source generators, and restricted workspace edit
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.
This repo is the public front page for the AAAA-Nexus hosted MCP server: formally verified AI safety and compliance APIs, reachable over HTTP with no signup.
The server is live. The source is not public. That is the whole point of this repo: if you landed here from an MCP directory and every other Atomadic link was a dead end, this is the one that resolves.
https://aaaa-nexus.atomadictech.workers.dev/mcp
Streamable HTTP. The server negotiates down to whatever revision the client asks for (a 2025-06-18 probe is answered with 2024-11-05). Verified live:
curl -s -X POST https://aaaa-nexus.atomadictech.workers.dev/mcp \
-H 'content-type: application/json' \ -H 'accept: application/json, text/event-stream' \ -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"probe","version":"1"}}}'
Then tools/list and tools/call. 44 tools are exposed. A sample:
rng_quantum, threat_score, hallucination_oracle, identity_verify, ratchet_register, authorize_action, spending_authorize, lineage_record.
The catalog also mirrors at https://aaaa-nexus.atomadictech.workers.dev/.well-known/mcp.json.
https://mcp.atomadic.tech/mcp/public exposes a curated 50 of the 68 tools on the main endpoint. Same deterministic calls, same auth rules, smaller surface. GET it for a self-describing index. Start there if 68 is a lot to read.
The full catalog lives at https://mcp.atomadic.tech (68 tools; a key unlocks your plan's set). Three tools need no key at all. Run this pair and you have seen the thing work:
# 1. orientation: install, connect, what you are entitled to
curl -s -X POST https://mcp.atomadic.tech \ -H 'content-type: application/json' \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"murmuration","arguments":{}}}'
curl -s -X POST https://mcp.atomadic.tech \ -H 'content-type: application/json' \ -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"render_polyglot_all_pure","arguments":{"atom_name":"compute_sum_pure"}}}'
That second call returns ok: true with Python, JavaScript, TypeScript, Rust, Go, C#, Kotlin, Swift, Ruby, Lua, Elixir and Haskell, all from a single node IR.
The baked demo atoms are compute_sum_pure, keep_positive_pure, double_each_pure, count_words_pure. Call the polyglot tools with an empty argument and they answer, honestly, novel_input_not_baked — that is a boundary, not a bug: arbitrary input is what the SDK is for.
Keys are sold at https://atomadic.tech/store. A key is emailed after checkout, and X-API-Key or Authorization: Bearer ato_ is the whole auth story.
tools/call returns an invocation contract: an HTTPS URL, a method, and a price in micro-USDC. Pay it with either
PAYMENT-REQUIRED on the 402 from the target route, or from /v1/payments/fee, sending an x402 PAYMENT-SIGNATURE header; orNo account is required for x402. Pay per call.
https://atomadic.tech — main site, docs, pricing, proof pagehttps://aaaa-nexus.atomadictech.workers.dev — the server itselfSome older pages and package metadata point at GitHub repositories that are private. Those links 404 for anyone outside the account. Nothing was deleted; the repositories are closed. If you followed a broken link to get here, this README is the correction: use the live endpoint above rather than the dead source link.
Official MCP Registry entry: io.github.atomadictech/aaaa-nexus (latest 0.5.2, remote https://mcp.atomadic.tech/mcp/public), with repository pointing at this repo. The older io.github.atomadictech/atomadic-forge entries are marked deprecated: that endpoint returns 404 and its package is retired.
https://registry.modelcontextprotocol.io/v0/servers?search=atomadic
Built by Thomas Ralph Colvin IV and Jessica Mary Colvin.