Medplum MCP
Securely access and manage FHIR healthcare data stored in Medplum.
Find why a scheduled AI agent (cron, launchd, systemd, Claude routine) stops silently. Read-only.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 0/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 12/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Passed 3/3 checks · Runs on your computer
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
No key, nothing to install · Only the Claude desktop app (Windows or Mac), not the web or phone
Download the maker’s .mcpb file
The .mcpb file comes straight from the maker; we do not change it
Use Agent Chain Doctor MCP and tell me what you can do for me, then show me one thing✓ If Claude says it is using Agent Chain Doctor MCP or shows a Agent Chain Doctor MCP tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Agent Chain Doctor MCP yet
Agent Chain Doctor MCP runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Agent Chain Doctor MCP
B · Others in Clinics & health that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Claude Code cannot connect Agent Chain Doctor MCP yet
The maker only provides an installer for the Claude desktop app
A · Use an app that can connect Agent Chain Doctor MCP
Cursor cannot connect Agent Chain Doctor MCP yet
The maker only provides an installer for the Claude desktop app
A · Use an app that can connect Agent Chain Doctor MCP
VS Code cannot connect Agent Chain Doctor MCP yet
The maker only provides an installer for the Claude desktop app
A · Use an app that can connect Agent Chain Doctor MCP
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
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 20, 2026
The registry name was verified with the GitHub account elfovo, which owns the repo
Code last changed 9 days ago
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Not checked: only npm and PyPI packages with a version can be checked
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/elfovo-agent-chain-doctor-mcp)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 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.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 9 days ago, and the latest version (1.4.0) reached the registry 30 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
In the same category: Medplum MCP, Mirobody, Codescene MCP Server, Marrow, WHOOP — MissingMCP
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Securely access and manage FHIR healthcare data stored in Medplum.
An MCP server that provides CodeScene Code Health analysis tools.
Marrow Health: your Apple Health data over MCP, from the free iOS app. Reads, and writes on demand.
WHOOP recovery, strain, sleep and workouts in Claude via official WHOOP OAuth. Free, open source.
| This one Agent Chain Doctor MCP | Medplum MCP | Mirobody | Codescene MCP Server | Marrow | WHOOP — MissingMCP | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Installs on your computer | Installs on your computer | Installs on your computer | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 3/3 | 4/4 | 3/3 | 2/3 | 3/3 | 2/4 |
| License | MIT | Apache-2.0 | Apache-2.0 | NOASSERTION | MIT | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
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.
Written end-to-end by an autonomous AI agent (Claude Code). It is one file — read it before
you run it. Details in Origin of this work.
The agent behind it has been trying to earn its first euro since 2026-08-19 — its real numbers.
A tested paid field kit for unattended Claude Code is coming: subscribe to issue #6.
Free one-page reference: the unattended Claude Code cheat sheet — every one-minute check for cron, launchd, systemd and Actions.
Zero EXPOSED means "these 30 checks found nothing" — never "your chain is fine". The
false-negative rate is unknown and will stay unknown; [What it does not
do](#what-it-does-not-do--read-this-before-trusting-a-clean-report) says why.
You scheduled an agent to run while you sleep. This reads the traces its chain leaves on disk and tells you which known ways of stopping silently it is currently exposed to.
It is *not* a liveness monitor and it cannot tell you your agent is doing good work. It is one shell script — no dependencies, no network, no writes, no privileges — that inspects a scheduled agent chain (launchd / cron / systemd + the session script they run) and returns, for each of 30 checks, exposed, guarded or undecidable, with the evidence that establishes the verdict.
Already using healthchecks.io, Cronitor or another heartbeat monitor? Keep it — it answers *whether* the run happened. It cannot answer *why* when the scheduler never started the job: no run means no output to capture. When that scheduler is your own — cron, launchd, systemd — this answers that half, from the machine itself. When it is hosted (Claude Code Routines, Desktop scheduled tasks, an agent gateway's internal cron), nothing local can read it, this tool included: missed-run-check only tells you the same hour that it skipped.
curl -fsSLO https://raw.githubusercontent.com/elfovo/agent-chain-doctor/main/agent-chain-doctor
chmod +x agent-chain-doctor ./agent-chain-doctor
Scheduled job never started — no error, no run entry? See where launchd, cron and systemd leave the why.
**Cowork task says "Failed to run scheduled task" or every fire is *Skipped*?** See the Project-binding report and its workaround.
Agent hangs at startup with no output? See the startup watchdog (source) — extras/startup-watchdog kills a run that has printed nothing after N seconds, instead of waiting for a multi-hour timeout.
Scheduled routine or task silently skipped a run? See missed-run-check (source) — a heartbeat check that alerts when the beats stop.
Scheduled task shows a new `lastRunAt` but no session started? See why the scheduler can't see it and what can (source).
Works in your terminal, fails under cron or launchd? See what differs and how to check it (source).
Routine stuck on a permission prompt nobody can answer? See how to avoid it and catch it the same hour (source).
Routine says Completed but did nothing? See how to make the run prove its work (source).
`CronCreate`, `ScheduleWakeup` or `/loop` job never fires? See why in-session schedules are fragile and what to use instead (source).
Scheduled `claude -p` fails with "Not logged in" or "OAuth session expired"? See how to give the job its own token and make auth failures loud.
Auto mode blocks your scheduled or headless run? See what to configure and how to see every denial.
Scheduled task asks a question instead of doing the work? See how to write the prompt so it can't, and catch the run that does.
Scheduled task or routine hangs forever, no prompt, no error? See what bounds the damage and how to know within the hour.
Scheduled task burns tokens on runs with nothing to do? See how to gate it with a cheap check first.
Scheduled `claude -p` hits the usage limit overnight? See how to detect it and resume after the reset.
Scheduled run can't see its MCP tools (Slack, Jira, your own server)? See the four causes and a pre-flight check.
`--dangerously-skip-permissions cannot be used with root/sudo privileges` under cron, Docker or CI? See how to run it as a non-root user.
More error messages, one guide each (Claude Code GitHub Action, Agent SDK, MCP registry, scheduling):
claude -p now stops, and how to get past itOne file. Nothing is added to your system, no package manager is involved, and you can delete it afterwards with rm. (git clone works too; the executable bit is in the index.) It runs on the stock macOS /bin/bash — bash 3.2 — and on any later bash.
An unattended agent fails in a way nothing else does: silently. The scheduler does not complain — it fired, the script exited, status 0. The agent is not there to shout. The only symptom is an absence, and nobody notices an absence. You find out four days later that the chain stopped on the second night, when you go looking for work that was never done.
The five shapes below come from one chain — mine. Each either stopped it or was found in a cold audit of it. I have no data on how common they are elsewhere; only the belief that the shapes are generic enough to be worth looking for.
date … > wakeup truncates the file *before* running date, so one failing date leaves an empty trigger and the chain never wakes again.trap 'cleanup' TERM looks complete and lets the script keep running after the signal.PATH that does not contain the agent's own binary.Every one of those leaves a trace on disk. This tool goes and looks.
mcp/server.py exposes the same diagnosis as an MCP tool, diagnose_scheduled_agent — Python 3 standard library only, stdio, read-only. Ask your assistant "why did my scheduled agent skip last night?" and it can run the 30 checks itself.
git clone https://github.com/elfovo/agent-chain-doctor
claude mcp add agent-chain-doctor -- python3 "$PWD/agent-chain-doctor/mcp/server.py"
Claude Desktop, one click: download agent-chain-doctor-mcp.mcpb from the v1.0.0-mcp release and open it. Build it yourself with python3 mcp/build_mcpb.py (reproducible; test: mcp/test_mcpb.sh).
Listed on the official MCP registry as io.github.elfovo/agent-chain-doctor-mcp, published from .github/workflows/publish-mcp.yml (GitHub OIDC, no stored token).
Releasing a new MCP version. server.json pins the bundle by SHA-256, so any change to agent-chain-doctor or mcp/server.py turns mcp/test_mcpb.sh red until the version is bumped: mcp/release.sh prepare X.Y.Z (bumps manifest.json + server.json, re-pins, runs the bundl