Back to Browse

Faultline MCP Server

Developer ToolsLow Risk9.9MCP RegistryRemote
Free

Server data from the Official MCP Registry

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

About

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

Remote endpoints: streamable-http: https://mcp.fltln.io/mcp

Security Report

9.9
Low Risk9.9Low Risk

Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry. 1 finding(s) downgraded by scanner intelligence.

Endpoint verified · Open access · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

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

Documentation

View on GitHub

From the project's GitHub README.

Faultline MCP Server

Faultline is infrastructure monitoring and incident management for DevOps/SRE teams. This repo documents faultline-mcp — Faultline's remote MCP server, which lets AI agents (Claude, Claude Code, Claude Desktop, or anything MCP-compatible) operate Faultline: check infrastructure health, inspect and act on incidents, look up who's on call, and run approved runbooks.

This repo is documentation only. The server is hosted by Faultline at https://mcp.fltln.io/mcp (Streamable HTTP transport) — there's nothing to install or run yourself.

Setup

  1. Create an API key in Faultline: Settings → API Keys. Keys look like flt_....
  2. Point your MCP client at https://mcp.fltln.io/mcp, sending the key as either X-API-Key: flt_... or Authorization: Bearer flt_....

Claude Code:

claude mcp add --transport http faultline-mcp https://mcp.fltln.io/mcp \
  --header "X-API-Key: flt_..."

Clients that take raw JSON config (Claude Desktop, etc.):

{
  "mcpServers": {
    "faultline": {
      "type": "http",
      "url": "https://mcp.fltln.io/mcp",
      "headers": { "X-API-Key": "flt_..." }
    }
  }
}

Tools

ToolWhat it does
list_servicesMonitor inventory with current status (optional status filter)
get_serviceOne service + its 10 most recent checks (for diagnosis)
list_incidentsOpen incidents (or status: "resolved" for history)
get_incidentFull incident record: timeline, AI summary, post-mortem
acknowledge_incidentAcknowledge an incident — stops further escalation
resolve_incidentResolve with an optional note (recorded on the timeline)
who_is_on_callCurrent on-call per schedule, with shift end time
list_anomaliesRecent learned-baseline latency anomalies (observed vs baseline, z-score, hours sustained, auto-opened incident if any)
diagnose_incidentRecommend the next action (run runbook / escalate / resolve / wait) + candidate runbooks. Analysis only — changes nothing
run_runbookExecute one chosen runbook against an incident — mutates infrastructure (can restart/scale services)

Security

  • Scoped to your API key. The server never stores your key — it's used only for the duration of each request, proxied straight through to Faultline's API.
  • Approval-gated mutation. run_runbook is the only tool that changes infrastructure. Its description instructs the calling agent to use it only after diagnose_incident recommended it and you've explicitly confirmed.
  • Tenant-isolated. Every request is scoped to the tenant that owns the API key — one key can never see or affect another tenant's data.

Support

Questions or issues: support@fltln.io or the Faultline dashboard.

Reviews

No reviews yet

Be the first to review this server!

Faultline MCP Server - Check infrastructure health, manage incidents, and run | MCP Marketplace