Skip to content

io.tooloracle/conductor

by tooloracle.io · remote · no sign-in to list tools · v1.0.0 · published by io.tooloracle

DORA OS Conductor — 16-tool meta-orchestrator for DORA compliance workflow automation.

Changes · 13
CompareRegistry entry

16 tools: 13 change things and 3 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http conductor https://tooloracle.io/conductor/mcp/

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

16 tools

Changes things 13Claude Code: ask
  • board_briefingExecutive briefing: readiness score, cloud status, test coverage, deadlines, key risks.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Executive briefing: readiness score, cloud status, test coverage, deadlines, key risks.
  • daily_checkDaily compliance health check: cloud, tests, findings, regulatory changes, CVEs.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Daily compliance health check: cloud, tests, findings, regulatory changes, CVEs.
  • full_assessmentRun complete DORA assessment across ALL 16 oracles.No findings

    Why it is in this group

    • The description's first verb is "run": a word for a change.
    Description, as the server wrote it
    Run complete DORA assessment across ALL 16 oracles. Returns aggregated risk score, critical issues, and per-oracle details.
  • gap_analysisCross-oracle gap analysis: compliance, testing, policies, training.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Cross-oracle gap analysis: compliance, testing, policies, training.
  • health_checkConductor health + oracle availability.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Conductor health + oracle availability.
  • nca_readinessBaFin/NCA audit readiness checklist: score, red articles, testing, RoI, training.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    BaFin/NCA audit readiness checklist: score, red articles, testing, RoI, training.
  • obligation_overviewAll obligation_ids from all oracles in one call.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    All obligation_ids from all oracles in one call.
  • onboard_entityFull entity onboarding workflow across all oracles.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Full entity onboarding workflow across all oracles.
  • plan_remediationGiven current gaps, generate prioritized remediation plan with actions, oracles, urgency, deadlines.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Given current gaps, generate prioritized remediation plan with actions, oracles, urgency, deadlines.
  • react_to_eventReact to compliance event: cve, law_change, cloud_incident, breach, sanctions_hit, audit_notice, supply_chain_disruption, nis2_incident, contract_issue, tax_deadline, medical_devic…No findings

    Why it is in this group

    • The name "react_to_event" says "react": a word for a change.
    Description, as the server wrote it
    React to compliance event: cve, law_change, cloud_incident, breach, sanctions_hit, audit_notice, supply_chain_disruption, nis2_incident, contract_issue, tax_deadline, medical_device_alert, employee_issue. Auto-dispatches to relevant oracles.
  • readiness_dashboardHealth status of all 23 oracles + total tool count.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Health status of all 23 oracles + total tool count. System-wide monitoring.
  • run_workflowExecute a predefined multi-step workflow across oracles.No findings

    Why it is in this group

    • The name "run_workflow" says "run": a word for a change.
    Description, as the server wrote it
    Execute a predefined multi-step workflow across oracles.
  • sync_allTrigger all sync_to_ampel across TestOracle + CloudOracle.No findings

    Why it is in this group

    • The name "sync_all" says "sync": a word for a change.
    Description, as the server wrote it
    Trigger all sync_to_ampel across TestOracle + CloudOracle. Updates AmpelOracle with latest data.
Only reads 3Claude Code: allow
  • oracle_statusHealth status of all 16 DORA OS oracles.No findings

    Why it is in this group

    • The name "oracle_status" says "status": a word for reading.
    Description, as the server wrote it
    Health status of all 16 DORA OS oracles.
  • pingConnectivity test.No findings

    Why it is in this group

    • The name "ping" says "ping": a word for reading.
    Description, as the server wrote it
    Connectivity test.
  • workflow_libraryList all available predefined workflows with descriptions and step counts.No findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.
    Description, as the server wrote it
    List all available predefined workflows with descriptions and step counts.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http conductor https://tooloracle.io/conductor/mcp/

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__conductor__workflow_library",
      "mcp__conductor__oracle_status",
      "mcp__conductor__ping"
    ],
    "ask": [
      "mcp__conductor__full_assessment",
      "mcp__conductor__readiness_dashboard",
      "mcp__conductor__run_workflow",
      "mcp__conductor__plan_remediation",
      "mcp__conductor__react_to_event",
      "mcp__conductor__sync_all",
      "mcp__conductor__gap_analysis",
      "mcp__conductor__board_briefing",
      "mcp__conductor__nca_readiness",
      "mcp__conductor__onboard_entity",
      "mcp__conductor__daily_check",
      "mcp__conductor__obligation_overview",
      "mcp__conductor__health_check"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as conductor. Review it before you use it.