# io.tooloracle/incidentoracle (remote · tooloracle.io)

IncidentOracle - 12-tool incident management MCP: triage, BaFin DORA reporting, RCA.

- Trust score: 63/100 (medium)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-04

## Components

- remote · `tooloracle.io`: 63/100 (this document), [markdown](https://verifymcp.io/servers/io-tooloracle-incidentoracle/incident-mcp.md), [page](https://verifymcp.io/servers/io-tooloracle-incidentoracle/incident-mcp)

## Channel facts

- Endpoint: `https://tooloracle.io/incident/mcp/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-04.

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 968 tokens (~80/item across 12 items; 12 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 12% of tool parameters carry a description.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http io-tooloracle-incidentoracle https://tooloracle.io/incident/mcp/
```

### Codex

```toml
[mcp_servers.io-tooloracle-incidentoracle]
url = "https://tooloracle.io/incident/mcp/"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add io-tooloracle-incidentoracle --url https://tooloracle.io/incident/mcp/ --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-tooloracle-incidentoracle:
    url: "https://tooloracle.io/incident/mcp/"
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-04 (score 63, +1)

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

### 2026-08-02 (score 62, +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.

### 2026-07-31 (score 61, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 58, +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.

### 2026-07-28 (score 57, +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.

### 2026-07-27 (score 56, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 55)

First indexed and scored.

## MCP tools (12)

### `log_incident` (~178 tokens)

Log a new ICT-related incident. First step in the DORA incident management process (Art. 17).

Input parameters:

- `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, required)

### `classify_incident` (~133 tokens)

Classify an incident against the 6 DORA criteria (RTS 2024/1772). Determines if MAJOR (triggers 4h/72h/1m reporting) or NON-MAJOR.

Input parameters:

- `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, required)

### `major_incident_check` (~90 tokens)

Quick check: would these criteria values classify as a MAJOR incident? No incident record needed — use for pre-assessment.

Input parameters:

- `clients_affected` (number)
- `criticality_of_services` (boolean)
- `data_losses` (boolean)
- `duration_hours` (number)
- `economic_impact_eur` (number)
- `geographic_spread` (integer)

### `initial_notification` (~113 tokens)

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.

Input parameters:

- `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, required)

### `intermediate_report` (~96 tokens)

Generate the 72h intermediate report for a MAJOR incident (ITS 2025/302). Must include action plan if incident is not yet resolved.

Input parameters:

- `action_plan` (string)
- `containment_actions` (string)
- `description_update` (string)
- `expected_resolution` (string)
- `incident_id` (string, required)
- `recovery_status` (string)
- `root_cause` (string)

### `final_report` (~95 tokens)

Generate the 1-month final report with root cause analysis and lessons learned.

Input parameters:

- `client_communication` (string)
- `incident_id` (string, required)
- `lessons_learned` (string)
- `preventive_measures` (string)
- `recovery_actions` (string)
- `resolved_at` (string)
- `root_cause_final` (string)
- `total_cost_eur` (number)

### `deadline_tracker` (~22 tokens)

Track all active MAJOR incident reporting deadlines. Shows overdue and upcoming.

### `reclassify` (~59 tokens)

Reclassify an incident (MAJOR to NON-MAJOR or vice versa). Competent authority must be notified of reclassification.

Input parameters:

- `incident_id` (string, required)
- `new_classification` (string, required)
- `reason` (string)

### `incident_stats` (~23 tokens)

Dashboard: total/open/major incidents, overdue deadlines, by severity/status.

### `cyber_threat_notify` (~98 tokens)

Voluntary notification of a significant cyber threat (Art. 19(2)). Uses ITS 2025/302 Annex III template.

Input parameters:

- `affected_systems` (string)
- `description` (string)
- `iocs` (string)
- `mitigation` (string)
- `source` (string)
- `threat_type` (string)
- `title` (string, required)
- `ttps` (string)

### `incident_log` (~50 tokens)

Full incident register with filters (status, classification, severity, search).

Input parameters:

- `classification` (string)
- `search` (string)
- `severity` (string)
- `status` (string)

### `health_check` (~11 tokens)

Server status.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-tooloracle-incidentoracle/incident-mcp#diagnostics

## Score history

- 2026-08-04: 63
- 2026-08-03: 62
- 2026-08-02: 62
- 2026-08-01: 61
- 2026-07-31: 61
- 2026-07-30: 58
- 2026-07-29: 57
- 2026-07-28: 57
- 2026-07-27: 56
- 2026-07-26: 55

## Links

- Remote endpoint: https://tooloracle.io/incident/mcp/
- Repository: https://github.com/ToolOracle/incidentoracle
- Changelog RSS feed: https://verifymcp.io/servers/io-tooloracle-incidentoracle/incident-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-tooloracle-incidentoracle/incident-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/io-tooloracle-incidentoracle/incident-mcp