MCP100 verdict
Discover and run MCP servers through Docker's MCP gateway.
MCP100 Assessment
Editorial verdict
Discover and run MCP servers through Docker's MCP gateway.
Reviewed 2026-07-24 · Next review 2026-10-24
Task Fit
Mapped
Developer workflows
Trust
Reviewed
A dated editorial review is published on the MCP detail page.
Maintenance
Activity observed
A dated repository or package update is available; editorial maintenance review is still pending.
Popularity
Signals available
Visible usage signals are shown for discovery only, not as proof of safety.
Best for
- Running multiple MCP servers behind one stdio connection
- Isolating catalog MCP servers in containers with restricted privileges and resources
- Centralizing server profiles, secrets, OAuth, logs, and call traces
Not ideal for
- Users who need only one simple remote MCP endpoint
- Hosts where Docker Desktop or Docker Engine cannot run
Avoid if
- You cannot review every downstream MCP server and profile permission
- The agent must not be able to discover or add tools dynamically
- Container isolation is being treated as protection from an over-privileged downstream credential
Trade-offs
- Gateway isolation improves lifecycle and credential management but adds Docker runtime complexity and local resource use.
- The MCP Toolkit is documented as Beta, and Dynamic MCP is experimental.
- The gateway reduces direct host privileges, but network access and injected credentials still let downstream servers affect external systems.
Evidence scope
Evidence
Popularity
1.5k MCP repository stars
No MCP-specific package metric is stored
Stars observed 2026-08-14T18:46:26.000Z · Downloads observation date unavailable
Exact implementation repository metric.
No public package data is mapped to the reviewed MCP.
Maintenance
Publisher activity observed 2026-08-13T18:48:45Z
Current source snapshot
Trust review
Source relationship: First-party MCP
Reviewed 2026-07-24 · Next review 2026-10-24