orinyx-mcp 0.1.5__tar.gz

orinyx_mcp-0.1.5/.gitignore

@@ -0,0 +1,10 @@
+__pycache__/
+*.pyc
+.venv/
+.pytest_cache/
+.ruff_cache/
+*.egg-info/
+dist/
+build/
+.env
+.env.*

orinyx_mcp-0.1.5/CHANGELOG.md

@@ -0,0 +1,207 @@
+# Changelog
+
+All notable changes to this project are recorded here. The format is based on
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
+
+## [0.1.5] - 2026-11-15
+
+### Added
+
+- `orinyx login`, `logout`, and `status`: browser OAuth with native keychain storage,
+  rotating refresh, and CLI/stdio credential resolution. Verification and Arena are included
+  according to account permissions; exams remain excluded. Explicit environment keys win.
+
+- Tag-driven PyPI publishing through GitHub OIDC and the protected `pypi` environment.
+  The workflow tests and builds the package, requires a matching version tag, and publishes
+  only the resulting wheel and source distribution without a long-lived PyPI token.
+- [Local package/stdio setup and CLI examples](README.md#installation), alongside the engine's
+  session-only self-serve key flow. The engine must be deployed first;
+  developer keys carry only `verify:read` and `verify:write` and expire within 90 days.
+  An account can have at most two active keys; a revoked or expired key does not count.
+
+- Every tool now has a human-readable title and MCP behaviour hints in `tools/list`
+  (`readOnlyHint`, `destructiveHint`, `idempotentHint`, `openWorldHint`), set from what each
+  call does on the Orinyx API. The reads and lookups are read-only. `finish_exam` is marked
+  destructive, since it closes a sitting for good. The verifications and exports are
+  additive and not idempotent, since each adds a run or an audit-chain entry. Tool names,
+  input schemas and descriptions are unchanged.
+- Nine new tests hold rules the code already followed, so a later change cannot loosen them
+  unnoticed: which credential a request carries, what the sign-in callback refuses, what the
+  CLI accepts from the token endpoint, the sign-in metadata and the keychain, the lock that
+  keeps sign-in renewals apart, the two scope lists, the credential module's imports, and the
+  match between the release manifest and the tracked files.
+
+### Changed
+
+- Onboarding docs: the README includes the welcome-email password step before connecting,
+  the README and Quickstart include help for a missing email, and troubleshooting correctly
+  permits developer FDA reference lookups. The README notes that the hosted connector's running
+  build can differ from the latest repository release.
+- Packaging for PyPI: the package metadata is complete (authors, keywords, classifiers and
+  project URLs), dependency ranges stop before the next major version, the build backend has
+  a bounded range, the source distribution holds a reviewed list of files, and the README's
+  links and logo are absolute so they work on the PyPI page. The lowest allowed versions rise
+  to `httpx` 0.28, `pydantic` 2.12, `starlette` 1.3.1 and `uvicorn` 0.31.1.
+- Before it sends orders, `orinyx observe` asks the Orinyx API for the current identifier
+  screen. If the API serves a different list, `observe` screens with that list. If the API
+  says its screen differs but does not send it, `observe` refuses rather than screen with a
+  stale list. If the API does not serve the list or cannot answer, the local copy is used; a
+  failed request is logged.
+- On the first tool call, the MCP server checks its copies of the label sections and the
+  identifier screen against the API's, in the background, when the API serves those lists. A
+  difference is logged. The API does not serve them yet, so for now the local copies are used.
+
+### Fixed
+
+- Reports no longer obey characters inside the text they show. In what `orinyx verify` and
+  `orinyx get` print, and in the tables the MCP tools return, a line break or tab inside a
+  claim, an explanation or a citation is shown as one space, and a control, format or
+  bidirectional character is shown as an escape such as `\x1b` or `\u202e`. Before this, an
+  AI tool under test could write an order that added lines of its own to the report, or hid
+  part of it on a terminal. Exit codes and `--json` output are unchanged, and text made of
+  ordinary characters and single spaces prints exactly as before.
+- The HTTP app keeps an explicitly supplied client pool even when it is empty. Previously,
+  an empty pool was treated as missing and replaced by the default, discarding its custom
+  transport and idle-client limit. Omitting the pool or passing `None` still selects the
+  default; the selected pool is closed when the app shuts down.
+- The network server refuses to start when `MCP_PUBLIC_URL` contains a username or password,
+  which it would otherwise publish in its protected-resource document and in the challenge of
+  every 401.
+- The network server refuses to start when `ORINYX_HOP_SECRET` cannot be sent as an HTTP header
+  (a line break or a NUL inside it, or a space or tab at either end), instead of starting,
+  reporting healthy and then refusing every caller.
+- Running the tests can no longer read, refresh or use a sign-in saved by `orinyx login`: the
+  test suite now blocks the OS keychain in its own process and in the child processes it
+  starts, and refuses any connection that leaves the machine.
+- `requirements.lock` pins `opentelemetry-api` 1.45.2 (was 1.45.1), the release that fixes
+  GHSA-mf5v-w3w3-f6cg (CVE-2026-126360), slow parsing of a crafted `traceparent`. A new test
+  fails if the pin falls below 1.45.2. The package's own dependency ranges are unchanged.
+
+## [0.1.4] - 2026-11-05
+
+### Changed
+
+- Developer accounts can use the five FDA reference lookups: `find_fda_label`,
+  `read_fda_label_section`, `find_otc_monographs`, `get_otc_monograph` and
+  `read_otc_monograph_section`. `start_a_test` lists them under LOOK SOMETHING UP for a
+  developer account. They return reference text, not a verdict, and are not charged against
+  the monthly checks of the free plan. On a label lookup the reply says how the name was
+  matched, and a formulation or salt Orinyx stripped from the name is shown as a caution.
+- Still staff-only: a label's version history and diff, a monograph's version history and its
+  separate orders listing, and a regulatory document's content. Product (vendor) accounts are still refused
+  every lookup. The change is in the Orinyx API; tool names and input schemas are unchanged.
+
+## [0.1.3] - 2026-11-05
+
+### Added
+
+- Every result row names the Orinyx check that produced it (beta). When Orinyx sends a run's
+  `checks` list, the tool text of `verify_order_text`, `verify_medications` and
+  `get_verification`, and the `orinyx verify` text output, carry a block headed
+  "Checks (beta release candidates; Orinyx names the check behind each row):". It names each
+  check by the label Orinyx sends, with the rows it produced and its own counts (flagged,
+  unreadable, supported, not verified); unreadable rows are never counted as flagged. The
+  block follows the existing output, so the earlier lines are unchanged and `Run id:` is
+  still the last line of tool text. A run without `checks` renders as in 0.1.2.
+- Install docs: a new `docs/TROUBLESHOOTING.md`, a "Supported environments" section in the
+  README and an "Official package" section in SECURITY.md. The README and SECURITY.md name
+  the only official package, `orinyx-mcp`, published only from
+  `github.com/lexthirteen-ai/orinyx-mcp`.
+- `orinyx-mcp stdio` starts the stdio MCP server, the same server as `python -m orinyx_mcp`,
+  and `orinyx-mcp --version` prints the installed version.
+
+### Changed
+
+- The server instructions say every result row names the Orinyx check that produced it
+  (Medication Claims, Semantic Mapping or Source Evidence), and that these checks are beta
+  release candidates, not production-ready, each deciding with deterministic rules only. The
+  descriptions of `verify_medications`, `verify_order_text` and `get_verification` say each
+  row names the check that produced it (beta). Tool names and input schemas are unchanged.
+- Install docs: the README's Installation section puts the hosted connector first as the
+  self-serve path, with Claude Code, Claude Desktop and Cursor steps, and says the stdio
+  server, the CLI and CI need a key issued by Orinyx. Every example that holds a key warns
+  never to commit a client config file that holds one.
+- `orinyx-mcp` with any argument other than `stdio` or `--version` (for example
+  `orinyx-mcp serve`) now exits 1 with a usage line instead of starting the network server.
+  `orinyx-mcp` with no argument is still the network server, unchanged.
+
+## [0.1.2] - 2026-11-03
+
+### Changed
+
+- Docs (2026-11-03): repository links now use `lexthirteen-ai/orinyx-mcp`; restored two
+  disclosures a tidy edit had dropped (the IV acetaminophen fix does not cover CDS Hooks,
+  telehealth or transcript extraction; the smoke test's IV step covers `IV` only); the
+  Acknowledgements say the optional models are not enabled on the hosted service.
+
+## [0.1.1] - 2026-11-02
+
+### Added
+
+- The not-for-clinical-use statement opens the server instructions and every tool description,
+  the README's first screen and the release notes; tests pin the exact text.
+
+### Changed
+
+- `verify_medications`'s description asks for one patient's medications per call, and says
+  that when the call states one route for a drug, that route is carried onto the drug's
+  frequency claims that state none. Nothing is carried for a drug whose claims state two
+  routes or one Orinyx cannot read, or whose drug name names a different route. The tool name
+  and input schema are unchanged.
+- The IV acetaminophen known limit: oral-label frequency is fixed on the orders path and on
+  `verify_medications` structured runs; not CDS Hooks, telehealth or transcript extraction;
+  IVP is not read as a route. Its disclosed limits are
+  listed with it. See
+  [Known limits](docs/RELEASE_NOTES_2026-11-02.md#known-limits).
+- The release notes are dated with the publication date (`docs/RELEASE_NOTES_2026-11-02.md`)
+  and name orinyx-mcp 0.1.1. A new known limit says that a NOT VERIFIED row shows no
+  citation, even when Orinyx's result names a specific label.
+
+## [0.1.0] - 2026-10-29
+
+Limited testing release of the hosted connector `https://orinyx-mcp.fly.dev/mcp`, with
+orinyx-mcp 0.1.0 and Orinyx engine 0.3.1. Synthetic data only. The current release notes,
+which cover 0.1.0 and 0.1.1 and list every known limit, are in
+[docs/RELEASE_NOTES_2026-11-02.md](docs/RELEASE_NOTES_2026-11-02.md).
+
+### Added
+
+- **Orders as written** (`verify_order_text`): each order is split into a dose, a route and a
+  frequency claim, with no language model, and each is checked against FDA label text or an
+  FDA OTC monograph. One drug per order; up to 50 orders of 500 characters per request.
+- **Structured claims** (`verify_medications`) of nine claim types, one claim type per claim.
+- **Interactions within a request** (`check_interactions: true` on either tool), checked
+  against the labels' own Drug Interactions text.
+- **Run read-backs:** `get_verification`, `get_accuracy` and `export_verification` (CSV, PDF
+  or a report). Every run is stored in an audit record under your account, and audit records
+  cannot be deleted.
+- **Four results per claim:** FLAGGED (with a severity), SUPPORTED, NOT VERIFIED (abstain) and
+  UNREADABLE. Each supported or flagged row cites the label section or monograph paragraph it
+  was judged against. A supported row is not a safety clearance, and an abstain is unchecked,
+  never passing. Orinyx flags; the clinician decides.
+- **Free plan:** 200 checks per calendar month (UTC), one account per sign-up. One call to
+  `verify_order_text` or `verify_medications` is one check; lookups and read-backs do not
+  count.
+- **A refused key says so:** when the API refuses the key or sign-in itself (401),
+  `start_a_test` answers with a short message saying it was refused and what to check, instead
+  of the menu of tests.
+
+### Not in this release
+
+- Exams are not self-serve: they are for product accounts that Orinyx registers.
+- Label and monograph lookups are for staff accounts and are refused for a developer account.
+- The dashboard is for staff accounts.
+
+### Known limits
+
+Known gaps in the knowledge base and the checks, among them nitrofurantoin (route only), no IV
+acetaminophen daily ceiling, weight- and age-conditional maxima not compared, one label per
+drug, and combination products. Most show up as a NOT VERIFIED row, a refused order or a daily
+total that was not checked, so a missing flag is never evidence that an order is safe. See
+[Known limits](docs/RELEASE_NOTES_2026-11-02.md#known-limits).
+
+[Unreleased]: https://github.com/lexthirteen-ai/orinyx-mcp/compare/v0.1.4...HEAD
+[0.1.4]: https://github.com/lexthirteen-ai/orinyx-mcp/compare/v0.1.3...v0.1.4
+[0.1.3]: https://github.com/lexthirteen-ai/orinyx-mcp/compare/v0.1.2...v0.1.3
+[0.1.2]: https://github.com/lexthirteen-ai/orinyx-mcp/compare/v0.1.1...v0.1.2
+[0.1.1]: docs/RELEASE_NOTES_2026-11-02.md

orinyx_mcp-0.1.5/LICENSE

@@ -0,0 +1,190 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   Copyright 2026 Lex Hamilton
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.