Score7.9
Popularity74.0
Risknone
TierSilver
Score breakdown
Usefulness8.0
Novelty7.0
Momentum8.0
Maturity7.3
Open-source/build8.4
Evidence7.2
Workflow potential9.4
Setup ease8.8
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for developers and platform teams who want to run MCP servers in production with per-request auth, audit logs, and a Kubernetes operator — without rolling their own proxy, registry, and policy layer.
Who should use it
platform teams that need to standardize on MCP across the org with per-request auth and audit logsenterprise teams with SaaS-prohibited data that need a self-hostable MCP registry / gateway / runtimedeveloper teams that want to run MCP servers in production with semantic tool search to cut token costKubernetes platform teams that want a Helm-installable MCP operator with OTel + Prometheus observabilitysecurity teams that need an MCP-specific policy enforcement layer with OIDC / OAuth integration
Who should skip it
Skip if the source link, docs, or setup requirements do not match your workflow.
Risk explanation
No inherent user-impacting risk is flagged from the captured evidence.
Evidence links
Closest alternatives / related signals
mcpmcp-platformstacklokkubernetes-operatorself-hostedoidcoauthsemantic-search