The supported transport is explicit
The README supports an OpenRouter key, not native TypeSafe routing. demo_typesafe_sdk.py is legacy research material, so it should not be the installation path.
Inspect the supporting source ↗A Python decision gateway and Model Context Protocol (MCP) server exposing TypeSafe's Jev model through OpenRouter's decisions endpoint to Claude Code, Codex, and Cursor agents.
The server exposes Jev Choice (`jev_classify`), Score (`jev_score`), and Noul (`jev_check`) decisions over standard stdio MCP to AI coding agents, executing requests against OpenRouter's decisions endpoint:
Adds structured choices or scores to the workflow; performance and cost benefits have not been independently verified.
The pinned README was checked for the OpenRouter alpha transport, legacy SDK example and diagnostic exclusions. This site did not start the MCP server or call OpenRouter. Excluding fields from local logs does not redact the state sent over the network.
Expose bounded Jev decisions as MCP tools through OpenRouter.
Material analysed:
The README supports an OpenRouter key, not native TypeSafe routing. demo_typesafe_sdk.py is legacy research material, so it should not be the installation path.
Inspect the supporting source ↗RFC 6901 exclusions remove fields from the local diagnostic copy, not from state sent to OpenRouter. Sensitive input must be removed before submission.
Inspect the supporting source ↗Use it when a Linux/Python MCP client needs reusable decision tools. Keep command authorization and irreversible actions in the host, not in a returned probability.
Review the offline unittest command in the README with credentials removed and logs in a temporary directory. Verify the gateway transport separately from optional live health probes.