Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Faultline

by fltln-ioversion 2.0.0i★ –iRuns in the cloud
Registry nameio.fltln/faultline

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs in the cloud
  • Transport: Streamable HTTP
  • Category: Clinics & health
  • You need to fill in: X-API-Key

Install

Pick the AI app you use, then copy the settings.

Before you install

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Run this in your terminal

claude mcp add --transport http faultline https://mcp.fltln.io/mcp --header 'X-API-Key: your-value'

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "faultline": {
      "url": "https://mcp.fltln.io/mcp",
      "headers": {
        "X-API-Key": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • X-API-Key secret required HTTP header
    Faultline API key (flt_...) from Settings → API Keys in the Faultline dashboard

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified against the domain fltln.io (the registry checks domain ownership)

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • … Not checked yet

    Endpoint responds

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    Sign-in with OAuth

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Compared with others in Clinics & healthi

  • More stars than 0% of the other 871 servers in this category
  • Published to the registry more recently than 22% of the other 871 servers in this category
  • Basic checks equal to or better than 100% of the other 871 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Faultline safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: X-API-Key

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (2.0.0) reached the registry 4 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Mirobody, FHIR MCP Server, Google Health MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Mirobody

by thetahealth

Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.

Runs on your computer★ 1,408Apache-2.0Updated 6 days ago
Install

MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications

Runs on your computer★ 137Apache-2.0Updated 9 days ago
Install

Google Health MCP

by davidmosiah

Privacy-first unofficial Google Health API v4 MCP server for health, sleep, activity, HR agents

Runs on your computer★ 79MITUpdated 4 months ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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:

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_..." } } } }

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:

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: support@fltln.io or the Faultline dashboard.

Ask PopNx