Field-by-field comparison
Compare the evidence before choosing an MCP.
Each signal stays separate, missing facts remain visible, and the column order follows your selection.
| Evidence field | Postman MCPWatchlist candidate | Docker MCP GatewayMCP100 Selected |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | First-party MCP Postman · Publisher source ↗ | First-party MCP Docker · Publisher source ↗ |
| Maintenance | ||
| Maintenance details | Repo: Aug 13, 2026 Package: Jul 24, 2026 | Repo: Aug 13, 2026 Package: Not documented |
| Popularity evidence | ||
| GitHub stars | 296 GitHub stars · checked 2026-08-14T18:46:26.000Z | 1,529 GitHub stars · checked 2026-08-14T18:46:26.000Z |
| 30-day package downloads | 39,429 30-day package downloads · checked 2026-07-29T17:30:00.000Z | No reliable download data |
| External adoption evidence |
|
|
| Client coverage | ||
| Client coverage details | Claude Code✓ Streamable HTTP Claude Desktop✓ Streamable HTTP Codex✓ Streamable HTTP VS Code✓ Streamable HTTP Cursor✓ Streamable HTTP OpenCode✓ Streamable HTTP | Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio |
| Client coverage note | Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server. | |
| Access and data | ||
| Authentication | Follow only the publisher source; credential storage, scopes, and revocation remain under review. | The gateway handles downstream server credentials and OAuth flows. The client connects locally over stdio by running `docker mcp gateway run`, optionally with a named profile. |
| Cost | Publisher plans, API usage, infrastructure, or per-action charges may apply; MCP100 has not published a cost conclusion. | The open-source gateway documents no standalone usage fee. Docker Desktop licensing, Docker AI Governance invite-only features, container infrastructure, downstream MCP services, and AI-client charges may apply. |
| Permissions | Exact permissions and read/write boundaries have not completed MCP100 review. | The gateway exposes the servers and tools included in the selected profile. It starts catalog servers in containers with restricted privileges, network access, and resource usage, injects configured secrets, and can support OAuth. Dynamic MCP can additionally expose tools that discover, add, configure, remove, and execute servers during a session. |
| Data handling | Candidate-specific retention, subprocess, telemetry, and model-data behavior remain review items. | Tool requests and results pass through the local gateway to downstream MCP containers or remote services. Docker documents built-in logging and call tracing. Credentials are managed and injected by the gateway; downstream servers can still receive data and reach networks allowed by their configuration. |
| Limitations | ||
| Tradeoffs |
|
|
| Risk context | Use a test account, least privilege, read-only controls where available, and explicit approval for mutations. | Gateway safety is only as strong as the selected profile, catalog provenance, tool filters, network policy, and downstream credentials. Disable experimental Dynamic MCP unless required, use narrow profiles, verify signatures where available, inspect traces, and treat each downstream server as a separate trust decision. This review does not claim MCP100 execution testing. |
| Evidence date | ||
| Editorial review | 2026-07-24 | 2026-07-24 |
| Candidate evidence | 2026-08-14T18:46:26.000Z | 2026-08-14T18:46:26.000Z |
Popularity, maintenance, fit, permissions, and client support are independent evidence fields.
Read the evidence method →