Atomadic starter MCP (50 tools)

Registre officiel Sécurité

50 starter MCP tools for AI compliance and trust: identity, escrow, SLA, EU AI Act.

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

Remote (streamable-http)
Claude Code
claude mcp add --transport http atomadic-starter-mcp-50-tools 'https://mcp.atomadic.tech/mcp/public'
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "atomadic-starter-mcp-50-tools": {
            "type": "http",
            "url": "https://mcp.atomadic.tech/mcp/public"
        }
    }
}

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. aaaa-nexus — public entry point
  2. Live endpoint
  3. The 30-second proof (no key, no account)
  4. How calls get paid
  5. Elsewhere
  6. On missing links
  7. Registry listing

aaaa-nexus — public entry point

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.

Live endpoint

https://aaaa-nexus.atomadictech.workers.dev/mcp

Streamable HTTP, MCP protocol revision 2025-11-25. 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.

The 30-second proof (no key, no account)

The full catalog lives at https://mcp.atomadic.tech (129 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":{}}}'

# 2. the proof: one function emitted into 12 languages from one source
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_<key> is the whole auth story.

How calls get paid

tools/call returns an invocation contract: an HTTPS URL, a method, and a price in micro-USDC. Pay it with either

  • x402 — complete payment per PAYMENT-REQUIRED on the 402 from the target route, or from /v1/payments/fee, sending an x402 PAYMENT-SIGNATURE header; or
  • X-API-Key — if you already hold a key.

No account is required for x402. Pay per call.

Elsewhere

  • https://atomadic.tech — main site, docs, pricing, proof page
  • https://aaaa-nexus.atomadictech.workers.dev — the server itself

Some 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.

Registry listing

Official MCP Registry entry: io.github.atomadictech/aaaa-nexus (latest 0.5.1), with repository pointing at this repo and the live remote above. 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.

Questions fréquentes

Qu'est-ce que Atomadic starter MCP (50 tools) ?

50 starter MCP tools for AI compliance and trust: identity, escrow, SLA, EU AI Act.

Comment installer Atomadic starter MCP (50 tools) ?

Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http atomadic-starter-mcp-50-tools 'https://mcp.atomadic.tech/mcp/public'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour Atomadic starter MCP (50 tools) ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

Atomadic starter MCP (50 tools) est-il open source ?

Son code est public sur GitHub, mais le dépôt ne déclare pas de licence standard.

Qui maintient Atomadic starter MCP (50 tools) ?

Il est publié par atomadictech. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.