# Atomadic MCP (remote · mcp.atomadic.tech)

Atomadic MCP: 68 deterministic tools for agent identity, escrow, SLA, EU AI Act compliance.

- Trust score: 63/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

> **Recent critical change**: Authorization (2026-10-27). See the changelog below before you install this server.

## Components

- remote · `mcp.atomadic.tech`: 63/100 (this document), [markdown](https://verifymcp.io/servers/tech-atomadic-atomadic/mcp.md), [page](https://verifymcp.io/servers/tech-atomadic-atomadic/mcp)

## Channel facts

- Endpoint: `https://mcp.atomadic.tech/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.6.9`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (escrow_dispute).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 49/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 3129 tokens (~46/item across 68 items; 68 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 61/100
  - Stability check failed: schema churn in the 19 days we've observed: 1 tool removals, 1 breaking changes, 0 auth/transport breaks, 1 additions.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 13% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 68 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 69 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### How do I install the Atomadic MCP server?

Atomadic MCP is a hosted endpoint at https://mcp.atomadic.tech/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

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

### VS Code

```json
{
  "servers": {
    "tech-atomadic-atomadic": {
      "type": "http",
      "url": "https://mcp.atomadic.tech/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.tech-atomadic-atomadic]
url = "https://mcp.atomadic.tech/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tech-atomadic-atomadic": {
      "type": "remote",
      "url": "https://mcp.atomadic.tech/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tech-atomadic-atomadic --url 'https://mcp.atomadic.tech/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  tech-atomadic-atomadic:
    url: "https://mcp.atomadic.tech/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "tech-atomadic-atomadic": {
      "Transport": "http",
      "Url": "https://mcp.atomadic.tech/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add tech-atomadic-atomadic -t streamable-http -u 'https://mcp.atomadic.tech/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 58 to 61.

### 2026-11-04 (score 62, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “compliance_check” rewrote its description, which is the text the model reads
- [functional regression] “compliance_check” dropped the required parameter “data_type”
- [functional regression] “compliance_check” dropped the required parameter “jurisdiction”
- [functional regression] “compliance_check” dropped the required parameter “operation”
- [functional] Schema quality: poor → fair
- [functional] Server version: 124 → 126
- [cosmetic] “compliance_check” added an optional parameter “chain_depth”
- [cosmetic] “compliance_check” added an optional parameter “description”
- [cosmetic] “compliance_check” added an optional parameter “kl_divergence”

### 2026-11-03 (score 62, +1)

- [functional] Server version: 0.6.9 → 124

### 2026-11-01 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 45 to 48.

### 2026-10-30 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 38 to 42.

### 2026-10-28 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 32 to 35.

### 2026-10-27 (score 58, 0)

- [critical regression] Authorization: unverified → fail
- [security regression] Stability: 0.30 → fail
- [security regression] A breaking change shipped without a version bump: still 0.6.9
- [security regression] Tool “forge_badge_{model}” was removed
- [security] Tool “agents_contradiction” rewrote its description, which is the text the model reads
- [security] Tool “agents_semantic_diff” rewrote its description, which is the text the model reads
- [security] Tool “detect_contradiction” rewrote its description, which is the text the model reads
- [security] Tool “escrow_dispute” is now declared destructive
- [security] Tool “escrow_release” is now declared destructive
- [security] Tool “forge_quarantine” is now declared destructive
- [functional] New tool “forge_badge”
- [cosmetic] Tool “agents_contradiction” changed its title: Agents Contradiction
- [cosmetic] Tool “agents_intent_classify” changed its title: Agents Intent Classify
- [cosmetic] Tool “agents_plan” changed its title: Agents Plan
- [cosmetic] Tool “agents_register” changed its title: Agents Register
- [cosmetic] Tool “agents_reputation” changed its title: Agents Reputation
- [cosmetic] Tool “agents_semantic_diff” changed its title: Agents Semantic Diff
- [cosmetic] Tool “agents_topology” changed its title: Agents Topology
- [cosmetic] Tool “audit_work_claim” changed its title: Audit Work Claim
- [cosmetic] Tool “compliance_check” changed its title: Compliance Check
- [cosmetic] Tool “compliance_eu_ai_act” changed its title: Compliance Eu Ai Act
- [cosmetic] Tool “compliance_explain” changed its title: Compliance Explain
- [cosmetic] Tool “compliance_fairness” changed its title: Compliance Fairness
- [cosmetic] Tool “compliance_incident” changed its title: Compliance Incident
- [cosmetic] Tool “compliance_incidents” changed its title: Compliance Incidents
- [cosmetic] Tool “compliance_lineage” changed its title: Compliance Lineage
- [cosmetic] Tool “compliance_oversight” changed its title: Compliance Oversight
- [cosmetic] Tool “compliance_oversight_history” changed its title: Compliance Oversight History
- [cosmetic] Tool “compliance_transparency” changed its title: Compliance Transparency
- [cosmetic] Tool “defi_bridge_verify” changed its title: Defi Bridge Verify
- [cosmetic] Tool “defi_contract_audit” changed its title: Defi Contract Audit
- [cosmetic] Tool “defi_liquidation_check” changed its title: Defi Liquidation Check
- [cosmetic] Tool “defi_optimize” changed its title: Defi Optimize
- [cosmetic] Tool “defi_oracle_verify” changed its title: Defi Oracle Verify
- [cosmetic] Tool “defi_risk_score” changed its title: Defi Risk Score
- [cosmetic] Tool “defi_yield_optimize” changed its title: Defi Yield Optimize
- [cosmetic] Tool “detect_contradiction” changed its title: Detect Contradiction
- [cosmetic] Tool “drift_certificate” changed its title: Drift Certificate
- [cosmetic] Tool “drift_check” changed its title: Drift Check
- [cosmetic] Tool “enforce_sla” changed its title: Enforce Sla
- [cosmetic] Tool “escrow_create” changed its title: Escrow Create
- [cosmetic] Tool “escrow_dispute” changed its title: Escrow Dispute
- [cosmetic] Tool “escrow_release” changed its title: Escrow Release
- [cosmetic] Tool “forge_delta_submit” changed its title: Forge Delta Submit
- [cosmetic] Tool “forge_leaderboard” changed its title: Forge Leaderboard
- [cosmetic] Tool “forge_quarantine” changed its title: Forge Quarantine
- [cosmetic] Tool “forge_verify” changed its title: Forge Verify
- [cosmetic] Tool “identity_sybil_check” changed its title: Identity Sybil Check
- [cosmetic] Tool “identity_verify” changed its title: Identity Verify
- [cosmetic] Tool “inference” changed its title: Inference
- [cosmetic] Tool “inference_stream” changed its title: Inference Stream
- [cosmetic] Tool “murmuration” changed its title: Murmuration
- [cosmetic] Tool “oracle_entropy” changed its title: Oracle Entropy
- [cosmetic] Tool “oracle_hallucination” changed its title: Oracle Hallucination
- [cosmetic] Tool “rag_augment” changed its title: Rag Augment
- [cosmetic] Tool “ratchet_advance” changed its title: Ratchet Advance
- [cosmetic] Tool “ratchet_probe” changed its title: Ratchet Probe
- [cosmetic] Tool “ratchet_register” changed its title: Ratchet Register
- [cosmetic] Tool “receipt_reputation” changed its title: Receipt Reputation
- [cosmetic] Tool “render_polyglot_all_pure” changed its title: Render Polyglot All Pure
- [cosmetic] Tool “render_polyglot_roundtrip_pure” changed its title: Render Polyglot Roundtrip Pure
- [cosmetic] Tool “reputation_record” changed its title: Reputation Record
- [cosmetic] Tool “rng_quantum” changed its title: Rng Quantum
- [cosmetic] Tool “rng_verify” changed its title: Rng Verify
- [cosmetic] Tool “route_capability” changed its title: Route Capability
- [cosmetic] Tool “security_zero_day” changed its title: Security Zero Day
- [cosmetic] Tool “sla_register” changed its title: Sla Register
- [cosmetic] Tool “sla_report” changed its title: Sla Report
- [cosmetic] Tool “swarm_inbox” changed its title: Swarm Inbox
- [cosmetic] Tool “swarm_relay” changed its title: Swarm Relay
- [cosmetic] Tool “text_keywords” changed its title: Text Keywords
- [cosmetic] Tool “text_sentiment” changed its title: Text Sentiment
- [cosmetic] Tool “text_summarize” changed its title: Text Summarize
- [cosmetic] Tool “threat_score” changed its title: Threat Score
- [cosmetic] Tool “trust_decay” changed its title: Trust Decay
- [cosmetic] Tool “trust_history” changed its title: Trust History
- [cosmetic] Tool “trust_score” changed its title: Trust Score
- [cosmetic] Tool “verify_settlement” changed its title: Verify Settlement

### 2026-10-25 (score 58, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (68)

### `murmuration` (~97 tokens)

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 a one-command bootstrap. Idempotent — re-call anytime to re-check.

Input parameters:

- `agent_id` (string): Optional stable id to track your onboarding state across calls.

### `agents_contradiction` (~50 tokens)

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.

Input parameters:

- `statements` (array, required)

### `agents_intent_classify` (~25 tokens)

Agents Intent Classify

[agents] Agent intent classification

Input parameters:

- `text` (string, required)

### `agents_plan` (~44 tokens)

Agents Plan

[agents] Autonomous agent goal planning

Input parameters:

- `constraints` (object): Optional constraints for the plan (e.g., time limits, resource caps)
- `goal` (string, required)

### `agents_register` (~30 tokens)

Agents Register

[agents] Register an agent

Input parameters:

- `agent_id` (string, required)
- `capabilities` (array, required)

### `agents_reputation` (~26 tokens)

Agents Reputation

[agents] Agent reputation and trust score

Input parameters:

- `agent_id` (string, required)

### `agents_semantic_diff` (~67 tokens)

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.

Input parameters:

- `context` (string)
- `output_a` (string, required)
- `output_b` (string, required)

### `agents_topology` (~16 tokens)

Agents Topology

[agents] Live swarm topology

### `compliance_check` (~147 tokens)

Compliance Check

[security] Delegation-depth + KL gate (GOV-100). Reads chain_depth and kl_divergence. It does NOT read your data description and does NOT evaluate GDPR/CCPA - compliant:true only means the delegation chain is shallow and KL is under epsilon.

Input parameters:

- `chain_depth` (integer): Delegation chain depth. Higher = deeper hand-off. Past the gate threshold the result escalates to quarantine_escalation.
- `description` (string): Free text. Accepted for readability and IGNORED by the gate. It never changes the verdict.
- `kl_divergence` (number): eps_KL divergence of the current policy from baseline. Above epsilon fails the gate.

### `compliance_eu_ai_act` (~45 tokens)

Compliance Eu Ai Act

[security] EU AI Act compliance certificate

Input parameters:

- `intended_purpose` (string, required)
- `risk_category` (string, required)
- `system_id` (string, required)

### `compliance_explain` (~48 tokens)

Compliance Explain

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

Input parameters:

- `decision_id` (string, required)
- `model_id` (string, required)
- `subject_context` (object, required)

### `compliance_fairness` (~57 tokens)

Compliance Fairness

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

Input parameters:

- `dataset_id` (string, required)
- `metric` (string, required)
- `model_id` (string, required)
- `protected_attrs` (array, required)

### `compliance_incident` (~46 tokens)

Compliance Incident

[security] Report compliance incident

Input parameters:

- `affected_users` (integer, required)
- `description` (string, required)
- `severity` (string, required)
- `system_id` (string, required)

### `compliance_incidents` (~23 tokens)

Compliance Incidents

[security] Incident registry

Input parameters:

- `system_id` (string, required)

### `compliance_lineage` (~39 tokens)

Compliance Lineage

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

Input parameters:

- `dataset_stages` (array, required)
- `model_id` (string, required)

### `compliance_oversight` (~47 tokens)

Compliance Oversight

[security] Log oversight event

Input parameters:

- `decision` (string, required)
- `notes` (string, required)
- `reviewer_id` (string, required)
- `system_id` (string, required)

### `compliance_oversight_history` (~26 tokens)

Compliance Oversight History

[security] Oversight history

Input parameters:

- `system_id` (string, required)

### `compliance_transparency` (~37 tokens)

Compliance Transparency

[security] Transparency report

Input parameters:

- `include` (array, required)
- `period` (string, required)
- `system_id` (string, required)

### `defi_bridge_verify` (~62 tokens)

Defi Bridge Verify

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

Input parameters:

- `amount` (number, required)
- `bridge_id` (string, required)
- `dest_chain` (string, required)
- `source_chain` (string, required)
- `token` (string, required)

### `defi_contract_audit` (~41 tokens)

Defi Contract Audit

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

Input parameters:

- `contract_id` (string, required)
- `contract_type` (string, required)

### `defi_liquidation_check` (~59 tokens)

Defi Liquidation Check

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

Input parameters:

- `collateral_factor` (number, required)
- `collateral_value` (number, required)
- `debt_value` (number, required)
- `position_id` (string, required)

### `defi_optimize` (~48 tokens)

Defi Optimize

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

Input parameters:

- `position` (object, required)
- `protocol` (string, required)
- `risk_tolerance` (number, required)

### `defi_oracle_verify` (~68 tokens)

Defi Oracle Verify

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

Input parameters:

- `asset` (string, required)
- `oracle_address` (string, required)
- `price_feed` (string, required)
- `reference_price` (number, required)
- `tvl_at_risk` (number, required)

### `defi_risk_score` (~50 tokens)

Defi Risk Score

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

Input parameters:

- `market_conditions` (object, required)
- `position` (object, required)
- `protocol` (string, required)

### `defi_yield_optimize` (~45 tokens)

Defi Yield Optimize

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

Input parameters:

- `principal_usd` (number, required)
- `risk_tolerance` (number, required)

### `drift_certificate` (~21 tokens)

Drift Certificate

[trust] Drift certificate

Input parameters:

- `id` (string, required)

### `drift_check` (~48 tokens)

Drift Check

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

Input parameters:

- `current_window` (object, required)
- `model_id` (string, required)
- `reference_window` (object, required)

### `escrow_create` (~56 tokens)

Escrow Create

[defi] Create agent-to-agent escrow

Input parameters:

- `amount` (number, required)
- `conditions` (object)
- `currency` (string, required)
- `payee_id` (string, required)
- `payer_id` (string, required)

### `escrow_dispute` (~39 tokens)

Escrow Dispute

[defi] Open escrow dispute

Input parameters:

- `escrow_id` (string, required)
- `evidence` (object)
- `reason` (string, required)

### `escrow_release` (~25 tokens)

Escrow Release

[defi] Release escrowed funds

Input parameters:

- `escrow_id` (string, required)

### `forge_badge` (~32 tokens)

Forge Badge

[fuse] Model quality badge

Input parameters:

- `model` (string, required): Model id to fetch the quality badge for.

### `forge_delta_submit` (~40 tokens)

Forge Delta Submit

[fuse] Submit a model delta

Input parameters:

- `delta` (object, required)
- `description` (string)
- `model_id` (string, required)

### `forge_leaderboard` (~17 tokens)

Forge Leaderboard

[fuse] Model leaderboard

### `forge_quarantine` (~18 tokens)

Forge Quarantine

[fuse] Quarantined models

### `forge_verify` (~33 tokens)

Forge Verify

[fuse] Verify a model submission

Input parameters:

- `model_id` (string, required)
- `verification_type` (string)

### `identity_sybil_check` (~19 tokens)

Identity Sybil Check

[identity] Sybil-resistance check

### `identity_verify` (~24 tokens)

Identity Verify

[identity] Topological identity verification

Input parameters:

- `agent_id` (string, required)

### `inference` (~25 tokens)

Inference

[inference] Chat inference with hallucination guard

Input parameters:

- `messages` (array, required)

### `inference_stream` (~27 tokens)

Inference Stream

[inference] Streaming inference with chain-of-thought

Input parameters:

- `messages` (array, required)

### `oracle_entropy` (~16 tokens)

Oracle Entropy

[trust] Entropy epoch oracle

### `oracle_hallucination` (~33 tokens)

Oracle Hallucination

[trust] Hallucination oracle

Input parameters:

- `claim` (string, required)
- `context` (string)

### `rag_augment` (~18 tokens)

Rag Augment

[inference] Trusted RAG augmentation

### `ratchet_advance` (~29 tokens)

Ratchet Advance

[identity] RatchetGate — advance session

Input parameters:

- `session_id` (string, required)

### `ratchet_probe` (~20 tokens)

Ratchet Probe

[identity] RatchetGate — health probe

### `ratchet_register` (~28 tokens)

Ratchet Register

[identity] RatchetGate — register session

Input parameters:

- `session_id` (string, required)

### `reputation_record` (~47 tokens)

Reputation Record

[agents] Record agent interaction

Input parameters:

- `agent_id` (string, required)
- `counterparty_id` (string)
- `interaction_type` (string, required)
- `outcome` (string, required)

### `rng_quantum` (~19 tokens)

Rng Quantum

[inference] Quantum random number with proof

### `rng_verify` (~18 tokens)

Rng Verify

[inference] Verify current epoch random value

### `security_zero_day` (~31 tokens)

Security Zero Day

[security] Zero-day threat assessment

Input parameters:

- `context` (object)
- `target` (string, required)

### `sla_register` (~38 tokens)

Sla Register

[agents] Register an SLA

Input parameters:

- `consumer_id` (string, required)
- `provider_id` (string, required)
- `terms` (object, required)

### `sla_report` (~38 tokens)

Sla Report

[agents] Report SLA violation

Input parameters:

- `description` (string)
- `sla_id` (string, required)
- `violation_type` (string, required)

### `swarm_inbox` (~16 tokens)

Swarm Inbox

[agents] Poll swarm inbox

### `swarm_relay` (~44 tokens)

Swarm Relay

[agents] Relay message through swarm

Input parameters:

- `message` (object, required)
- `target_agent_id` (string, required)
- `ttl` (integer): Hop limit for relay

### `text_keywords` (~30 tokens)

Text Keywords

[inference] Keyword extraction

Input parameters:

- `max_keywords` (integer)
- `text` (string, required)

### `text_sentiment` (~24 tokens)

Text Sentiment

[inference] Sentiment analysis

Input parameters:

- `text` (string, required)

### `text_summarize` (~25 tokens)

Text Summarize

[inference] Text summarization

Input parameters:

- `text` (string, required)

### `threat_score` (~31 tokens)

Threat Score

[security] Multi-vector threat score

Input parameters:

- `agent_id` (string, required)
- `context` (string)

### `trust_decay` (~16 tokens)

Trust Decay

[trust] Current trust ceiling value

### `trust_history` (~23 tokens)

Trust History

[trust] Trust score history

Input parameters:

- `agent_id` (string, required)

### `trust_score` (~24 tokens)

Trust Score

[trust] Bounded trust score

Input parameters:

- `agent_id` (string, required)

### `audit_work_claim` (~131 tokens)

Audit Work Claim

[Ledger product, entitlement: ledger] Recompute-audit an agent work claim: re-derive a deterministic SHA-256 digest from the claimed inputs and check it against the claimed digest. Returns GREEN (matches), RED (tampered), or UNVERIFIED (no claim supplied). Replay, not opinion. 3 free calls/day, then entitlement 'ledger'.

Input parameters:

- `claimed_digest` (string): The agent's claimed SHA-256 digest to verify against. Omit for UNVERIFIED + the recomputed digest.
- `inputs` (object, required): The work/claim payload to recompute a digest over.

### `verify_settlement` (~85 tokens)

Verify Settlement

[Ledger product, entitlement: ledger] Proof-gated settlement: recompute the work digest and authorize a payout only if the claimed digest verifies GREEN. No proof, no payout. 3 free calls/day, then entitlement 'ledger'.

Input parameters:

- `claimed_digest` (string): Claimed digest the payout is conditioned on.
- `inputs` (object, required): The work payload backing the settlement.

### `receipt_reputation` (~80 tokens)

Receipt Reputation

[Ledger product, entitlement: ledger] Compute an agent's reputation from a ledger of verifiable receipts (verified minus refuted), deterministically - not from vibes or LLM judgment. 3 free calls/day, then entitlement 'ledger'.

Input parameters:

- `receipts` (array, required): List of receipt objects, each with an 'ok' boolean and optional 'score'.

### `detect_contradiction` (~95 tokens)

Detect Contradiction

[Ledger product, entitlement: ledger] Detect contradictions across structured claims: the same key asserted with conflicting values flips RED, otherwise GREEN. Deterministic and recomputable. Use agents_contradiction instead when comparing free-text agent prose. 3 free calls/day, then entitlement 'ledger'.

Input parameters:

- `claims` (array, required): List of claim objects, each with a 'key' (or 'subject') and a 'value'.

### `enforce_sla` (~93 tokens)

Enforce Sla

[Ledger product, entitlement: ledger] Enforce an SLA/obligation by recomputation: the obligation is met only if the work verifies GREEN against its claimed digest. 3 free calls/day, then entitlement 'ledger'.

Input parameters:

- `claimed_digest` (string): Claimed digest the obligation is conditioned on.
- `inputs` (object, required): The work payload to verify.
- `obligation` (string): Human-readable obligation label.

### `route_capability` (~54 tokens)

Route Capability

[Ledger product, entitlement: ledger] Route a natural-language intent to a deterministic capability/pipeline coordinate. 3 free calls/day, then entitlement 'ledger'.

Input parameters:

- `intent` (string, required): The natural-language intent to route.

### `render_polyglot_roundtrip_pure` (~98 tokens)

Render Polyglot Roundtrip Pure

[Fuse product · entitlement: fuse · FREE_R2_DEMO] Syntax-as-Data polyglot render head: source -> language-neutral logic IR -> source in target language. Canonical demo examples baked to R2 (4 examples × 12 languages). Live emit of novel inputs via the SDK.

Input parameters:

- `atom_name` (string, required)
- `language` (string)
- `source_text` (string, required)

### `render_polyglot_all_pure` (~81 tokens)

Render Polyglot All Pure

[Fuse product · entitlement: fuse · FREE_R2_DEMO] Polyglot emit to all 7 supported targets in one call. Returns {ok, ir, results, languages}. Canonical demo examples baked to R2; novel inputs via SDK.

Input parameters:

- `atom_name` (string, required)
- `source_text` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/tech-atomadic-atomadic/mcp#diagnostics

## Score history

- 2026-11-05: 63
- 2026-11-04: 62
- 2026-11-03: 62
- 2026-11-02: 61
- 2026-11-01: 61
- 2026-10-31: 60
- 2026-10-30: 60
- 2026-10-29: 59
- 2026-10-28: 59
- 2026-10-27: 58
- 2026-10-26: 58
- 2026-10-25: 58
- 2026-10-24: 57
- 2026-10-23: 57
- 2026-10-22: 56
- 2026-10-21: 56
- 2026-10-20: 55
- 2026-10-19: 55
- 2026-10-18: 54
- 2026-10-17: 54

## Common questions

### What is the Atomadic MCP server?

Atomadic MCP is listed in the public MCP registry as tech.atomadic/atomadic. Atomadic MCP: 68 deterministic tools for agent identity, escrow, SLA, EU AI Act compliance. This page covers its hosted endpoint (https://mcp.atomadic.tech/mcp).

### Is the Atomadic MCP server safe to use?

Atomadic MCP scores 63 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Atomadic MCP server expose?

Atomadic MCP exposes 68 tools: murmuration, agents_contradiction, agents_intent_classify, agents_plan, agents_register, and 63 more. Their descriptions and schemas cost roughly 2,952 tokens of context every time the server is loaded.

### Does the Atomadic MCP server require authentication?

No. We connected to Atomadic MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Atomadic MCP server still maintained?

Atomadic MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.atomadic.tech/mcp
- Website: https://atomadic.tech/
- Changelog RSS feed: https://verifymcp.io/servers/tech-atomadic-atomadic/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/tech-atomadic-atomadic/mcp.json
- HTML version of this page: https://verifymcp.io/servers/tech-atomadic-atomadic/mcp