io.tooloracle/dora
REMOTE · TOOLORACLE.IO
DORAOracle — 15 tools for DORA Art.5-32: risk register, ICT incidents, TLPT, third-party.
Available components
Last scanned (10 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Security
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 → Why this is hard to 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 Usability74
- 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
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.
- 28 Sept 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
- 25 Sept 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 Aug 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
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 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
- 31 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
- 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
- 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
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 5 Nov 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=YE2,O=Let's Encrypt,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6375d594a6b9fdf6754e5a9a3d1f38b0dbd |
| SANs: mcp.tooloracle.io, tooloracle.io, www.tooloracle.io | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of tooloracle.io. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 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=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
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/ |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
breach_check ~74
HaveIBeenPwned breach database — check domain/company breach exposure. DORA Art. 18 incident assessment.
| 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.
| 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.
| 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.
| 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.
| 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 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.
| 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 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.
| 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.
| 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.
| 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.
| 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.
| 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.
| 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.
| 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.
How do I install the io.tooloracle/dora MCP server?
io.tooloracle/dora is a hosted endpoint at https://tooloracle.io/dora/mcp/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · tooloracle.io
claude mcp add --transport http io-tooloracle-dora 'https://tooloracle.io/dora/mcp/'
What is the io.tooloracle/dora MCP server?
io.tooloracle/dora is an MCP server listed in the public MCP registry as io.tooloracle/dora. DORAOracle, 15 tools for DORA Art.5-32: risk register, ICT incidents, TLPT, third-party. This page covers its hosted endpoint (https://tooloracle.io/dora/mcp/).
Is the io.tooloracle/dora MCP server safe to use?
io.tooloracle/dora scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.tooloracle/dora MCP server expose?
io.tooloracle/dora exposes 15 tools: cve_search, cve_latest, kev_list, kev_check, cert_advisories, and 10 more. Their descriptions and schemas cost roughly 1,204 tokens of context every time the server is loaded.
Does the io.tooloracle/dora MCP server require authentication?
No. We connected to io.tooloracle/dora without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.tooloracle/dora MCP server still maintained?
io.tooloracle/dora is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.