Faultline

io.fltln/faultlineVersion 2.0.0

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

Status

Responds458 msNov 14, 2026, 14:34 UTCAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.

Last checked: Nov 14, 2026, 14:34 UTC
Latency: 458 ms
Remotes responding: 1 of 1
Sign-in: API key
Hosting: Hosted outside the EU (detected)
Registry data as of: Nov 14, 2026, 22:14 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP

https://mcp.fltln.io/mcpResponds458 msNov 14, 2026, 14:34 UTC

No sign-in

Claude Code

claude mcp add --transport http faultline https://mcp.fltln.io/mcp --header 'X-API-Key: <YOUR_X_API_KEY>'

Replace <YOUR_X_API_KEY> before running.

Claude Desktop and claude.ai

Settings > Connectors > Add custom connector
Name: faultline
Remote MCP server URL: https://mcp.fltln.io/mcp
This server expects the header X-API-Key.

Cursor

{
  "mcpServers": {
    "faultline": {
      "url": "https://mcp.fltln.io/mcp",
      "headers": {
        "X-API-Key": "<YOUR_X_API_KEY>"
      }
    }
  }
}

Replace <YOUR_X_API_KEY> before running.

VS Code

code --add-mcp '{"name":"faultline","type":"http","url":"https://mcp.fltln.io/mcp","headers":{"X-API-Key":"<YOUR_X_API_KEY>"}}'

Replace <YOUR_X_API_KEY> before running.

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

10 tools

Tools of Faultline
	Description		Read-only	Idempotent	Open world
`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.	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.	No	No	Not declared	Not declared
`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 incident; then confirm with the user before calling run_runbook.	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 incident; then confirm with the user before calling run_runbook.	Not declared	Yes	Not declared	No
`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 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.	Not declared	Yes	Not declared	No
`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.	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.	Not declared	Yes	Not declared	No
`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 that have not yet tripped a hard up/down threshold.	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 that have not yet tripped a hard up/down threshold.	Not declared	Yes	Not declared	No
`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 incidents — open ones by default, or recently resolved with status='resolved'. Call this when asked about outages, what's broken, or incident history.	Not declared	Yes	Not declared	No
`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.	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.	Not declared	Yes	Not declared	No
`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.	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.	No	No	Not declared	Not declared
`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.	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.	Yes	No	Not declared	Not declared
`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.	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.	Not declared	Yes	Not declared	No

Details

Registry status: Active
Published: Jul 4, 2026
Updated: Jul 4, 2026
Website: Not given
Repository: https://github.com/fltln-io/faultline-mcp⁠ (opens in a new tab)
Categories (suggested): Cloud and infrastructureSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR: Not declared

Are you the operator? Claim this listing