Finding / omnigent
2026-10-13-omnigent-a-managed-mcp-registry-and-gateway-prototype-lands-on-main-with-separate-policy-and-creden
A managed MCP registry and gateway prototype lands on main with separate policy and credential actors. An opt-in main-only prototype adds an admin-configured MCP registry, encrypted server-held grants, per-session service selections and a gateway. The adapter authenticates the caller and requires Edit access; a session header supplies context, not authentication. Verified runner calls separate the policy actor from the credential owner, so an editor-triggered turn can use the owner’s connection subject to the actor’s policies. Direct calls use the caller for both. Queued multi-editor turn attribution remains a documented limitation. A same-evening follow-up lets users remove saved selections and launch without MCP services during registry outages.
Channel: main-unreleased. Half: both. Date: 2026-10-13T22:29:44Z merged; follow-up 23:13:40Z.
Operator consequence: Wait for a containing stable release for ordinary deployment. A prototype trial needs the same compatible commit on server and execution hosts, explicit registry configuration and a review of whose account each actor uses. Examine shared-session attribution and result-review limits; moving credentials to the server does not remove the need to authorize their use.
Receipt
- https://github.com/omnigent-ai/omnigent/commit/03beb88c01a966b04c6c762e723e8b4463dc16e0
- https://github.com/omnigent-ai/omnigent/blob/03beb88c01a966b04c6c762e723e8b4463dc16e0/omnigent/server/mcp_policy_adapter.py#L45-L129
- https://github.com/omnigent-ai/omnigent/blob/03beb88c01a966b04c6c762e723e8b4463dc16e0/designs/MCP_REGISTRY_GATEWAY.md#L175-L244
- https://github.com/omnigent-ai/omnigent/blob/03beb88c01a966b04c6c762e723e8b4463dc16e0/examples/mcp-registry/README.md
- https://github.com/omnigent-ai/omnigent/commit/5ba977020ce1f2b0a447405cfa1806ac77f21f5a
- https://github.com/omnigent-ai/omnigent/blob/5ba977020ce1f2b0a447405cfa1806ac77f21f5a/examples/mcp-registry/README.md#L103-L112
Finding metadata
Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0
Finding ID: 2026-10-13-omnigent-a-managed-mcp-registry-and-gateway-prototype-lands-on-main-with-separate-policy-and-creden
Profile citations
- omnigent / claim / managed-mcp-main-only
Source links
Primary links, including exact changelog lines when available.
- commit2026-10-13-omnigent-a-managed-mcp-registry-and-gateway-prototype-lands-on-main-with-separate-policy-and-credengithub.com/omnigent-ai/omnigent/commit/03beb88c01a966b04c6c762e723e8b4463dc16e0tagged commit file2026-10-13-omnigent-a-managed-mcp-registry-and-gateway-prototype-lands-on-main-with-separate-policy-and-credenomnigent-ai/omnigent / omnigent/server/mcp_policy_adapter.py#L45-L129tagged commit file2026-10-13-omnigent-a-managed-mcp-registry-and-gateway-prototype-lands-on-main-with-separate-policy-and-credenomnigent-ai/omnigent / designs/MCP_REGISTRY_GATEWAY.md#L175-L244tagged commit file2026-10-13-omnigent-a-managed-mcp-registry-and-gateway-prototype-lands-on-main-with-separate-policy-and-credenomnigent-ai/omnigent / examples/mcp-registry/README.mdcommit2026-10-13-omnigent-a-managed-mcp-registry-and-gateway-prototype-lands-on-main-with-separate-policy-and-credengithub.com/omnigent-ai/omnigent/commit/5ba977020ce1f2b0a447405cfa1806ac77f21f5atagged commit file2026-10-13-omnigent-a-managed-mcp-registry-and-gateway-prototype-lands-on-main-with-separate-policy-and-credenomnigent-ai/omnigent / examples/mcp-registry/README.md#L103-L112