devops-infra MCP Server
Hardened LLM and MCP gateway container — deployment recipes for the customer-edge service-edge image with policy enforcement, mTLS, and multi-provider routing.
Discovered via github-topic:model-context-protocol and last synced 3mo ago.
Install instructions not detected yet
Check the source repository for the latest setup steps.
`service-edge@sha256:...`
The image runs as non-root UID 1000. Persistent volumes need `chown -R 1000:1000` (Docker) or `fsGroup: 1000` (Kubernetes). ### Bootstrap and identity
No
`service-edge:0.4.0`
`service-edge:0.4`
`service-edge:sha-<short>`
Guide
[render/](render/)
Purpose
Default
Yes (first run)
Required
**Yes**
No
No
No
No
Purpose
MCP JSON-RPC 2.0 endpoint (Streamable HTTP transport)
Enrollment claim
`capabilities.llm: true`
`service-edge:0`
Recommended (recoverable on cold start, but adds latency)
No
Protocol
Image
[helm/service-edge/](helm/service-edge/)
No
`capabilities.mcp: true`
`service-edge:latest`
HTTPS
Example
[railway/](railway/)
No
No
PRM discovery (alternative path)
Health checks and actuator only. Binds at startup; LLM/MCP endpoints are blocked here unless `TLS_PORT_FILTERING_ENABLED=false`.