Support remote MCP servers safely #47

New issue

Open

opened 2026-10-24 23:25:41 +00:00 by TheComputerGuy · 0 comments

TheComputerGuy commented

2026-10-24 23:25:41 +00:00

Owner

Problem

Chock supports local MCP processes, while many integrations are remote HTTP services. Treating one as a trusted tool could bypass host network policy, credential boundaries, and per-call auditing.

Proposed outcome

Route remote MCP transport through Chock's network broker. Authorize destinations, scope credentials to the approved server, apply per-tool policy at dispatch, sanitize results, and log both the logical call and network destination.

Acceptance criteria

Redirects, DNS rebinding, proxy settings, and server requests cannot escape destination policy.
Credentials are server-scoped and absent from model-visible logs.
Discovery and invocation are separately policy-controlled.
Cancellation, timeout, reconnect, and partial streams have defined behavior.
Local and remote transports have consistent diagnostics.

### Problem Chock supports local MCP processes, while many integrations are remote HTTP services. Treating one as a trusted tool could bypass host network policy, credential boundaries, and per-call auditing. ### Proposed outcome Route remote MCP transport through Chock's network broker. Authorize destinations, scope credentials to the approved server, apply per-tool policy at dispatch, sanitize results, and log both the logical call and network destination. ### Acceptance criteria - Redirects, DNS rebinding, proxy settings, and server requests cannot escape destination policy. - Credentials are server-scoped and absent from model-visible logs. - Discovery and invocation are separately policy-controlled. - Cancellation, timeout, reconnect, and partial streams have defined behavior. - Local and remote transports have consistent diagnostics.

TheComputerGuy added the

enhancement

label

2026-10-25 11:59:04 +00:00

TheComputerGuy added reference feat/remote-mcp

2026-10-29 22:36:06 +00:00

TheComputerGuy referenced this issue from a pull request that will close it,

2026-10-29 22:36:16 +00:00

feat: reach a remote MCP server over HTTP #63