io.fltln/faultline

up checked 2026-11-11T04:39:13.610Z

Unclaimed · Unverified

Agent searches it appeared in, last 30 days: 0. Run this server? Claim the listing: verified label, uptime alerts and analytics.

Publisher-provided title

Faultline

Publisher-provided description

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

Summary by lookupd

Lets an agent check service health, list and manage incidents, run runbooks, and see on-call contacts.

Install

Claude Code, remote (streamable-http)

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

Codex, remote (streamable-http)

codex mcp add faultline --url https://mcp.fltln.io/mcp

Cursor, remote (streamable-http) → .cursor/mcp.json

{
  "mcpServers": {
    "faultline": {
      "url": "https://mcp.fltln.io/mcp"
    }
  }
}

Other clients: docs. Or tell your agent: Set up lookupd for me: read https://lookupd.com/agent.md and follow it.

Tools (10 tools)

Publisher-provided text

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

Details

• Version: 2.0.0
• Transports: streamable-http
• Uptime (7 days): 100%
• Median latency: 326 ms
• First indexed: 2026-11-01T09:03:05.406Z
• Last seen in registry: 2026-11-01T09:03:05.406Z
• Repository: https://github.com/fltln-io/faultline-mcp

Badge for your README

Shows this live status and links here; updates hourly.

[![lookupd status](https://lookupd.com/badge/io.fltln/faultline.svg)](https://lookupd.com/servers/io.fltln/faultline)

• 62033 servers
• Last crawl: 2026-11-11T15:38:39.561Z
• API base: https://api.lookupd.com
• MCP URL: https://api.lookupd.com/mcp