Skip to content

Add ECHO Connectors: 12 namespace-jailed MCP facades over the SDK gate - #2

Draft
echoomegaprime wants to merge 1 commit into
mainfrom
agent/echo-connectors
Draft

Add ECHO Connectors: 12 namespace-jailed MCP facades over the SDK gate#2
echoomegaprime wants to merge 1 commit into
mainfrom
agent/echo-connectors

Conversation

@echoomegaprime

Copy link
Copy Markdown
Owner

Summary

Adds twelve namespace-jailed MCP connectors over the FORGE SDK gate. One
zero-dependency Node runtime; connector identity is selected by ECHO_CONNECTOR.
Each connector exposes five tools scoped to a single ECHO service namespace.

Why

The SDK gate exposes 13,731 undifferentiated capabilities through a single tool
surface. Clients could not scope access to one service, and nothing prevented a
vault-scoped caller from invoking echo.shell.run.

Validation

node smoke.js
12 connectors | 12 clean | 0 failed checks

node guards.js
6 assertions | 6 passed | 0 failed

python -m detect_secrets scan .git/pushrange.diff
0 files flagged

Smoke spawns each connector as a real MCP stdio child against the live gate; no
mocks. Container build not run - this package has no container target.

Security

No secrets in the repository. The sovereign key is read from a protected file at
runtime; ECHO_SOVEREIGN_KEY is a container-only fallback and is never
committed. Secret redaction is enabled on the vault, oauth and ghgateway
connectors. Danger tier >= 2 requires a 50-character justification; tier 3 is
refused by default. Additive only - no migration, no rollback dependency.

Evidence

Commit: 3cbb844
Certification Forge / Release Sentinel / CodeQL: see checks on this commit.

One zero-dependency runtime, twelve connector identities selected by ECHO_CONNECTOR. Each exposes caps/describe/invoke/health/about over one ECHO service namespace. Guards enforced in code: namespace jail, tier>=2 bypass_reason, tier-3 block, archived/RETIRED refusal, secret redaction on vault/oauth/ghgateway. Verified live: 12/12 connectors clean, 6/6 governance assertions passed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants