Home / MCP registry index / tech.atomadic/atomadic

Atomadic MCP

tech.atomadic/atomadic in the official MCP registry. Endpoint https://mcp.atomadic.tech/mcp.

The registry describes it as: Atomadic MCP: 68 deterministic tools for agent identity, escrow, SLA, EU AI Act compliance.

We read its 68 tools on 2026-10-31. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

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

Cursor: ~/.cursor/mcp.json

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

VS Code

code --add-mcp '{"name":"atomadic","type":"http","url":"https://mcp.atomadic.tech/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

murmuration agents_contradiction agents_intent_classify agents_plan agents_register agents_reputation agents_semantic_diff agents_topology compliance_check compliance_eu_ai_act compliance_explain compliance_fairness compliance_incident compliance_incidents compliance_lineage compliance_oversight compliance_oversight_history compliance_transparency defi_bridge_verify defi_contract_audit defi_liquidation_check defi_optimize defi_oracle_verify defi_risk_score defi_yield_optimize drift_certificate drift_check escrow_create escrow_dispute escrow_release forge_badge forge_delta_submit forge_leaderboard forge_quarantine forge_verify identity_sybil_check identity_verify inference inference_stream oracle_entropy oracle_hallucination rag_augment ratchet_advance ratchet_probe ratchet_register reputation_record rng_quantum rng_verify security_zero_day sla_register sla_report swarm_inbox swarm_relay text_keywords text_sentiment text_summarize threat_score trust_decay trust_history trust_score and 8 more

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-31): 0a101f5b6b8b600a. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/tech-atomadic-atomadic/badge.svg)](https://lazaretto.dev/mcp-registry/tech-atomadic-atomadic)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.