DriftOracle

The first compliance system that keeps itself compliant. Detects regulatory changes, evidence staleness, cloud drift, and control degradation — then heals automatically.

14
MCP Tools
4
Drift Types
4
Obligations
∞
Self-Healing
Regulatory DriftEvidence StalenessCloud DriftAuto-RemediationAll Free
MCP Endpoint: https://tooloracle.io/drift/mcp
Health: https://tooloracle.io/drift/health
Transport: StreamableHTTP + SSE
Monitors: RegWatchOracle, LawOracle, CloudOracle, AmpelOracle
Heals via: Conductor → sync_all → escalation → collect evidence → auto-resolve

Tools (14)

full_drift_scan
Run ALL 4 drift detections in one call. Returns STABLE / DRIFT_DETECTED / SIGNIFICANT_DRIFT.
All-in-One
detect_regulatory_drift
Scan for regulation changes affecting DORA. Checks RegWatch + LawOracle + EU feeds.
Regulatory
detect_evidence_drift
Find stale assessments, expired evidence, degraded controls.
Evidence
detect_cloud_drift
Cloud provider status changes since last check.
Cloud
detect_control_drift
Controls that degraded from GREEN to YELLOW/RED.
Controls
trigger_remediation
Self-healing: sync all → escalation → collect evidence → auto-resolve drift.
Self-Healing
drift_status
Current open drift events per entity.
Dashboard
mark_drift
Manually mark an article as DRIFT.
Manual
resolve_drift
Mark drift event as resolved.
Lifecycle
drift_history
History of all drift events.
Audit
configure_thresholds
Set evidence max age, assessment age, scan intervals.
Config
obligation_map
Drift detection obligations DORA-DFT-01 to DFT-04.
Reference
health_check
Server status.
System
ping
Connectivity test.
System

Self-healing cycle

1. full_drift_scan → detects 4 drift types (regulatory, evidence, cloud, controls)
2. trigger_remediation → Conductor.sync_all (Test + Cloud → AmpelOracle)
3. Run escalation engine → create/upgrade findings
4. Collect fresh Art. 10 evidence (CVE, threat intel)
5. Auto-resolve drift events that were fixed
Result: System returns to STABLE without human intervention