Skip to content
Atomadic logo

Atomadic MCP server

Which MCP servers are Atomadic's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-28

← Back to Atomadic

Whose server it is
  • Registry nametech.atomadic/atomadicverified in the MCP registry

The registry name sits under atomadic.tech. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-28
  • Stateanswerschecked 2026-10-28
  • Tools68
  • Server calls itselfatomadic-mcp
  • Server version0.6.9
  • Protocol version2024-11-05

On 2026-10-28 the server answered initialize and tools/list without a sign-in. First answer in 68 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: Screen AI systems for EU AI Act risk; Check compliance gates for GDPR and CCPA.
  • Checked on 5 of the 7 days it takes to judge reliability.

Once connected

  • For "Check compliance gates for GDPR and CCPA", the likely first call is compliance_check.
  • escrow_create change data without a sign-in: anyone with the address can call them.
  • Parameters are untyped or undescribed in 49 of 68 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 5, the first on 2026-10-28
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 5 so far
  • What an agent can do with it2 of 2 use cases
  • Use145 PyPI downloads a week
  • Answeredmeasuring5 of the 7 daily checks it takes to print a share
  • Median first answer66 ms
  • Space in an agent's context≈ 5,006 tokensthe definitions of all its tools (68), which an agent carries on every turn
  • Tool definitionsB · 88 of 100
  • Typed results0 of 68 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 49 of 68

What an agent can do with it

  • can do · Screen AI systems for EU AI Act risk
  • can do · Check compliance gates for GDPR and CCPA
  • not sure · Verify trust scores for tools before buying

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

  • Tools that change data, on a server that answers without a sign-in: escrow_create

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers68 tools · read 2026-10-28
  • murmuration

    START HERE (free, no key). Initialize your Atomadic control surface in one call: returns a verbose, step-by-step setup (SDK install, MCP connect, your unlocked tools), a RUNNABLE polyglot demo that proves the superpowers, recon links, and…

  • agents_contradiction

    [agents] Detect contradictions between two free-text agent outputs (natural-language claim drift). For structured key/value claims that must agree, use detect_contradiction instead.

  • agents_intent_classify

    [agents] Agent intent classification

  • agents_plan

    [agents] Autonomous agent goal planning

  • agents_register

    [agents] Register an agent

  • agents_reputation

    [agents] Agent reputation and trust score

  • agents_semantic_diff

    [agents] Semantic diff between two free-text agent outputs (meaning-level change, not text-level). Use forge_verify for build artifacts and drift_check for certified operational drift.

  • agents_topology

    [agents] Live swarm topology

  • compliance_check

    [security] GDPR/CCPA compliance gate

  • compliance_eu_ai_act

    [security] EU AI Act compliance certificate

  • compliance_explain

    [security] Explainability certificate (XPL-100-ExplainBound)

  • compliance_fairness

    [security] Fairness proof (FNS-100-FairnessBound)

  • compliance_incident

    [security] Report compliance incident

  • compliance_incidents

    [security] Incident registry

  • compliance_lineage

    [security] Data lineage (LIN-100-ChainIntegrity)

  • compliance_oversight

    [security] Log oversight event

  • compliance_oversight_history

    [security] Oversight history

  • compliance_transparency

    [security] Transparency report

  • defi_bridge_verify

    [defi] Bridge Proof (BRP-100-BridgeIntegrity)

  • defi_contract_audit

    [defi] Contract Verify (CVR-100-AuditBound)

  • defi_liquidation_check

    [defi] Liquid Shield (LQS-100-LiquidationBound)

  • defi_optimize

    [defi] LP parameter optimization (DFP-100-OptimalTick)

  • defi_oracle_verify

    [defi] Oracle guard (OGD-100-ManipulationBound)

  • defi_risk_score

    [defi] DeFi risk scoring (DFI-101-RiskScoreBound)

  • defi_yield_optimize

    [defi] Yield Oracle (YLD-100-YieldConvergence)

  • drift_certificate

    [trust] Drift certificate

  • drift_check

    [trust] DriftGuard check (DRG-100-DriftBound)

  • escrow_create

    [defi] Create agent-to-agent escrow

  • escrow_dispute

    [defi] Open escrow dispute

  • escrow_release

    [defi] Release escrowed funds

  • forge_badge

    [fuse] Model quality badge

  • forge_delta_submit

    [fuse] Submit a model delta

  • forge_leaderboard

    [fuse] Model leaderboard

  • forge_quarantine

    [fuse] Quarantined models

  • forge_verify

    [fuse] Verify a model submission

  • identity_sybil_check

    [identity] Sybil-resistance check

  • identity_verify

    [identity] Topological identity verification

  • inference

    [inference] Chat inference with hallucination guard

  • inference_stream

    [inference] Streaming inference with chain-of-thought

  • oracle_entropy

    [trust] Entropy epoch oracle

  • oracle_hallucination

    [trust] Hallucination oracle

  • rag_augment

    [inference] Trusted RAG augmentation

  • ratchet_advance

    [identity] RatchetGate — advance session

  • ratchet_probe

    [identity] RatchetGate — health probe

  • ratchet_register

    [identity] RatchetGate — register session

  • reputation_record

    [agents] Record agent interaction

  • rng_quantum

    [inference] Quantum random number with proof

  • rng_verify

    [inference] Verify current epoch random value

  • security_zero_day

    [security] Zero-day threat assessment

  • sla_register

    [agents] Register an SLA

  • sla_report

    [agents] Report SLA violation

  • swarm_inbox

    [agents] Poll swarm inbox

  • swarm_relay

    [agents] Relay message through swarm

  • text_keywords

    [inference] Keyword extraction

  • text_sentiment

    [inference] Sentiment analysis

  • text_summarize

    [inference] Text summarization

  • threat_score

    [security] Multi-vector threat score

  • trust_decay

    [trust] Current trust ceiling value

  • trust_history

    [trust] Trust score history

  • trust_score

    [trust] Bounded trust score

The first 60 of 68, as the server listed them.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "atomadic": {
      "type": "http",
      "url": "https://mcp.atomadic.tech/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http atomadic https://mcp.atomadic.tech/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://mcp.atomadic.tech/mcp as a custom connector in the settings.

Other servers listed as Atomadic's
  • io.github.atomadictech/atomadic-forgenot asked yetendpoint on the vendor's domain
  • tech.atomadic/atomadic-fusenot asked yetverified in the MCP registry
  • tech.atomadic/atomadic-nexusnot asked yetverified in the MCP registry

OpenAPI spec

149 paths, read 2026-10-28. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.