Medplum MCP
Securely access and manage FHIR healthcare data stored in Medplum.
Test healthcare AI agents' medication claims against cited FDA label text. Not for clinical use.
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 11/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 8/8 | 上次检查时云端端点有响应 |
| 使用分 | 31/100 |
质量: 基础检查通过 5/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Orinyx。按照 https://mcp.popnx.com/i/lexthirteen-ai-orinyx-mcp.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 5/5 项检查 · 你的提问会经过开发者的服务器(orinyx-mcp.fly.dev) · ✓ 命令已检查 2026年11月13日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Orinyxhttps://orinyx-mcp.fly.dev/mcp在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsOrinyx
用 Orinyx 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Orinyx,或回答中出现 Orinyx 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
Plugins+Add custom MCP server
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
Orinyxhttps://orinyx-mcp.fly.dev/mcp开启新聊天,输入前先从插件列表中选择 Orinyx
用 Orinyx 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 Orinyx,或回答中出现 Orinyx 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user orinyx https://orinyx-mcp.fly.dev/mcp应能看到 Orinyx 在列表中并显示已连接
用 Orinyx 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Orinyx,或回答中出现 Orinyx 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
用 Orinyx 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Orinyx,或回答中出现 Orinyx 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
用 Orinyx 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Orinyx,或回答中出现 Orinyx 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://orinyx-mcp.fly.dev/mcpJSON 设置在下方“开发者专用”中
Claude Code
claude mcp add --transport http --scope user orinyx https://orinyx-mcp.fly.dev/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"orinyx": {
"url": "https://orinyx-mcp.fly.dev/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"orinyx": {
"type": "http",
"url": "https://orinyx-mcp.fly.dev/mcp"
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
服务器要求先登录,才会列出它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月18日
注册名称已通过 GitHub 账户 lexthirteen-ai 验证,该账户拥有此仓库
代码最后更新于前天
使用 Apache-2.0
在 3207 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
云端地址最近 3 次检查中有 3 次响应 · 最近一次 3,207 ms · 检查于 2026年11月17日
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/lexthirteen-ai-orinyx-mcp)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于前天,最新版本(0.1.2)于15天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
同一分类中有:Medplum MCP, Mirobody, Codescene MCP Server, WHOOP — MissingMCP, Marrow
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量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.
WHOOP recovery, strain, sleep and workouts in Claude via official WHOOP OAuth. Free, open source.
Marrow Health: your Apple Health data over MCP, from the free iOS app. Reads, and writes on demand.
| 本项 Orinyx | Medplum MCP | Mirobody | Codescene MCP Server | WHOOP — MissingMCP | Marrow | |
|---|---|---|---|---|---|---|
| 运行位置 | 在云端运行,无需安装 | 在云端运行,无需安装 | 需要安装在电脑上 | 需要安装在电脑上 | 在云端运行,无需安装 | 需要安装在电脑上 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 5/5 | 4/4 | 3/3 | 2/3 | 2/4 | 3/3 |
| 许可证 | Apache-2.0 | Apache-2.0 | Apache-2.0 | NOASSERTION | MIT | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Orinyx MCP Server
Test your healthcare AI agent against cited FDA labels and coded answer keys. Deterministic: no LLM in the verdict.
Not for clinical use. Orinyx is a testing and evaluation tool that checks medication claims against cited FDA label text. It does not give medical advice, and its results must not be used for diagnosis, treatment or prescribing decisions. A "supported" result means one claim matches the cited label text, not that an order is safe or appropriate. Submit synthetic test data only, never real patient information.
Synthetic data only: never send real patient records, names, dates or record numbers (claim
text is stored in the API's audit record).
Apache-2.0. This repository is a client of the Orinyx API: it holds no rules, no reference data and no verdict logic, and every tool call is an ordinary REST request carrying your own credential. The one check it runs itself is a pre-flight refusal: orinyx observe screens what it reads for identifier-shaped text (the engine's own pattern list) before sending anything. Sign up at orinyx.io/developers to use the hosted connector with your Orinyx account, or mint a personal key for stdio, the CLI or CI through the self-serve API.
verify_order_text splits each order into its dose, route and frequency claims (rules, no model) and answers with one table row per claim.verify_medications checks {rawText, drug, claimType, structuredValue} claims of nine types, from dose_range to rems_attestation.orinyx verify and orinyx observe exit 0 clean, 2 flagged, 3 not verified and 1 on error, so a pipeline can fail on a flag.What is in the box:
| Piece | Entry point | Use it from |
|---|---|---|
| MCP server, stdio | orinyx-mcp stdio or python -m orinyx_mcp | Claude Code, Claude Desktop, any local agent host |
| MCP server, network (Streamable HTTP) | orinyx-mcp or python -m orinyx_mcp serve | hosted connectors, remote agents |
| Command-line tool | orinyx verify --file claims.json | CI, shell pipelines, frameworks that do not speak MCP |
| Observer (CLI) | orinyx observe out/ | CI: checks every order in an agent's saved transcripts, not only the ones it reports |
| REST client | from orinyx_mcp.client import OrinyxClient | your own Python code |
| Operator script | python evals/product_exam.py | registering a product and opening a scored exam |
verify_order_text: at most 50 orders of 500 characters, one drug per order; Orinyx splits them.verify_medications.get_verification, get_accuracy or export_verification.find_fda_label and read_fda_label_section, or the OTC monograph tools (developer accounts). Reference text, not a verdict.start_a_test: it lists what your account can run and the next step for each.Consider something else when you need an EHR connection, need to send real patient data, or want a clinical decision. Orinyx does not do any of these: see Safety and limits.
Use the hosted connector with OAuth, or install the Python package for stdio, the CLI and CI. Local use supports browser login or an API URL and a personal API key. CI remains key-based.
| Path | For | What you need |
|---|---|---|
| Hosted connector | the self-serve path | an Orinyx account from orinyx.io/developers; no install and no key |
| Local stdio, the CLI and CI | a key holder | an Orinyx API URL and an ork_live_ key from the self-serve API or an operator |
The only official package is orinyx-mcp, published only from github.com/lexthirteen-ai/orinyx-mcp. Anything else named orinyx isn't Orinyx's.
If a step fails, see docs/TROUBLESHOOTING.md. What is tested is under Supported environments.
Nothing to install and no key: this uses the hosted connector, and you sign in with your Orinyx account.
https://orinyx-mcp.fly.dev/mcp (Streamable HTTP) in your client. The steps for each client are below.start_a_test. It lists what your account can run and the next step for each.The client sends you to the Orinyx sign-in page (OAuth 2.1; the API is the authorization server) and you sign in with your Orinyx account. No API key is needed for this path.
Per-client setup, a CI recipe and exam steps are in docs/QUICKSTART.md. Its first run checks two bundled synthetic orders, one clean and one with a planted error, and shows the output to expect.
claude mcp add --transport http orinyx https://orinyx-mcp.fly.dev/mcp
then run /mcp inside Claude Code and authenticate; you are sent to the Orinyx sign-in page. To use a key issued to you by Orinyx instead of signing in, add --header "Authorization: Bearer $ORINYX_API_KEY".
Never commit a client config file that holds a key, such as claude_desktop_config.json, .cursor/mcp.json or a project .mcp.json.
Add https://orinyx-mcp.fly.dev/mcp as a custom connector and sign in with your Orinyx account. A hosted connector is added as a connector, not in claude_desktop_config.json, which is for local servers.
For the Cursor editor or CLI, add the connector to ~/.cursor/mcp.json (or .cursor/mcp.json in a project):
{"mcpServers": {"orinyx": {"url": "https://orinyx-mcp.fly.dev/mcp"}}}
orinyx, and choose Authenticate. Sign in with your Orinyx account in the browser.agent mcp login orinyx and sign in with your Orinyx account.See the Cursor quickstart to check the connection and run a synthetic test.
codex mcp add orinyx --url https://orinyx-mcp.fly.dev/mcp
Codex detects the sign-in and opens the Orinyx sign-in page in your browser. Sign in with your Orinyx account. If you missed it, or it expires later, run codex mcp login orinyx.
The same server in ~/.codex/config.toml, if you prefer to edit it (then run codex mcp login orinyx to sign in):
[mcp_servers.orinyx]
url = "https://orinyx-mcp.fly.dev/mcp"
To use a key issued to you by Orinyx instead of signing in, add bearer_token_env_var = "ORINYX_API_KEY" to that table and export the key in the shell that starts Codex. In the codex terminal UI, /mcp lists the servers Codex has connected.
Never commit a client config file that holds a key, such as claude_desktop_config.json, .cursor/mcp.json, .codex/config.toml or a project .mcp.json.
Requires the L9 engine update before use; this is not yet a published package release. On macOS or desktop Linux with an unlocked OS keychain:
orinyx login
orinyx status --json orinyx-mcp stdio orinyx logout
Login opens your external browser and receives the result on a one-time IPv4 loopback listener. orinyx login --no-browser prints the authorization URL instead; open it on the same device within three minutes. It is not a device-code or SSH login flow. No password, code, or token is entered in the terminal.
The default API is https://orinyx-api.fly.dev; set ORINYX_API_URL to select another HTTPS API origin (HTTP is accepted only on loopback). The issuer and OAuth endpoints must belong to that origin. Each origin has its own saved login and public-client registration. Re-run commands with the same origin; credentials are never sent to a new target.
Login grants verification and Arena scopes permitted by your account, never exam scopes. Arena still needs operator enablement, tester eligibility, and ORINYX_ARENA_ENABLED=true in the local MCP environment; sign-in does not bypass any of those gates. Use the existing hosted connector for exam workflows pending the exam-integrity ruling.
Credentials, including rotating refresh tokens, live only in macOS Keychain or Linux Secret Service. There is no plaintext config-file fallback. Headless CI uses environment keys. The explicit ORINYX_API_KEY always wins, even if invalid; unset it to use a login. logout revokes the saved grant and removes the local record, not environment API keys. Offline logout reports that server revocation was not confirmed; end account sessions to invalidate a remaining server-side grant. Expired/revoked logins require login again; commands never launch a browser implicitly. Long-running stdio refreshes before API calls, not during startup, and does not retry writes after authentication failures.
Beta developers can mint their own keys after signing up and setting a password:
POST /v1/auth/login to your API host with {"email":" ", "password":" "} and keep the returned session token private.POST /v1/auth/api-keys/self with Authorization: Bearer and Content-Type: application/json: {"name":"beta-laptop","scopes":["verify:read","verify:write"],"expiresDays":30}
key in your secret store; the raw key is shown only once. The apiKey object contains its id and metadata. Set ORINYX_API_URL to your API host (hosted: https://orinyx-api.fly.dev) and ORINYX_API_KEY to that key in the environment of your client process.Only verify:read and verify:write are accepted, with at least one required. Expiry is 1–90