A governed, auditable agent gateway for oncology data workflows
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"custody-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Custody Custody sits between an AI agent and the tools it uses on oncology data, so the agent can work under controls a privacy or compliance officer can actually review: data-aware policy, approval gates for anything sensitive, a tamper-evident audit log, and isolated execution for every command. ``` Agent (Claude Code / Codex / OpenHands / Goose / any MCP client) | MCP (stdio or streamable HTTP) v Custody Gateway 1. Identify principal + session 2. Classify request (tool, datasets, data class, egress, model target) 3. Policy engine -> allow | deny | require_approval 4. Approval broker -> wait for human decision (timeout = deny) 5. Executor -> sandboxed container 6. Output guard -> redact/summarize results by data class 7. Audit log -> hash-chained entry at every step | v Custody's own tools: catalog.list, sql.query, shell.run, files.write, files.export, approvals.status, fhir.search ``` Status: v0.1.0 tagged and public (285 tests, 96% coverage on `src/custody`, `ruff` and `mypy --strict` clean); `main` carries several items since merged in from ROADMAP.md (signed policy bundles, an OPA policy backend, a Kubernetes deployment, a FHIR connector, an S3 Object Lock audit sink, an egress allowlist proxy, OIDC-verified approver identity) -- see CHANGELOG.md's `[Unreleased]` section for exactly what, and for what shipped in v0.1.0 itself. One scope note: the architecture above describes a gateway that can also proxy a downstream MCP server's tools, that proxying is **not implemented**, every tool call this release handles goes through one of the built-ins listed above (see `custody/mcp_server.py`'s module docstring). ## Quickstart (under 5 minutes to the demo, Docker required) From a clone of this repository (not yet published to PyPI): ```bash git clone <this repo> cd custody uv sync --extra dev docker build -f docker/sandbox.Dockerfile -t custody-sandbox:duckdb . uv run custody demo ``` `custody demo` generates a…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.