Skip to content

io.tooloracle/dora

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

DORAOracle — 15 tools for DORA Art.5-32: risk register, ICT incidents, TLPT, third-party.

Changes · 12
CompareRegistry entry

15 tools: 12 change things and 3 only read.

Scanned Oct 21, 2026

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

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

Findings

Matches of fixed checks, with the text they matched.

1 info
  • Infomitre_techniques

    The input schema at properties.keyword.description mentions "credential".

    Matched text

    inputSchema.properties.keyword.description: "...keyword e.g. 'ransomware', 'phishing', 'credential'"

    What this check looks for

Tools

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

15 tools

Changes things 12Claude Code: ask
  • breach_checkHaveIBeenPwned breach database — check domain/company breach exposure.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
    HaveIBeenPwned breach database — check domain/company breach exposure. DORA Art. 18 incident assessment.
  • cert_advisoriesCERT-Bund security advisories — authoritative DE source for ICT threats.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
    CERT-Bund security advisories — authoritative DE source for ICT threats. DORA Art. 17 threat monitoring.
  • cve_latestLatest critical CVEs — daily DORA ICT risk briefing.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
    Latest critical CVEs — daily DORA ICT risk briefing. Filter by severity and banking relevance.
  • dora_calendarDORA compliance milestones and upcoming deadlines for financial institutions.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
    DORA compliance milestones and upcoming deadlines for financial institutions. All Art. references included.
  • dora_newsEBA/DORA regulatory news for banks.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
    EBA/DORA regulatory news for banks. Topics: general, eba, incident, third_party, testing, guidelines, bafin, swift.
  • health_checkDORAOracle server status and all backend connectivity checks.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
    DORAOracle server status and all backend connectivity checks.
  • incident_timelineGenerate a DORA Art.No findings

    Why it is in this group

    • The description's first verb is "generate": a word for a change.
    Description, as the server wrote it
    Generate a DORA Art. 19-aligned ICT incident reporting timeline with the regulatory deadline structure. Supports - does not constitute - compliant reporting.
  • kev_checkCheck if a specific CVE is in CISA KEV (actively exploited in the wild).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
    Check if a specific CVE is in CISA KEV (actively exploited in the wild). Returns DORA incident classification guidance.
  • mitre_techniquesMITRE ATT&CK techniques for DORA TLPT / TIBER-EU penetration testing.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    Findings

    • Info

      The input schema at properties.keyword.description mentions "credential".

      Matched text

      inputSchema.properties.keyword.description: "...keyword e.g. 'ransomware', 'phishing', 'credential'"

      What this check looks for
    Description, as the server wrote it
    MITRE ATT&CK techniques for DORA TLPT / TIBER-EU penetration testing. Maps to DORA Art. 26.
  • provider_riskDORA Art.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
    DORA Art. 28 ICT third-party risk assessment: CVE history, news, GLEIF registration, contractual checklist.
  • threat_actorsFeodo Tracker: live C2 botnet servers (Emotet, QakBot, etc.).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
    Feodo Tracker: live C2 botnet servers (Emotet, QakBot, etc.). Actionable IP blocklist for DORA Art. 9.
  • tlpt_scenariosTIBER-EU threat scenarios for DORA resilience testing planning.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
    TIBER-EU threat scenarios for DORA resilience testing planning. Banking-specific attack simulations.
Only reads 3Claude Code: allow
  • cloud_statusLive status of AWS, GCP, Azure cloud providers.No findings

    Why it is in this group

    • The name "cloud_status" says "status": a word for reading.
    Description, as the server wrote it
    Live status of AWS, GCP, Azure cloud providers. DORA Art. 28 third-party ICT risk monitoring.
  • kev_listCISA Known Exploited Vulnerabilities — actively exploited CVEs with patch deadlines.No findings

    Why it is in this group

    • The name "kev_list" says "list": a word for reading.
    Description, as the server wrote it
    CISA Known Exploited Vulnerabilities — actively exploited CVEs with patch deadlines. DORA Art. 9 patch compliance.

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 dora https://tooloracle.io/dora/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__dora__cve_search",
      "mcp__dora__kev_list",
      "mcp__dora__cloud_status"
    ],
    "ask": [
      "mcp__dora__cve_latest",
      "mcp__dora__kev_check",
      "mcp__dora__cert_advisories",
      "mcp__dora__breach_check",
      "mcp__dora__threat_actors",
      "mcp__dora__incident_timeline",
      "mcp__dora__mitre_techniques",
      "mcp__dora__tlpt_scenarios",
      "mcp__dora__provider_risk",
      "mcp__dora__dora_news",
      "mcp__dora__dora_calendar",
      "mcp__dora__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 dora. Review it before you use it.