Atomadic Forge
Architecture compiler for AI code. 11 tools, 92 actions, 872 Lean4 proofs, 100/100 self-cert.
needs work
No valid MCP answer at last check (HTTP 404).
Rule R2g · what this means · Not tested in Copilot Studio.
| Registry name | io.github.atomadictech/atomadic-forge |
| Endpoint used for verdict | https://forge.atomadic.tech/mcp |
| Transports | streamable-http |
| Auth (Copilot Studio setting) | Unknown |
| Last endpoint check | 2026-10-23T22:39:43Z · HTTP 404 |
| GitHub | atomadictech/atomadic-forge |
| Website | https://forge.atomadic.tech |
| Version | 0.87.0 |
| Registry updated | 2026-05-11 |
Standards signals
| Official MCP Registry | Listed (active) MCP Registry |
| server.json schema | 2025-12-11 · currentserver.json schema changelog |
| Transport | Streamable HTTP (remote) Transports: Streamable HTTP |
| Answers MCP | No valid MCP answer at last check Lifecycle: initialization |
| Spec version spoken | Not observed Versioning |
| Supports 2026-07-28 | Not detected server/discover |
Observed from public registry data and a read-only, unauthenticated check on 2026-10-23. Not a certification: AAIF and the MCP project don't certify servers, and these lines are signals, not pass/fail. They don't change the Copilot Studio verdict. Own this server? modelcontextprotocol/conformance: test your own server.
Maintenance signals
- PyPI classifier on atomadic-forge: Development Status :: 7 - Inactive · checked 2026-10-23 · source
An estimate from public metadata, not a judgment of the project. Signals don't change the Copilot Studio verdict.
Track changes like this weekly. New Copilot-ready MCP servers, breakages and auth changes, in one short email.
Is this wrong or out of date? Email us. Data built 2026-10-24.