Model Context Protocol server for Rollbar
Nothing to run from here
Incidentoracle is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
12
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
IncidentOracle - 12-tool incident management MCP: triage, BaFin DORA reporting, RCA.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http incidentoracle-mcp https://tooloracle.io/incident/mcp/
# 2 — ask your agent for something these tools do
# log_incident, classify_incident, major_incident_check and 9 more
Incidentoracle costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
TOAll 61 servers
tooloracle61 servers
14 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http incidentoracle-mcp https://tooloracle.io/incident/mcp/Reconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
12 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Log a new ICT-related incident. First step in the DORA incident management process (Art. 17).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| incident_id | string | no | — |
| title | string | yes | — |
| description | string | no | — |
| severity | string | no | — |
| detected_at | string | no | ISO datetime of detection |
| affected_systems | string | no | — |
| affected_services | string | no | — |
| owner | string | no | — |
| team | string | no | — |
| bcm_activated | boolean | no | — |
| clients_affected | number | no | Percentage of clients affected |
| duration_hours | number | no | — |
| geographic_spread | integer | no | — |
| data_losses | boolean | no | — |
| economic_impact_eur | number | no | — |
| criticality_of_services | boolean | no | — |
| notes | string | no | — |
Classify an incident against the 6 DORA criteria (RTS 2024/1772). Determines if MAJOR (triggers 4h/72h/1m reporting) or NON-MAJOR.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| incident_id | string | yes | — |
| clients_affected | number | no | % of clients affected |
| duration_hours | number | no | — |
| geographic_spread | integer | no | Number of EU member states |
| data_losses | boolean | no | Confidential/personal data affected? |
| economic_impact_eur | number | no | — |
| criticality_of_services | boolean | no | Critical functions affected? |
Quick check: would these criteria values classify as a MAJOR incident? No incident record needed — use for pre-assessment.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| clients_affected | number | no | — |
| duration_hours | number | no | — |
| geographic_spread | integer | no | — |
| data_losses | boolean | no | — |
| economic_impact_eur | number | no | — |
| criticality_of_services | boolean | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| incident_id | string | yes | — |
| entity_name | string | no | — |
| entity_lei | string | no | — |
| authority | string | no | Competent authority (e.g., BaFin, FMA) |
| affected_states | string | no | Comma-separated EU member states |
| discovery_method | string | no | — |
Generate the 72h intermediate report for a MAJOR incident (ITS 2025/302). Must include action plan if incident is not yet resolved.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| incident_id | string | yes | — |
| description_update | string | no | — |
| root_cause | string | no | — |
| containment_actions | string | no | — |
| recovery_status | string | no | — |
| action_plan | string | no | — |
| expected_resolution | string | no | — |
Generate the 1-month final report with root cause analysis and lessons learned.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| incident_id | string | yes | — |
| root_cause_final | string | no | — |
| recovery_actions | string | no | — |
| lessons_learned | string | no | — |
| preventive_measures | string | no | — |
| client_communication | string | no | — |
| total_cost_eur | number | no | — |
| resolved_at | string | no | — |
Track all active MAJOR incident reporting deadlines. Shows overdue and upcoming.
No parameter schema on file.
Reclassify an incident (MAJOR to NON-MAJOR or vice versa). Competent authority must be notified of reclassification.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| incident_id | string | yes | — |
| new_classification | string | yes | — |
| reason | string | no | — |
Dashboard: total/open/major incidents, overdue deadlines, by severity/status.
No parameter schema on file.
Voluntary notification of a significant cyber threat (Art. 19(2)). Uses ITS 2025/302 Annex III template.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| title | string | yes | — |
| description | string | no | — |
| threat_type | string | no | — |
| iocs | string | no | — |
| ttps | string | no | — |
| affected_systems | string | no | — |
| mitigation | string | no | — |
| source | string | no | — |
Full incident register with filters (status, classification, severity, search).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | — |
| classification | string | no | — |
| severity | string | no | — |
| search | string | no | — |
Server status.
No parameter schema on file.
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Incidentoracle or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Incidentoracle can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.