bots.st/faultline
Faultline
Incident health checks and runbook execution
2523 ms
answered our call
- State
- Answered
- Protocol
- MCP 2025-06-18
- Tools listed
- 10
- Answered
- 3 of the last 3 calls
How to reach it
- MCP, HTTP
https://mcp.fltln.io/mcpNeeds header X-API-Key
What it can do
| Tool | What it says it does |
|---|---|
acknowledge_incident | Acknowledge an open incident, stopping further escalation. Call this when the user says they are looking into an incident or asks you to take ownership of it. |
diagnose_incident | Analyze an open incident and recommend the next action: run a specific runbook, escalate to a human, resolve, or wait. Returns the recommendation (with rationale and confidence) and the candidate runbooks. This is analysis ONLY — it does not change anything. Call this to decide what to do about an… |
get_incident | Get an incident's full record: timeline of every update, escalations, runbook results, AI summary, and post-mortem if drafted. Call this before acting on an incident. |
get_service | Get one service's details including its 10 most recent health checks (status codes, latency, errors). Call this when diagnosing WHY a service is degraded or down. |
list_anomalies | List recent learned-baseline latency anomalies: observed vs baseline response time, the deviation z-score, how many consecutive hours it has been sustained, and the incident it auto-opened (if any). Call this when asked why a service is slow, about latency spikes, or for early degradation signals… |
list_incidents | List incidents — open ones by default, or recently resolved with status='resolved'. Call this when asked about outages, what's broken, or incident history. |
list_services | List all monitored services with their current status (OK, DEGRADED, DOWN, PAUSED, PENDING). Call this first to get an overview of infrastructure health, or to find a service's ID. |
resolve_incident | Mark an incident as resolved, with an optional note describing the fix. Only call this when the user confirms the underlying issue is fixed — resolving is a status-page-visible action. |
run_runbook | Execute one specific runbook against an incident. This MUTATES INFRASTRUCTURE (it can restart or scale services). Only call after diagnose_incident recommended it AND the user has confirmed. Pass the runbookId from the diagnosis's recommendation or candidate list. |
who_is_on_call | Get the person currently on call for each on-call schedule, and when their shift ends. Call this when deciding who to contact about an incident. |
In its maker's words
Check infrastructure health, manage incidents, and run runbooks in Faultline.
- Source
- github.com/fltln-io/faultline-mcp
- Publisher
- fltln.io
- Listed from
- the official MCP Registry as
io.fltln/faultline - Version
- 2.0.0, updated 4 Jul 2026
- Kinds of work
- cloud-and-devops, messaging-and-support, security-and-trust
The domain it lives on
- fltln.io
- registered 19 Apr 2026 (7 months ago), at NameCheap, Inc., its home page is a working site
From our own crawl of domain names: registry records and the home page as our crawler last saw it.
Every call we made
| When | What happened | Time |
|---|---|---|
| Answered | 2523 ms | |
| Answered | 2571 ms | |
| Answered | 1105 ms |
Next door
Is this your bot? Claim its address to add a verified badge and keep the listing current.