Faultline

io.fltln由 fltln.io 發布官方發布者v2.0.0更新於 Nov 3, 2026

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

已驗證Streamable HTTP可網頁執行雲端與基礎設施安全與監控

概覽

AI 產生的概覽

Faultline 的託管 MCP 伺服器，讓助理檢查基礎設施健康狀態、處理事件、查詢值班人員並執行已核准的 runbook。

可以做什麼
  • 列出服務清單，並檢視單一服務及其最近的檢查紀錄
  • 列出並檢視事件，包含時間軸、AI 摘要與事後檢討
  • 確認或解決事件，可附上備註
  • 依排班查詢目前值班人員，並列出以學習基準偵測到的延遲異常
  • 取得針對某事件的建議下一步動作與候選 runbook
  • 對某事件執行選定的 runbook
適用情境
適合已使用 Faultline 的 DevOps/SRE 團隊，讓助理提供健康總覽、說明服務為何變慢、進行事件分流與處置，並回答值班相關問題，不必切換工具。
執行需求
遠端 Streamable HTTP 端點，無需在本機安裝。需要 Faultline 帳號，並在 Settings → API Keys 建立 API 金鑰，透過 X-API-Key 標頭（或 Bearer 權杖）送出。工具探索不需金鑰，但每次工具呼叫都需要。
安裝前請注意
此 API 金鑰可存取你所屬租戶的監控與事件資料，應視為機密。run_runbook 會變更基礎設施，可能重新啟動或擴縮服務；確認與解決事件同樣會改變狀態，並可能顯示在狀態頁面。README 表示伺服器不儲存金鑰、每次請求即時轉送，且變更操作應等待明確確認。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Faultline，將其新增到工作區。
  2. 連接 X-API-Key 憑證。它們會被私密儲存，絕不會在公開頁面上展示。
  3. 為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.fltln%2Ffaultline/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

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

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 plus an Agent Skill. The server is hosted by Faultline at https://mcp.fltln.io/mcp (Streamable HTTP transport), so 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:

bash
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.):

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

Discovery without a key

You can browse the toolset before creating a key. The MCP discovery methods initialize, notifications/initialized, and tools/list work without an API key, so connector directories, registry scanners, and curious humans can see every tool's name, description, input schema, and annotations:

bash
curl -s https://mcp.fltln.io/mcp \  -H "Content-Type: application/json" \  -H "Accept: application/json, text/event-stream" \  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Anything else, including every tools/call, needs a key and returns 401 without one.

Agent Skill

skills/faultline/SKILL.md is an Agent Skill that teaches Claude how to use these tools well:

  • Workflows: which tools to call for a health overview, "why is X slow?", incident triage and remediation, and on-call lookups.
  • Approval rules: read-only tools run freely; acknowledging, resolving, and running runbooks wait for your explicit go-ahead, and Claude only runs a runbook that diagnose_incident returned for that incident.

Install it alongside the MCP server:

  • Claude Code: copy the skills/faultline folder into ~/.claude/skills/ (all projects) or .claude/skills/ (one project).
  • Claude.ai / Claude Desktop: zip the faultline folder and upload it under Settings → Capabilities → Skills.

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, which stops further escalation
resolve_incidentResolve with an optional note (recorded on the timeline and visible on your status page)
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.
  • Keyless means read-only metadata. Requests without a key can only list the static tool definitions. They never reach Faultline's API and can't read or change any tenant data.
  • Approval-gated mutation. run_runbook is the only tool that changes infrastructure. Its description, and the Agent Skill, instruct 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, so one key can never see or affect another tenant's data.

Support

Questions or issues: [email protected] or the Faultline dashboard.

[MCP Badge]

來源：README.md，提交 e4eb376

工具

10

list_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.

輸入參數status

get_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.

輸入參數serviceId必填

list_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.

輸入參數status

get_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.

輸入參數incidentId必填

acknowledge_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.

輸入參數incidentId必填

resolve_incident

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.

輸入參數noteincidentId必填

who_is_on_call

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 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_incident

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.

輸入參數incidentId必填

run_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.

輸入參數runbookId必填incidentId必填

版本歷史

1
  1. v2.0.0最新Sep 16, 2026

評分

已滿足適用檢查項的 90%

該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

    請在儲存庫或註冊中心條目中宣告授權條款。