Skip to content

conductor MCP server

io.tooloracle/conductortooloracle.iostreamable-httpv1.0.0Scanned

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

16 tools: 13 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 13 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

13 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the conductor MCP server can do

The conductor MCP server is published by tooloracle.io, a domain the MCP Registry verified. It has 16 tools. It can create or change data (13 tools: full_assessment, readiness_dashboard, run_workflow, plan_remediation and 9 more), but cannot delete data. 3 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 21, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

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 3Show 3 read-only tools
  • 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.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:25 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
13
Protocol version
2025-03-26
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://tooloracle.io/.well-known/oauth-protected-resource/conductor/mcp
Authorization servers
https://feedoracle.io
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 13 tools that change things (13 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://tooloracle.io/conductor/mcp/: tools/list returned 16 tools to an anonymous client, including full_assessment (write), readiness_dashboard (write), run_workflow (write), plan_remediation (write), react_to_event (write) and 8 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

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/
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 or a way out, 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. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as conductor. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.tooloracle/conductor/verify?hash=c96cd088437fc2b55e19780916dcfc67c18f7f23f4fef96a5b31fb40d381d62d" | jq -e '.changed == false'

Pinned hash c96cd088437f, from Nov 21, 2026, 10:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.tooloracle/conductor/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.tooloracle/conductor
[![Anlyon Radar](https://radar.anlyon.com/badge/io.tooloracle/conductor.svg)](https://radar.anlyon.com/servers/io.tooloracle/conductor)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:52 UTC.

conductor MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the conductor MCP server safe?

No scan can promise that. What its definitions show: 16 tools, 13 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the conductor MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the conductor MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the conductor MCP server have?

16 tools: 13 write, 3 read. full_assessment, readiness_dashboard, run_workflow, plan_remediation, react_to_event, sync_all, gap_analysis, board_briefing and 8 more.

Does the conductor MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the conductor MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the conductor MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.