Skip to content
This repository was archived by the owner on Feb 15, 2026. It is now read-only.

feat: support self-hosted instances on private networks#1

Merged
NicolasRitouet merged 3 commits into
mainfrom
feat/self-hosting
Feb 3, 2026
Merged

feat: support self-hosted instances on private networks#1
NicolasRitouet merged 3 commits into
mainfrom
feat/self-hosting

Conversation

@NicolasRitouet

Copy link
Copy Markdown
Member

Summary

  • Add single-label hostname detection to isPrivateNetwork() for Docker service names (e.g., backend, api)
  • This allows MCP to connect to self-hosted instances over HTTP when using Docker Compose internal networking

Test plan

  • KEYWAY_API_URL=http://backend:8080 connects without HTTPS enforcement error
  • KEYWAY_API_URL=https://api.example.com still requires HTTPS (public hostname)
  • KEYWAY_API_URL=http://localhost:8080 still works (already supported)

🤖 Generated with Claude Code

NicolasRitouet and others added 3 commits February 1, 2026 23:27
Add single-label hostname support to isPrivateNetwork for Docker
service names (e.g., 'backend', 'api'). This allows MCP to connect
to self-hosted instances over HTTP on private networks.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Fixes security audit failures:
- GHSA-8r9q: ReDoS in @modelcontextprotocol/sdk (fixed in 1.25.3)
- GHSA-3vhc, GHSA-f67f: JWT algorithm confusion in hono (fixed in 4.11.4)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@NicolasRitouet NicolasRitouet merged commit 66fb19a into main Feb 3, 2026
4 of 12 checks passed
@NicolasRitouet NicolasRitouet deleted the feat/self-hosting branch February 3, 2026 00:05
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant