Faultline
Check infrastructure health, manage incidents, and run runbooks in Faultline
Reviews
No review yet. Used Faultline? Be the first to help others choose.What it does
Faultline is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
No capability identified yet from its description.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 10h ago (live check)Hosted endpoint
https://mcp.fltln.io/mcpstreamable-http
Required: X-API-Key (get it from the publisher)
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"faultline": {
"url": "https://mcp.fltln.io/mcp",
"headers": {
"X-API-Key": "<your X-API-Key>"
}
}
}
}Replace the values in <angle brackets>.
Live check
Electra Index connected to the hosted endpoint 10h agoONLINE Faultline answered an MCP connection on 17 Nov 2026 and introduced itself as faultline 0.1.0 (MCP protocol 2025-06-18).
10 tools offered to AI assistants
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 slodiagnose_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 norun_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 recommend
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Hosted endpoint | https://mcp.fltln.io/mcp | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Repository | https://github.com/fltln-io/faultline-mcp | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Version | 2.0.0 | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
Change history
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is Faultline still online?
Free alerts · no account▲ 0Do you run Faultline? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about Faultline
How do I connect Faultline?
Use the hosted endpoint https://mcp.fltln.io/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
Does Faultline need an API key or token?
Yes. The registry entry lists a required value: X-API-Key. Get it from the publisher.
What tools does Faultline offer?
When Electra Index connected on 17 Nov 2026, it listed 10 tools: list_services, get_service, list_incidents, get_incident, acknowledge_incident, resolve_incident, who_is_on_call, list_anomalies and more. The full list is in "Live check" above.
Is Faultline online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 10h ago.