LeashIndex Get the report

Index / other

Atomadic MCP

tech-atomadic-atomadic declares 68 capabilities across 68 tools, with 2 critical issues.

98/100 exposureHigh exposure

Manifest recorded 2026-10-21 from tools/list on https://mcp.atomadic.tech/mcp, published in the official MCP registry as tech.atomadic/atomadic 0.6.9. The date changes only when the manifest does. Not verified by a maintainer.

Issues

These describe what this server's manifest declares. A product can provide controls that MCP has no way to express — token revocation, an admin console, audit logs — and this page cannot see them. The absence of a declaration is not evidence that a control is absent.

critical · no-revocation · All 68 tools

68 of 68 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.

critical · irreversible-uncapped · 1 of 68 tools

1 tool is classified as irreversible and declares no limit.

high · no-expiry · All 68 tools

68 of 68 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.

high · no-audit-trail · All 68 tools

68 of 68 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.

high · uncapped-write · 57 of 68 tools

57 tools can modify data and declare no limit.

low · uncapped-read · 10 of 68 tools

10 tools can read data and declare no limit.

Declared capabilities

How each tool was read. declared means the server's own annotation said so — self-reported and unverified. inferred is from the tool's name. assumed means nothing indicated either way.

ToolRead asBasis
murmurationwrite assumed
agents_contradictionwrite assumed
agents_intent_classifywrite assumed
agents_planwrite assumed
agents_registerwrite assumed
agents_reputationwrite assumed
agents_semantic_diffwrite assumed
agents_topologywrite assumed
compliance_checkwrite assumed
compliance_eu_ai_actwrite assumed
compliance_explainwrite assumed
compliance_fairnesswrite assumed
compliance_incidentwrite assumed
compliance_incidentswrite assumed
compliance_lineagewrite assumed
compliance_oversightwrite assumed
compliance_oversight_historyread inferred
compliance_transparencywrite assumed
defi_bridge_verifyread inferred
defi_contract_auditread inferred
defi_liquidation_checkwrite assumed
defi_optimizewrite assumed
defi_oracle_verifyread inferred
defi_risk_scorewrite assumed
defi_yield_optimizewrite assumed
drift_certificatewrite assumed
drift_checkwrite assumed
escrow_createwrite inferred
escrow_disputewrite assumed
escrow_releasewrite assumed
forge_badge_{model}write assumed
forge_delta_submitwrite assumed
forge_leaderboardwrite assumed
forge_quarantinewrite assumed
forge_verifyread inferred
identity_sybil_checkwrite assumed
identity_verifyread inferred
inferencewrite assumed
inference_streamwrite assumed
oracle_entropywrite assumed
oracle_hallucinationwrite assumed
rag_augmentwrite assumed
ratchet_advancewrite assumed
ratchet_probewrite assumed
ratchet_registerwrite assumed
reputation_recordread inferred
rng_quantumwrite assumed
rng_verifyread inferred
security_zero_daywrite assumed
sla_registerwrite assumed
sla_reportwrite assumed
swarm_inboxwrite assumed
swarm_relaysend inferred
text_keywordswrite assumed
text_sentimentwrite assumed
text_summarizewrite assumed
threat_scorewrite assumed
trust_decaywrite assumed
trust_historyread inferred
trust_scorewrite assumed
audit_work_claimwrite assumed
verify_settlementread inferred
receipt_reputationwrite assumed
detect_contradictionwrite assumed
enforce_slawrite assumed
route_capabilitywrite assumed
render_polyglot_roundtrip_purewrite assumed
render_polyglot_all_purewrite assumed
Answering this question about your own agent? The self-serve stack report applies the same reading to your own stack or server and gives you a dated document you can hand to a customer's security review. It is generated in your browser, with nobody to wait for. Buying one does not change this page, its score or its place in the index — see Independence.
Maintain this server? If this page misreads your manifest, or your server has changed, submit its current tools/list response and it will be re-scored and dated. Corrections are published alongside the original, not in place of it.