MCP access with an enterprise boundary.
Use Durin as a governed MCP gateway with enterprise identity, default-allow policy checks, optional approvals, reviewed tools, and execution evidence.
Connect the client you approve
Configure an MCP-compatible client to use the gateway and bind the authenticated client instance to the request. Exact client versions and hosted interoperability remain release checks.
Enforce reviewed tools
List and invoke the reviewed tools and resources available to the deployment. Production discovery, change diff, review, and activation remain explicit trust controls.
Treat protocol outcomes precisely
The gateway supports the current Streamable HTTP path and a tested legacy initialize path. Policy outcomes (allowed, denied, or approval-required) remain distinct from execution outcomes (succeeded, failed, or uncertain).
Before dispatch
- Allowed
- Denied
- Approval required
Denied requests stop here. Approval-required requests wait for review.
After dispatch
- Succeeded
- Failed
- Uncertain
A timeout is not proof that a write failed.
Test a governed MCP route.
Create an account to manage an MCP gateway path while checking client coverage, provider boundaries, and rollout limits.
Create an account