Check infrastructure health, manage incidents, and run runbooks in Faultline.
Connect Remote server
claude mcp add --transport http faultline https://mcp.fltln.io/mcp --header "X-API-Key: <X_API_KEY>"
{
"mcpServers": {
"faultline": {
"url": "https://mcp.fltln.io/mcp",
"headers": {
"X-API-Key": "<X_API_KEY>"
}
}
}
}
{
"servers": {
"faultline": {
"type": "http",
"url": "https://mcp.fltln.io/mcp",
"headers": {
"X-API-Key": "<X_API_KEY>"
}
}
}
}
Settings > Connectors > Add custom connector
URL: https://mcp.fltln.io/mcp
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools 10 found in our last check
list_servicesList 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.
get_serviceGet 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_incidentsList incidents — open ones by default, or recently resolved with status='resolved'. Call this when asked about outages, what's broken, or incident history.
get_incidentGet 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.
acknowledge_incidentAcknowledge 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.
resolve_incidentMark 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.
who_is_on_callGet 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.
list_anomaliesList 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 d…
diagnose_incidentAnalyze 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…
run_runbookExecute 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.
Headers
| Name | Description |
|---|---|
X-API-KeyRequired, secret | Faultline API key (flt_...) from Settings → API Keys in the Faultline dashboard |
Details
| Endpoint | https://mcp.fltln.io/mcp (Streamable HTTP) |
| First published | 4 Jul 2026 |
| Last updated | 4 Jul 2026 |
| Registry name | io.fltln/faultline |
More other servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
