Mirobody
Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.
Description from the maker (original English)
Check infrastructure health, manage incidents, and run runbooks in Faultline.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
X-API-KeyValues 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.
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.
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.
X-API-Key secret required HTTP headerThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
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
The registry name was verified against the domain fltln.io (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
You need to fill in: X-API-Key
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.
The GitHub repo last changed –, and the latest version (2.0.0) reached the registry 4 months ago.
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.
In the same category: Mirobody, FHIR MCP Server, Google Health MCP
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
Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.
MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications
Privacy-first unofficial Google Health API v4 MCP server for health, sleep, activity, HR agents
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 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.
flt_....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_..." } } } }
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.
skills/faultline/SKILL.md is an Agent Skill that teaches Claude how to use these tools well:
diagnose_incident returned for that incident.Install it alongside the MCP server:
skills/faultline folder into ~/.claude/skills/ (all projects) or .claude/skills/ (one project).faultline folder and upload it under Settings → Capabilities → Skills.| Tool | What it does |
|---|---|
list_services | Monitor inventory with current status (optional status filter) |
get_service | One service + its 10 most recent checks (for diagnosis) |
list_incidents | Open incidents (or status: "resolved" for history) |
get_incident | Full incident record: timeline, AI summary, post-mortem |
acknowledge_incident | Acknowledge an incident, which stops further escalation |
resolve_incident | Resolve with an optional note (recorded on the timeline and visible on your status page) |
who_is_on_call | Current on-call per schedule, with shift end time |
list_anomalies | Recent learned-baseline latency anomalies (observed vs baseline, z-score, hours sustained, auto-opened incident if any) |
diagnose_incident | Recommend the next action (run runbook / escalate / resolve / wait) + candidate runbooks. Analysis only; changes nothing |
run_runbook | Execute one chosen runbook against an incident. Mutates infrastructure (can restart/scale services) |
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.Questions or issues: support@fltln.io or the Faultline dashboard.