Publisher · GitHub account
MCP servers published by atomadictech
2 servers in the official MCP Registry are published under the namespace io.github.atomadictech/ and have a page in this directory: 2 remote, reached by URL, and 1 run locally from a package (1 offer both). First published 2026-04-07; latest update 2026-05-11.
What this publisher publishes
Names under io.github.atomadictech/ can only be published by someone who signs in to the MCP Registry as the GitHub user atomadictech, or as a member of the GitHub organisation of that name. The name shows which GitHub account published the entry; it does not show that the account belongs to the company whose product a server works with.
- Namespace
io.github.atomadictech- Servers with a page
- 2
- Categories
- developer (1), finance (1)
- Transports
- Streamable HTTP (2), stdio (local process) (1)
- Package registries
- PyPI (1)
- Remote servers declaring a header
- 0 of 2
- Packages declaring environment variables
- 0 of 1
- Websites stated
- aaaa-nexus.atomadictech.workers.dev, forge.atomadic.tech
- First published
- 2026-04-07
- Latest update
- 2026-05-11
Source repositories
The 2 repositories these servers state, with how many servers name each.
| Repository | Servers |
|---|---|
| github.com/atomadictech/aaaa-nexus | 1 |
| github.com/atomadictech/atomadic-forge | 1 |
All 2 servers, A to Z
| Server | Runs |
|---|---|
| aaaa-nexus — Formally Verified AI Safety APIsFormally verified AI safety APIs. Pay-per-call via USDC (x402). 75+ endpoints, no signup. | Remote · HTTP |
| Atomadic ForgeArchitecture compiler for AI code. 11 tools, 92 actions, 872 Lean4 proofs, 100/100 self-cert. | Remote & Local · HTTP, stdio |
Grouped by registry namespace, as the MCP Registry states it. A page here is not an endorsement and nobody pays to be listed: editorial policy · Before you connect a server