Skip to content

dora MCP server

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

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

15 tools: 12 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 12 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

12 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 dora MCP server can do

The dora MCP server is published by tooloracle.io, a domain the MCP Registry verified. It has 15 tools. It can create or change data (12 tools: cve_latest, kev_check, cert_advisories, breach_check and 8 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.

The fixed checks matched 1 finding (credentials-mention). Each one comes with the text it matched.

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.

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

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:27 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
12
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/dora/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 12 tools that change things (12 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://tooloracle.io/dora/mcp/: tools/list returned 15 tools to an anonymous client, including cve_latest (write), kev_check (write), cert_advisories (write), breach_check (write), threat_actors (write) and 7 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 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

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 dora https://tooloracle.io/dora/mcp/
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 or a way out, 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. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as dora. 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/dora/verify?hash=8f287510ffc65013fb5e6777593e5d4ddcf5fbf27277169219173f77233c6c49" | jq -e '.changed == false'

Pinned hash 8f287510ffc6, from Nov 21, 2026, 12:17 UTC.

Watch

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

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

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

Badge

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

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

dora MCP server: questions and answers

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

Is the dora MCP server safe?

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

Can the dora MCP server delete data?

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

Can the dora 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 dora MCP server have?

15 tools: 12 write, 3 read. cve_latest, kev_check, cert_advisories, breach_check, threat_actors, incident_timeline, mitre_techniques, tlpt_scenarios and 7 more.

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

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

Does the dora MCP server send data to outside services?

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

Has the dora MCP server changed its tools?

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