Compiled MCP tools are assembly-discovered at server startup. Source docs state adding/removing compiled tools still requires restart.
Model Context Protocol
Agent tooling that stays behind API policy
The MCP server acts as a protocol bridge: it gets service JWTs through an HMAC-signed AuthService handshake, calls implemented APIs, and returns structured tool responses.
Agent clientStdio or HTTP MCP transport.
->MCP serverTool error boundary, JWT cache, changesets, runtime observations.
AuthServiceHMAC token issue with timestamp-bound signatures.
->MedicalLibrary APIRBAC, feature flags, rate limits, and endpoint contracts.
What is intentionally bounded
Mutating tools use explicit confirmation flags or changeset entries, and sensitive workflow confirmation remains human-in-the-loop.
Runtime heartbeats, bounded tool summaries, and prompt/resource observations avoid fake sample data when no shared state exists.
Security review boundary. Shared-secret, role, scope, endpoint, and deployment details should be reviewed before publishing production setup instructions.