get_incident

shallow

sh.fettle/mcp · Verify this server

Return one incident: id, monitor_id or heartbeat_id (exactly one is set), started_at, resolved_at, cause, cause_detail, last_notified_at, acknowledged_at, acknowledged_by, renotify_count and notification_logs (the alert attempts: each with id, channel_type, destination, event TRIGGERED, RESOLVED or SSL_EXPIRY, sent_at, status PENDING, SENT or FAILED, and error). destination is an email address, a Telegram chat id, or for a webhook only scheme://host/… (the full URL is never returned). incident_id (uuid, required) is the incident's id from list_incidents; an id that is not an incident of this organization is a 404.

100.0/100

1 trials · measured today

get_incident scores 100.0/100 on Vouch's measured behaviour index, from 1 real invocation trials against sh.fettle/mcp, measured 20 Oct 2026 under methodology v0.2.0. Every measured component scored 100.

Component breakdown

ComponentWeightValue
Reliability35%not applicable
Schema integrity25%100.0
Failure behaviour15%not applicable
Latency15%not applicable
Concurrency10%not applicable

Tool details

Transport
remote + stdio
Credential class
gated
Category
Developer infrastructure
Input schema
not declared
Output schema
not declared
Side-effect classification
unclassified

Score history

DayScoreTierMethodology
2026-10-20100.0shallowv0.2.0

Probe evidence

ProbeOutcomes
schema_integritypass: 1

Raw request/response logs are not archived yet — the outcome counts above are drawn directly from every recorded trial.

Embed this score

Available for every tool, scored or not — not a verification perk. Always links back to this page.

Vouch score: get_incident
[![Vouch score](https://vouch.tools/api/tools/3d76e474-2e55-480c-881a-980f743a2d09/badge.svg)](https://vouch.tools/tools/3d76e474-2e55-480c-881a-980f743a2d09)
get_incident — Vouch