mcpField
A
Atomadic starter MCP (50 tools)

Atomadic starter MCP (50 tools)

Remote
atomadic.techSecurity0Updated 2d ago

About Atomadic starter MCP (50 tools)

Atomadic starter MCP is a hosted HTTP server offering APIs for AI safety and compliance. It provides tools for identity, authorization, threat scoring, and related tasks, with a curated 50-tool entry point and no-signup access to selected calls.

Key features

  1. 01Identity verification
  2. 02Action authorization
  3. 03Threat scoring
  4. 04Lineage recording
  5. 05Polyglot code generation
  6. 06Pay-per-call access

Use cases

  1. 01Verify an identity in an AI workflow
  2. 02Check risk before authorizing an action
  3. 03Record lineage for a process

MCP support

Exposes safety and compliance APIs as tools to MCP clients over HTTP. The curated endpoint offers 50 tools; the wider catalog has 68, and selected calls work without a key.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://mcp.atomadic.tech/mcp/public
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

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

Want fewer tools? Use the starter door

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 30-second proof (no key, no account)

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":{}}}'

# 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

On missing links

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

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.