coulomb/hub-core
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

feat: compose authenticated stdio MCP with explicit runtime tool mapping
Some checks failed
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / pytest-smoke (push) Failing after 3s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0e747-8f27-7242-8df8-8bc44f88c929
This commit is contained in:
tegwick 2026-09-28 12:38:04 +02:00
parent 1ece969f59
commit 3c5cbfbafe
14 changed files with 465 additions and 81 deletions
Download patch file Download diff file Expand all files Collapse all files

5
README.md
View file

@ -125,3 +125,8 @@ are tracked in `HUB-WP-0006`.
API/MCP/migration commands, and a locked non-root OCI image.
Domain-specific MCP tools follow in each hub package.
MCP access enforcement and the standalone four-tool runtime profile are described
in the [MCP composition contract](docs/owner-access-integration.md#mcp-caller-composition-and-backend-mapping).
Production stdio requires an explicitly projected caller credential; network
MCP requires an authenticated host with per-invocation Hub credentials.