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.
作者提供的原文
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 12/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
通过 3/3 项检查 · 在你的电脑上运行
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 Agent Chain Doctor MCP
Agent Chain Doctor MCP 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
A · 使用能连接 Agent Chain Doctor MCP 的应用
B · 诊所与健康 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
Claude Code 暂时无法连接 Agent Chain Doctor MCP
开发者只提供了电脑版 Claude 应用的安装文件
A · 使用能连接 Agent Chain Doctor MCP 的应用
Cursor 暂时无法连接 Agent Chain Doctor MCP
开发者只提供了电脑版 Claude 应用的安装文件
A · 使用能连接 Agent Chain Doctor MCP 的应用
VS Code 暂时无法连接 Agent Chain Doctor MCP
开发者只提供了电脑版 Claude 应用的安装文件
A · 使用能连接 Agent Chain Doctor MCP 的应用
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日
注册名称已通过 GitHub 账户 elfovo 验证,该账户拥有此仓库
代码最后更新于9天前
使用 MIT
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/elfovo-agent-chain-doctor-mcp)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于9天前,最新版本(1.4.0)于30天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 MCPB。
同一分类中有:Medplum MCP, Mirobody, Codescene MCP Server, Marrow, WHOOP — MissingMCP
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Securely access and manage FHIR healthcare data stored in Medplum.
Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.
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.
| 本项 Agent Chain Doctor MCP | Medplum MCP | Mirobody | Codescene MCP Server | Marrow | WHOOP — MissingMCP | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 需要安装在电脑上 | 需要安装在电脑上 | 需要安装在电脑上 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 3/3 | 4/4 | 3/3 | 2/3 | 3/3 | 2/4 |
| 许可证 | MIT | Apache-2.0 | Apache-2.0 | NOASSERTION | MIT | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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