io.tooloracle/incidentoracle
REMOTE · TOOLORACLE.IO · SCANNED AUG 3
IncidentOracle - 12-tool incident management MCP: triage, BaFin DORA reporting, RCA.
Available components
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 12 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 Usability63
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 968 tokens (~80/item across 12 items; 12 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 Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 12% of tool parameters carry a description.Partial
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
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 mcp add --transport http io-tooloracle-incidentoracle https://tooloracle.io/incident/mcp/
[mcp_servers.io-tooloracle-incidentoracle] url = "https://tooloracle.io/incident/mcp/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-tooloracle-incidentoracle": {
"type": "remote",
"url": "https://tooloracle.io/incident/mcp/",
"enabled": true
}
}
} openclaw mcp add io-tooloracle-incidentoracle --url https://tooloracle.io/incident/mcp/ --transport streamable-http
mcp_servers:
io-tooloracle-incidentoracle:
url: "https://tooloracle.io/incident/mcp/" {
"mcpServers": {
"io-tooloracle-incidentoracle": {
"type": "http",
"url": "https://tooloracle.io/incident/mcp/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +3
- 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 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 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 +1
- 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 55
First indexed and scored.
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/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 | 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/incident/mcp/ | Verified | 200 | |
| 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.
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.