Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Atomadic starter MCP (50 tools)

REMOTE · MCP.ATOMADIC.TECH

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

+3 this week 58 Trust /100

Last scanned (6 hours ago)

Scores higher than 43% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Security

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability49
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 2360 tokens (~47/item across 50 items; 50 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management29
  • Stability check failed: schema churn in the 9 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 12% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 50 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 51 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 0
    • Stability: 0.27 → fail ▼ security
    • Tool “compliance_check” rewrote its description, which is the text the model reads security
    • “compliance_check” dropped the required parameter “operation” ▼ functional
    • “compliance_check” dropped the required parameter “jurisdiction” ▼ functional
    • “compliance_check” dropped the required parameter “data_type” ▼ functional
    • Schema quality: poor → fair functional
    • Server version: 125 → 126 functional
    • “compliance_check” added an optional parameter “kl_divergence” cosmetic
    • “compliance_check” added an optional parameter “description” cosmetic
    • “compliance_check” added an optional parameter “chain_depth” cosmetic
  • 4 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 124 → 125 functional
  • 3 Nov 26 0
    • Server version: 0.6.9 → 124 functional
  • 2 Nov 26 +1

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

  • 31 Oct 26 +1

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

  • 29 Oct 26 +1

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

  • 28 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 27 Oct 26 54

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://mcp.atomadic.tech/mcp/public

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=atomadic.tech CN=WE1,O=Google Trust Services,C=US 3 Oct 2026 1 Jan 2027 ECDSA 256 ECDSA-SHA256 897545e9c60854421346cc39e45cdd63
SANs: atomadic.tech, mcp.atomadic.tech, *.mcp.atomadic.tech
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.atomadic.tech. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
tech. present 2185 13 Verified
atomadic.tech. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.atomadic.tech/mcp/public Verified 200
http (plaintext) http://mcp.atomadic.tech/mcp/public HTTPS enforced 301 https://mcp.atomadic.tech/mcp/public
MCP tools · 50 exposed · ~2,183 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
agents_contradiction ~50

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

NameTypeReqDescription
statementsarrayyes–

No output schema declared.

No examples provided.

agents_plan ~44

[agents] Autonomous agent goal planning

NameTypeReqDescription
constraintsobject–Optional constraints for the plan (e.g., time limits, resource caps)
goalstringyes–

No output schema declared.

No examples provided.

agents_register ~30

[agents] Register an agent

NameTypeReqDescription
agent_idstringyes–
capabilitiesarrayyes–

No output schema declared.

No examples provided.

agents_reputation ~26

[agents] Agent reputation and trust score

NameTypeReqDescription
agent_idstringyes–

No output schema declared.

No examples provided.

agents_semantic_diff ~67

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

NameTypeReqDescription
contextstring––
output_astringyes–
output_bstringyes–

No output schema declared.

No examples provided.

audit_work_claim ~131

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

NameTypeReqDescription
claimed_digeststring–The agent's claimed SHA-256 digest to verify against. Omit for UNVERIFIED + the recomputed digest.
inputsobjectyesThe work/claim payload to recompute a digest over.

No output schema declared.

No examples provided.

compliance_check ~147

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

NameTypeReqDescription
chain_depthinteger–Delegation chain depth. Higher = deeper hand-off. Past the gate threshold the result escalates to quarantine_escalation.
descriptionstring–Free text. Accepted for readability and IGNORED by the gate. It never changes the verdict.
kl_divergencenumber–eps_KL divergence of the current policy from baseline. Above epsilon fails the gate.

No output schema declared.

No examples provided.

compliance_eu_ai_act ~45

[security] EU AI Act compliance certificate

NameTypeReqDescription
intended_purposestringyes–
risk_categorystringyes–
system_idstringyes–

No output schema declared.

No examples provided.

compliance_explain ~48

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

NameTypeReqDescription
decision_idstringyes–
model_idstringyes–
subject_contextobjectyes–

No output schema declared.

No examples provided.

compliance_fairness ~57

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

NameTypeReqDescription
dataset_idstringyes–
metricstringyes–
model_idstringyes–
protected_attrsarrayyes–

No output schema declared.

No examples provided.

compliance_incident ~46

[security] Report compliance incident

NameTypeReqDescription
affected_usersintegeryes–
descriptionstringyes–
severitystringyes–
system_idstringyes–

No output schema declared.

No examples provided.

compliance_incidents ~23

[security] Incident registry

NameTypeReqDescription
system_idstringyes–

No output schema declared.

No examples provided.

compliance_lineage ~39

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

NameTypeReqDescription
dataset_stagesarrayyes–
model_idstringyes–

No output schema declared.

No examples provided.

compliance_oversight ~47

[security] Log oversight event

NameTypeReqDescription
decisionstringyes–
notesstringyes–
reviewer_idstringyes–
system_idstringyes–

No output schema declared.

No examples provided.

compliance_transparency ~37

[security] Transparency report

NameTypeReqDescription
includearrayyes–
periodstringyes–
system_idstringyes–

No output schema declared.

No examples provided.

defi_optimize ~48

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

NameTypeReqDescription
positionobjectyes–
protocolstringyes–
risk_tolerancenumberyes–

No output schema declared.

No examples provided.

defi_risk_score ~50

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

NameTypeReqDescription
market_conditionsobjectyes–
positionobjectyes–
protocolstringyes–

No output schema declared.

No examples provided.

defi_yield_optimize ~45

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

NameTypeReqDescription
principal_usdnumberyes–
risk_tolerancenumberyes–

No output schema declared.

No examples provided.

detect_contradiction ~95

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

NameTypeReqDescription
claimsarrayyesList of claim objects, each with a 'key' (or 'subject') and a 'value'.

No output schema declared.

No examples provided.

drift_certificate ~21

[trust] Drift certificate

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

drift_check ~48

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

NameTypeReqDescription
current_windowobjectyes–
model_idstringyes–
reference_windowobjectyes–

No output schema declared.

No examples provided.

escrow_create ~56

[defi] Create agent-to-agent escrow

NameTypeReqDescription
amountnumberyes–
conditionsobject––
currencystringyes–
payee_idstringyes–
payer_idstringyes–

No output schema declared.

No examples provided.

escrow_dispute ~39

[defi] Open escrow dispute

NameTypeReqDescription
escrow_idstringyes–
evidenceobject––
reasonstringyes–

No output schema declared.

No examples provided.

escrow_release ~25

[defi] Release escrowed funds

NameTypeReqDescription
escrow_idstringyes–

No output schema declared.

No examples provided.

forge_badge ~32

[fuse] Model quality badge

NameTypeReqDescription
modelstringyesModel id to fetch the quality badge for.

No output schema declared.

No examples provided.

forge_delta_submit ~40

[fuse] Submit a model delta

NameTypeReqDescription
deltaobjectyes–
descriptionstring––
model_idstringyes–

No output schema declared.

No examples provided.

forge_leaderboard ~17

[fuse] Model leaderboard

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

forge_verify ~33

[fuse] Verify a model submission

NameTypeReqDescription
model_idstringyes–
verification_typestring––

No output schema declared.

No examples provided.

identity_sybil_check ~19

[identity] Sybil-resistance check

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

identity_verify ~24

[identity] Topological identity verification

NameTypeReqDescription
agent_idstringyes–

No output schema declared.

No examples provided.

inference ~25

[inference] Chat inference with hallucination guard

NameTypeReqDescription
messagesarrayyes–

No output schema declared.

No examples provided.

inference_stream ~27

[inference] Streaming inference with chain-of-thought

NameTypeReqDescription
messagesarrayyes–

No output schema declared.

No examples provided.

murmuration ~97

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.

NameTypeReqDescription
agent_idstring–Optional stable id to track your onboarding state across calls.

No output schema declared.

No examples provided.

oracle_hallucination ~33

[trust] Hallucination oracle

NameTypeReqDescription
claimstringyes–
contextstring––

No output schema declared.

No examples provided.

rag_augment ~18

[inference] Trusted RAG augmentation

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ratchet_advance ~29

[identity] RatchetGate — advance session

NameTypeReqDescription
session_idstringyes–

No output schema declared.

No examples provided.

ratchet_register ~28

[identity] RatchetGate — register session

NameTypeReqDescription
session_idstringyes–

No output schema declared.

No examples provided.

render_polyglot_all_pure ~81

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

NameTypeReqDescription
atom_namestringyes–
source_textstringyes–

No output schema declared.

No examples provided.

reputation_record ~47

[agents] Record agent interaction

NameTypeReqDescription
agent_idstringyes–
counterparty_idstring––
interaction_typestringyes–
outcomestringyes–

No output schema declared.

No examples provided.

rng_quantum ~19

[inference] Quantum random number with proof

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

rng_verify ~18

[inference] Verify current epoch random value

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

security_zero_day ~31

[security] Zero-day threat assessment

NameTypeReqDescription
contextobject––
targetstringyes–

No output schema declared.

No examples provided.

sla_register ~38

[agents] Register an SLA

NameTypeReqDescription
consumer_idstringyes–
provider_idstringyes–
termsobjectyes–

No output schema declared.

No examples provided.

sla_report ~38

[agents] Report SLA violation

NameTypeReqDescription
descriptionstring––
sla_idstringyes–
violation_typestringyes–

No output schema declared.

No examples provided.

swarm_inbox ~16

[agents] Poll swarm inbox

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

swarm_relay ~44

[agents] Relay message through swarm

NameTypeReqDescription
messageobjectyes–
target_agent_idstringyes–
ttlinteger–Hop limit for relay

No output schema declared.

No examples provided.

text_summarize ~25

[inference] Text summarization

NameTypeReqDescription
textstringyes–

No output schema declared.

No examples provided.

threat_score ~31

[security] Multi-vector threat score

NameTypeReqDescription
agent_idstringyes–
contextstring––

No output schema declared.

No examples provided.

trust_score ~24

[trust] Bounded trust score

NameTypeReqDescription
agent_idstringyes–

No output schema declared.

No examples provided.

verify_settlement ~85

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

NameTypeReqDescription
claimed_digeststring–Claimed digest the payout is conditioned on.
inputsobjectyesThe work payload backing the settlement.

No output schema declared.

No examples provided.

Install

How do I install the Atomadic starter MCP (50 tools) server?

Atomadic starter MCP (50 tools) is a hosted endpoint at https://mcp.atomadic.tech/mcp/public, 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.

remote · mcp.atomadic.tech

# add to Claude Code
claude mcp add --transport http atomadictech-aaaa-nexus 'https://mcp.atomadic.tech/mcp/public'
Common questions

What is the Atomadic starter MCP (50 tools) server?

Atomadic starter MCP (50 tools) is listed in the public MCP registry as io.github.atomadictech/aaaa-nexus. 50 starter MCP tools for AI compliance and trust: identity, escrow, SLA, EU AI Act. This page covers its hosted endpoint (https://mcp.atomadic.tech/mcp/public).

Is the Atomadic starter MCP (50 tools) server safe to use?

Atomadic starter MCP (50 tools) scores 58 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 starter MCP (50 tools) server expose?

Atomadic starter MCP (50 tools) exposes 50 tools: murmuration, agents_contradiction, agents_semantic_diff, agents_register, agents_reputation, and 45 more. Their descriptions and schemas cost roughly 2,183 tokens of context every time the server is loaded.

Does the Atomadic starter MCP (50 tools) server require authentication?

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

Is the Atomadic starter MCP (50 tools) server still maintained?

Atomadic starter MCP (50 tools) 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.