mcpbeat Sign in

Faultline MCP Server

by fltln Your server? Claim it
answering

Faultline is answering right now. Last checked 13 min ago. It exposes 10 tools. Last commit 1 Nov 2026.

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

Uptime history 91 days of history · worst day 0%
91 days agonow
100.0%
Uptime 24h
91 of 91 checks
10
Tools
read from the server
521 ms
Response time
average over 24h
0
Stars
last commit 1 Nov 2026

Nothing serious here today

Today is the operative word: we check Faultline every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

run in your terminal
claude mcp add faultline --transport http https://mcp.fltln.io/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mcp.fltln.io/mcp
~/.codex/config.toml
[mcp_servers.faultline]
url = "https://mcp.fltln.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "faultline": {
      "url": "https://mcp.fltln.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "faultline": {
      "type": "http",
      "url": "https://mcp.fltln.io/mcp"
    }
  }
}

Available tools 10

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

acknowledge
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.
anomalies
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.
diagnose
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.
incident
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.
incidents
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.
resolve
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.
runbook
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.
service
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.
services
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.
who
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.

Endpoints

URLTransportStateLatencyChecked
https://mcp.fltln.io/mcp streamable-http answering 517 ms 13 min ago

Alternatives to Faultline

same job, measured the same way
Uptimebolt MCP Server
by clm-cloud-solutions

AI-powered infrastructure monitoring — health, incidents, predictions, RCA, deploy safety

62 installs/wk local only
H
Human Task Desk — Ron Long
by chatgpt-rlong33-ron-human-task-desk

Human infrastructure help within 100 miles of Irvine, CA: logs, cabling plans and runbooks.

3 tools answering
Datadog
by mcparmory

Monitor infrastructure, manage agents and deployments, track metrics, logs, and events

237 installs/wk local only
Cronalert
by jaredhobbs

Manage CronAlert uptime monitors, check results, and incidents from any MCP client.

87 installs/wk local only
HostTracker
by hosttracker

Website uptime monitoring: run checks from 300+ locations, manage monitors, alerts and incidents

65 tools answering
DebugBundle
by debugbundle

DebugBundle MCP: runtime error reporting, incident response, health checks, and product analytics.

2 395 installs/wk local only
Runframe MCP Server
by runframe

MCP server for Runframe incident management covering incidents, on-call, postmortems, and more.

66 installs/wk local only
Drumbeats Io
by drumbeats-io

Manage Drumbeats cron, heartbeat and uptime monitors, report job runs and handle incidents.

110 installs/wk answering

Faultline — questions

Answers built from our own checks of this server.

What can Faultline do?
It exposes 10 tools, read directly from the server on our last check. Among them: acknowledge_incident, diagnose_incident, get_incident, get_service, list_anomalies, list_incidents and 4 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Faultline working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 521 ms. The bar chart above shows every period we have measured.
How do I connect Faultline?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Faultline need an API key?
No. Faultline completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 10 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Faultline?
It answers our handshake in 521 ms on average, which is faster than 22% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Faultline open source?
We cannot say either way: 0 stars on GitHub, but we could not determine the licence, and without one the code is not open source by default.