io.tooloracle/incidentoracle
REMOTE · TOOLORACLE.IO
IncidentOracle - 12-tool incident management MCP: triage, BaFin DORA reporting, RCA.
Available components
Last scanned (22 hours ago)
Scores higher than 10% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Monitoring and Observability
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 Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 503. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (5)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (6)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 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
- 19 Oct 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HSTS header: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 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
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 21 Nov 2026 · Probed https://tooloracle.io/incident/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 | 12 Nov 2026 | 10 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 56ada3c3c9667f6eeefdd0b9dbc93811aa2 |
| 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 |
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. | DS published | 38690 | 8 | Verified |
| tooloracle.io. | DS published | 45856 | 8 | Verified |
| tooloracle.io. | Verified address RRset verified with the apex keys |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 503 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://tooloracle.io/incident/mcp/ | HTTP error | 503 | |
| http (plaintext) | http://tooloracle.io/incident/mcp/ | HTTPS enforced | 308 | https://tooloracle.io/incident/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 →
classify_incident ~133
Classify an incident against the 6 DORA criteria (RTS 2024/1772). Determines if MAJOR (triggers 4h/72h/1m reporting) or NON-MAJOR.
| Name | Type | Req | Description |
|---|---|---|---|
| clients_affected | number | – | % of clients affected |
| criticality_of_services | boolean | – | Critical functions affected? |
| data_losses | boolean | – | Confidential/personal data affected? |
| duration_hours | number | – | – |
| economic_impact_eur | number | – | – |
| geographic_spread | integer | – | Number of EU member states |
| incident_id | string | yes | – |
No output schema declared.
No examples provided.
cyber_threat_notify ~98
Voluntary notification of a significant cyber threat (Art. 19(2)). Uses ITS 2025/302 Annex III template.
| Name | Type | Req | Description |
|---|---|---|---|
| affected_systems | string | – | – |
| description | string | – | – |
| iocs | string | – | – |
| mitigation | string | – | – |
| source | string | – | – |
| threat_type | string | – | – |
| title | string | yes | – |
| ttps | string | – | – |
No output schema declared.
No examples provided.
deadline_tracker ~22
Track all active MAJOR incident reporting deadlines. Shows overdue and upcoming.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
final_report ~95
Generate the 1-month final report with root cause analysis and lessons learned.
| Name | Type | Req | Description |
|---|---|---|---|
| client_communication | string | – | – |
| incident_id | string | yes | – |
| lessons_learned | string | – | – |
| preventive_measures | string | – | – |
| recovery_actions | string | – | – |
| resolved_at | string | – | – |
| root_cause_final | string | – | – |
| total_cost_eur | number | – | – |
No output schema declared.
No examples provided.
health_check ~11
Server status.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
incident_log ~50
Full incident register with filters (status, classification, severity, search).
| Name | Type | Req | Description |
|---|---|---|---|
| classification | string | – | – |
| search | string | – | – |
| severity | string | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
incident_stats ~23
Dashboard: total/open/major incidents, overdue deadlines, by severity/status.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
initial_notification ~113
Generate the 4h initial notification for a MAJOR incident (ITS 2025/302 Annex I). Must be submitted within 4h of classification, max 24h after detection.
| Name | Type | Req | Description |
|---|---|---|---|
| affected_states | string | – | Comma-separated EU member states |
| authority | string | – | Competent authority (e.g., BaFin, FMA) |
| discovery_method | string | – | – |
| entity_lei | string | – | – |
| entity_name | string | – | – |
| incident_id | string | yes | – |
No output schema declared.
No examples provided.
intermediate_report ~96
Generate the 72h intermediate report for a MAJOR incident (ITS 2025/302). Must include action plan if incident is not yet resolved.
| Name | Type | Req | Description |
|---|---|---|---|
| action_plan | string | – | – |
| containment_actions | string | – | – |
| description_update | string | – | – |
| expected_resolution | string | – | – |
| incident_id | string | yes | – |
| recovery_status | string | – | – |
| root_cause | string | – | – |
No output schema declared.
No examples provided.
log_incident ~178
Log a new ICT-related incident. First step in the DORA incident management process (Art. 17).
| Name | Type | Req | Description |
|---|---|---|---|
| affected_services | string | – | – |
| affected_systems | string | – | – |
| bcm_activated | boolean | – | – |
| clients_affected | number | – | Percentage of clients affected |
| criticality_of_services | boolean | – | – |
| data_losses | boolean | – | – |
| description | string | – | – |
| detected_at | string | – | ISO datetime of detection |
| duration_hours | number | – | – |
| economic_impact_eur | number | – | – |
| geographic_spread | integer | – | – |
| incident_id | string | – | – |
| notes | string | – | – |
| owner | string | – | – |
| severity | string | – | – |
| team | string | – | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
major_incident_check ~90
Quick check: would these criteria values classify as a MAJOR incident? No incident record needed — use for pre-assessment.
| Name | Type | Req | Description |
|---|---|---|---|
| clients_affected | number | – | – |
| criticality_of_services | boolean | – | – |
| data_losses | boolean | – | – |
| duration_hours | number | – | – |
| economic_impact_eur | number | – | – |
| geographic_spread | integer | – | – |
No output schema declared.
No examples provided.
reclassify ~59
Reclassify an incident (MAJOR to NON-MAJOR or vice versa). Competent authority must be notified of reclassification.
| Name | Type | Req | Description |
|---|---|---|---|
| incident_id | string | yes | – |
| new_classification | string | yes | – |
| reason | string | – | – |
No output schema declared.
No examples provided.
How do I install the io.tooloracle/incidentoracle MCP server?
io.tooloracle/incidentoracle is a hosted endpoint at https://tooloracle.io/incident/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-incidentoracle 'https://tooloracle.io/incident/mcp/'
What is the io.tooloracle/incidentoracle MCP server?
io.tooloracle/incidentoracle is an MCP server listed in the public MCP registry as io.tooloracle/incidentoracle. IncidentOracle - 12-tool incident management MCP: triage, BaFin DORA reporting, RCA. This page covers its hosted endpoint (https://tooloracle.io/incident/mcp/).
Is the io.tooloracle/incidentoracle MCP server safe to use?
io.tooloracle/incidentoracle scores 24 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/incidentoracle MCP server expose?
io.tooloracle/incidentoracle exposes 12 tools: log_incident, classify_incident, major_incident_check, initial_notification, intermediate_report, and 7 more. Their descriptions and schemas cost roughly 968 tokens of context every time the server is loaded.
Does the io.tooloracle/incidentoracle MCP server require authentication?
Its publisher declares no required credentials for io.tooloracle/incidentoracle. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the io.tooloracle/incidentoracle MCP server still maintained?
io.tooloracle/incidentoracle is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the io.tooloracle/incidentoracle MCP server?
VerifyMCP ran 5 checks on io.tooloracle/incidentoracle, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about io.tooloracle/incidentoracle: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.