compliance_incidents — Atomadic MCP MCP Tool
compliance_incidents
(compliance incidents) is one of 68 tools on the
Atomadic MCP
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call compliance_incidents from your client
- Claude Code Atomadic MCP compliance_incidents run in your project directory
- Claude Desktop Atomadic MCP compliance_incidents ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Atomadic MCP compliance_incidents ~/.cursor/mcp.json
- VS Code Atomadic MCP compliance_incidents .vscode/mcp.json
- Zed Atomadic MCP compliance_incidents ~/.config/zed/settings.json
- Windsurf Atomadic MCP compliance_incidents ~/.codeium/windsurf/mcp_config.json
- Cline Atomadic MCP compliance_incidents ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Atomadic MCP compliance_incidents ~/.gemini/settings.json
- Grok Atomadic MCP compliance_incidents .mcp.json (in your project root)
- ChatGPT Atomadic MCP compliance_incidents Settings → Connectors → Advanced → Developer mode
- Claude.ai Atomadic MCP compliance_incidents Settings → Connectors → Add custom connector
- LangChain Atomadic MCP compliance_incidents pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http atomadic https://mcp.atomadic.tech/mcpOther tools on this server
- 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_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_{model}
- 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
- audit_work_claim
- verify_settlement
- receipt_reputation
- detect_contradiction
- enforce_sla
- route_capability
- render_polyglot_roundtrip_pure
- render_polyglot_all_pure
This list was read from the server itself, by connecting to it and calling tools/list on 17 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.