Orinyx

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; a key for the stdio server, the CLI or CI is issued by Orinyx.

Features

• Orders as written. verify_order_text splits each order into its dose, route and frequency claims (rules, no model) and answers with one table row per claim.
• Structured claims. verify_medications checks {rawText, drug, claimType, structuredValue} claims of nine types, from dose_range to rems_attestation.
• Cited results. Each supported or flagged row cites the label section or monograph paragraph it was judged against. A flag carries a rule-derived severity.
• FDA reference lookups. Prescribing-label sections and OTC monograph text, with the SPL set ID, version and source address, for developer accounts. Reference text, not a verdict.
• Scored exams for AI products. A product account sits an exam on a fixed, synthetic test set held on the server; every report adds speed. Families and their limits are in docs/EXAMS.md.
• A CLI for CI. 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.
• Hosted or local. A hosted connector with nothing to install, or a stdio server from a checkout, plus a REST client for your own Python code.
• No model in the verdict. No language model decides a verdict, a severity or a score.

What is in the box:

When to use this server

• Check orders exactly as written with verify_order_text: at most 50 orders of 500 characters, one drug per order; Orinyx splits them.
• Check claims your agent already structures with verify_medications.
• Read a run back with get_verification, get_accuracy or export_verification.
• Read FDA reference text with find_fda_label and read_fda_label_section, or the OTC monograph tools (developer accounts). Reference text, not a verdict.
• Score an AI product on a fixed test set with the exam tools (product accounts).
• Not sure yet? Call 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.

Installation

Today a self-serve sign-up gives you the hosted connector only. The stdio server, the CLI and CI need a key issued by Orinyx.

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.

Hosted connector (the self-serve path)

Nothing to install and no key: this uses the hosted connector, and you sign in with your Orinyx account.

1. Sign up at orinyx.io/developers.
2. Add the connector https://orinyx-mcp.fly.dev/mcp (Streamable HTTP) in your client. The steps for each client are below.
3. Start a test. Then ask your agent to call 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. A self-serve account signs in this way and has no key.

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 Code

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.

Claude Desktop

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.

Cursor

Add the connector to ~/.cursor/mcp.json (or .cursor/mcp.json in a project):

{"mcpServers": {"orinyx": {"url": "https://orinyx-mcp.fly.dev/mcp"}}}

then sign in with your Orinyx account.

Codex

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.

Local stdio (from source)

Today the stdio server, the CLI and CI each need an Orinyx API URL and a key (ork_live_...) issued to you by Orinyx; a self-serve sign-up does not include a key. Install it from a checkout.

git clone https://github.com/lexthirteen-ai/orinyx-mcp.git && cd orinyx-mcp

python -m venv .venv && . .venv/bin/activate pip install -e . # Python 3.11+

export ORINYX_API_URL=https:// export ORINYX_API_KEY= orinyx-mcp stdio # speaks MCP on stdin/stdout orinyx-mcp --version # prints the installed version

The key is read from the environment only; no flag takes it. Register the server with your agent host as a stdio server:

{

"mcpServers": { "orinyx": { "command": "/absolute/path/to/orinyx-mcp/.venv/bin/orinyx-mcp", "args": ["stdio"], "env": { "ORINYX_API_URL": "https:// ", "ORINYX_API_KEY": " " } } } }

python -m orinyx_mcp starts the same stdio server. Any other argument to orinyx-mcp exits 1 with a usage line. Agent hosts launch the stdio server themselves, so point them at the virtualenv's orinyx-mcp by absolute path; a bare orinyx-mcp or python may not be the one you installed into.

Never commit a client config file that holds a key, such as claude_desktop_config.json, .cursor/mcp.json or a project .mcp.json.

Claude Code (stdio)

Export the two variables first so the key is not typed on the command line. The key is one issued to you by Orinyx:

export ORINYX_API_URL=https://<your orinyx api>

export ORINYX_API_KEY= claude mcp add orinyx \ -e ORINYX_API_URL="$ORINYX_API_URL" \ -e ORINYX_API_KEY="$ORINYX_API_KEY" \ -- /absolute/path/to/orinyx-mcp/.venv/bin/orinyx-mcp stdio

Never commit a client config file that holds a key, such as claude_desktop_config.json, .cursor/mcp.json or a project .mcp.json.

Claude Desktop (stdio)

Edit claude_desktop_config.json (Settings > Developer > Edit Config) and restart. The key is one issued to you by Orinyx:

{

"mcpServers": { "orinyx": { "command": "/absolute/path/to/orinyx-mcp/.venv/bin/orinyx-mcp", "args": ["stdio"], "env": { "ORINYX_API_URL": "https:// ", "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.

Codex (stdio)

Add this to ~/.codex/config.toml. env_vars forwards the two variables from the shell that starts Codex, so the key is never written into the file. The key is one issued to you by Orinyx:

[mcp_servers.orinyx]

command = "/absolute/path/to/orinyx-mcp/.venv/bin/orinyx-mcp" args = ["stdio"] env_vars = ["ORINYX_API_URL", "ORINYX_API_KEY"]

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.

Docker

The Dockerfile builds the network server (its command is orinyx-mcp, listening on port 8000); fly.toml builds the hosted connector from it. It is conf