Plugged.in Proxy vs TAP Certified
Plugged.in Proxy is an MCP server published by VeriTeknik. Marketplaces we read that list it: 1 (Docker MCP Catalog). TAP Certified is an MCP server published by theatlasproject.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Plugged.in Proxy |  TAP Certified |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:b7c32590b270 Forks (GitHub): 30 Pulls (Docker Hub): 36 108 Stars (Docker Hub): 3 Stars (GitHub): 137 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.1.0 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Plugged.in Proxy | TAP Certified |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 137 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 36 108 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 30 | No figure on GitHub |
| Last release (differs) | Not published | 2026-10-13 |
| Where it runs (differs) | On your machine (mcp/pluggedin-mcp-proxy) | Remote server (theatlasproject.dev/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 6 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/veriteknik/pluggedin-mcp-proxy | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-13 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 4 days ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Plugged.in Proxy
A unified MCP proxy that aggregates multiple MCP servers into one interface, enabling seamless tool discovery and management across all your AI interactions. Manage all your MCP servers from a single connection point with RAG capabilities and real-time notifications.
TAP Certified
Check if an AI agent is certified; list the TAP Registry and certifications. Free, read-only.
How to run each
Plugged.in Proxy As a local MCP server: Docker image
claude mcp add --env "PLUGGEDIN_API_KEY=<YOUR_PLUGGEDIN_API_KEY>" --transport stdio pluggedin-mcp-proxy -- docker run -i --rm -e PLUGGEDIN_API_KEY mcp/pluggedin-mcp-proxyRequires: PLUGGEDIN_API_KEY (secret)
TAP Certified As a remote MCP server
claude mcp add --transport http tap-certified https://theatlasproject.dev/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only TAP Certified has a remote endpoint we check. How we check endpoints
Tools each declares
Only Plugged.in Proxy has
pluggedin_ask_knowledge_basepluggedin_delete_notificationpluggedin_discover_toolspluggedin_list_notificationspluggedin_mark_notification_donepluggedin_send_notification
Only TAP Certified has
check_agent_certificationhow_to_get_certifiedlist_certificationslist_certified_agents
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (TAP Certified as of 2026-10-15). More tools is not better in itself: compare what each needs for the job.
Settings each asks for
The marketplaces of TAP Certified publish no settings it asks for, so we do not compare settings.
What it can do: Plugged.in Proxy · What it can do: TAP Certified · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.