NestDaddy

Faultline

io.fltln/faultline · v2.0.0

Check infrastructure health, manage incidents, and run runbooks in Faultline.

Connect Remote server

Terminal
claude mcp add --transport http faultline https://mcp.fltln.io/mcp --header "X-API-Key: <X_API_KEY>"
~/.cursor/mcp.json
{
  "mcpServers": {
    "faultline": {
      "url": "https://mcp.fltln.io/mcp",
      "headers": {
        "X-API-Key": "<X_API_KEY>"
      }
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "faultline": {
      "type": "http",
      "url": "https://mcp.fltln.io/mcp",
      "headers": {
        "X-API-Key": "<X_API_KEY>"
      }
    }
  }
}
Claude Desktop
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_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.

  • 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_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.

  • 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.

  • 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.

  • 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.

  • 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.

  • 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 d…

  • 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…

  • 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.

Headers

NameDescription
X-API-Key
Required, secret
Faultline API key (flt_...) from Settings → API Keys in the Faultline dashboard

Details

Endpointhttps://mcp.fltln.io/mcp (Streamable HTTP)
First published4 Jul 2026
Last updated4 Jul 2026
Registry nameio.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.