# Fltln Faultline MCP server

Source: https://glimind.com/server/mcp-registry%2Fio.fltln%2Ffaultline
Registry id: `mcp-registry/io.fltln/faultline`
Status: live (checked 2026-11-22T16:11:06.153Z)

## Measurements (30 days)

- Uptime: 99.97%
- Checks: 3955
- Outages (90 days): 1

## Install

```json
{
  "mcpServers": {
    "fltln-faultline-mcp-server": {
      "type": "http",
      "url": "https://mcp.fltln.io/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http fltln-faultline-mcp-server https://mcp.fltln.io/mcp
```

## Tools (10)

- `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 rational
- `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 inc
- `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 dow
- `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
- `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 
- `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 sta
- `run_runbook`: Execute one specific runbook against an incident. This MUTATES INFRASTRUCTURE (it can restart or scale services). Only call after diagnose_incident recommended 
- `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.

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
