io.tooloracle/dora

REMOTE · TOOLORACLE.IO · SCANNED AUG 3

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

Available components

+5 this week 67 67 Trust /100

Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security66

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
Authorisation not fully verified: no authorisation is required to call this server, and 15 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability71

AI-judged instruction clarity (good).Pass
Tool/resource definitions use about 1204 tokens (~80/item across 15 items; 15 tools + 0 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass

Capabilities40

Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · tooloracle.io

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

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

# ~/.codex/config.toml

[mcp_servers.io-tooloracle-dora]
url = "https://tooloracle.io/dora/mcp/"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-tooloracle-dora": {
      "type": "remote",
      "url": "https://tooloracle.io/dora/mcp/",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add io-tooloracle-dora --url https://tooloracle.io/dora/mcp/ --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  io-tooloracle-dora:
    url: "https://tooloracle.io/dora/mcp/"

// mcp.json

{
  "mcpServers": {
    "io-tooloracle-dora": {
      "type": "http",
      "url": "https://tooloracle.io/dora/mcp/"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

3 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
1 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
31 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
29 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
28 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
26 Jul 26 62

First indexed and scored.

Show 7 earlier entries Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://tooloracle.io/dora/mcp/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=tooloracle.io	CN=YE1,O=Let's Encrypt,C=US	15 Jul 2026	13 Oct 2026	ECDSA 256	ECDSA-SHA384	5f17476491787e67dfd3d995c4c2b1679c9
SANs: mcp.tooloracle.io, tooloracle.io, www.tooloracle.io
CN=YE1,O=Let's Encrypt,C=US (CA)	CN=Root YE,O=ISRG,C=US	3 Sept 2025	2 Sept 2028	ECDSA 384	ECDSA-SHA384	5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA)	CN=ISRG Root X2,O=Internet Security Research Group,C=US	13 May 2026	2 Sept 2032	ECDSA 384	ECDSA-SHA384	872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA)	CN=ISRG Root X1,O=Internet Security Research Group,C=US	13 May 2026	2 Sept 2032	ECDSA 384	SHA256-RSA	6c8f1dc727c7117f7baf853ac980f9cd

DNSSEC secure

Validation of tooloracle.io. — Secure

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
io.	present	57355	8	Verified
tooloracle.io.	present	45856	8	Verified
tooloracle.io.				Verified address RRset verified with the apex keys

Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result	No authorisation required
HTTP status	200

Header	Value
strict-transport-security	max-age=31536000; includeSubDomains; preload
content-security-policy	default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; img-src 'self' data: https:; font-src 'self' data: https://fonts.gstatic.com; connect-src 'self' https://api.feedoracle.io https://tooloracle.io https://.tooloracle.io https://fonts.googleapis.com wss://.tooloracle.io; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'none';
x-content-type-options	nosniff
x-frame-options	DENY
referrer-policy	strict-origin-when-cross-origin
permissions-policy	geolocation=(), microphone=(), camera=()

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://tooloracle.io/dora/mcp/	Verified	200
http (plaintext)	http://tooloracle.io/dora/mcp/	HTTPS enforced	308	https://tooloracle.io/dora/mcp/

MCP tools — 15 exposed · ~1,204 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

breach_check ~74

HaveIBeenPwned breach database — check domain/company breach exposure. DORA Art. 18 incident assessment.

Input Output Examples

Name	Type	Req	Description
domain	string	—	Company domain e.g. 'meinbank.de' (optional — omit for latest breaches)
limit	integer	—	Max results 1-50 (default: 20)

No output schema declared.

No examples provided.

cert_advisories ~72

CERT-Bund security advisories — authoritative DE source for ICT threats. DORA Art. 17 threat monitoring.

Input Output Examples

Name	Type	Req	Description
keyword	string	—	Filter by keyword e.g. 'Windows', 'Apache', 'Cisco'
limit	integer	—	Max results 1-30 (default: 15)

No output schema declared.

No examples provided.

cloud_status ~69

Live status of AWS, GCP, Azure cloud providers. DORA Art. 28 third-party ICT risk monitoring.

Input Output Examples

Name	Type	Req	Description
limit	integer	—	Max incidents per provider (default: 10)
provider	string	—	Provider: aws, gcp, azure, all (default: all)

No output schema declared.

No examples provided.

cve_latest ~99

Latest critical CVEs — daily DORA ICT risk briefing. Filter by severity and banking relevance.

Input Output Examples

Name	Type	Req	Description
banking_only	boolean	—	Filter to banking-relevant vendors only (default: false)
days	integer	—	Last N days (default: 7)
limit	integer	—	Max results 1-20 (default: 10)
severity	string	—	CRITICAL, HIGH, MEDIUM (default: CRITICAL)

No output schema declared.

No examples provided.

cve_search ~128

Search CVEs by keyword, vendor or product. Returns CVSS scores, attack vectors, DORA pillar mapping.

Input Output Examples

Name	Type	Req	Description
days	integer	—	Published within last N days (default: 30)
keyword	string	—	Search keyword e.g. 'authentication bypass', 'remote code execution'
limit	integer	—	Max results 1-20 (default: 10)
severity	string	—	CVSS severity: CRITICAL, HIGH, MEDIUM, LOW
vendor	string	—	Vendor/product e.g. 'SAP', 'Cisco', 'Microsoft Exchange'

No output schema declared.

No examples provided.

dora_calendar ~26

DORA compliance milestones and upcoming deadlines for financial institutions. All Art. references included.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

dora_news ~102

EBA/DORA regulatory news for banks. Topics: general, eba, incident, third_party, testing, guidelines, bafin, swift.

Input Output Examples

Name	Type	Req	Description
lang	string	—	Language: en or de (default: en)
limit	integer	—	Max articles 1-20 (default: 10)
topic	string	—	Topic: general, eba, incident, third_party, testing, guidelines, bafin, swift, fintech

No output schema declared.

No examples provided.

health_check ~19

DORAOracle server status and all backend connectivity checks.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

incident_timeline ~109

Generate a DORA Art. 19-aligned ICT incident reporting timeline with the regulatory deadline structure. Supports - does not constitute - compliant reporting.

Input Output Examples

Name	Type	Req	Description
classification	string	—	Incident class: major, significant, minor (default: major)
incident_time	string	—	ISO timestamp of incident e.g. '2026-03-19T14:00:00Z' (default: now)
sector	string	—	Sector: banking, insurance, payment (default: banking)

No output schema declared.

No examples provided.

kev_check ~65

Check if a specific CVE is in CISA KEV (actively exploited in the wild). Returns DORA incident classification guidance.

Input Output Examples

Name	Type	Req	Description
cve_id	string	—	CVE ID to check e.g. 'CVE-2021-44228' (Log4Shell)

No output schema declared.

No examples provided.

kev_list ~108

CISA Known Exploited Vulnerabilities — actively exploited CVEs with patch deadlines. DORA Art. 9 patch compliance.

Input Output Examples

Name	Type	Req	Description
days	integer	—	Added to KEV within last N days (default: 30)
limit	integer	—	Max results 1-50 (default: 15)
overdue	boolean	—	Show only overdue patches (default: false)
vendor	string	—	Filter by vendor e.g. 'Cisco', 'Microsoft', 'SAP'

No output schema declared.

No examples provided.

mitre_techniques ~104

MITRE ATT&CK techniques for DORA TLPT / TIBER-EU penetration testing. Maps to DORA Art. 26.

Input Output Examples

Name	Type	Req	Description
keyword	string	—	Search keyword e.g. 'ransomware', 'phishing', 'credential'
limit	integer	—	Max results 1-20 (default: 10)
tactic	string	—	Filter by tactic: Initial Access, Lateral Movement, Impact, Persistence, etc.

No output schema declared.

No examples provided.

provider_risk ~60

DORA Art. 28 ICT third-party risk assessment: CVE history, news, GLEIF registration, contractual checklist.

Input Output Examples

Name	Type	Req	Description
provider	string	—	Provider name e.g. 'SAP', 'Salesforce', 'AWS', 'Temenos'

No output schema declared.

No examples provided.

threat_actors ~101

Feodo Tracker: live C2 botnet servers (Emotet, QakBot, etc.). Actionable IP blocklist for DORA Art. 9.

Input Output Examples

Name	Type	Req	Description
limit	integer	—	Max results 1-100 (default: 20)
malware	string	—	Filter by malware family: Emotet, QakBot, Dridex, TrickBot
status	string	—	Filter by status: online, offline

No output schema declared.

No examples provided.

tlpt_scenarios ~68

TIBER-EU threat scenarios for DORA resilience testing planning. Banking-specific attack simulations.

Input Output Examples

Name	Type	Req	Description
focus	string	—	Focus area: swift, ransomware, insider, ddos, cloud (default: all)
sector	string	—	Sector: banking (default: banking)

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	62
27 Jul	62
28 Jul	63
29 Jul	64
30 Jul	64
31 Jul	65
1 Aug	66
2 Aug	66
3 Aug	67