Plugged.in Proxy vs mcp-pulse
mcp-pulse is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑16.
Plugged.in Proxy is an MCP server published by VeriTeknik. Marketplaces we read that list it: 1 (Docker MCP Catalog). mcp-pulse is an MCP server published by ondraulehla. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-25. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Plugged.in Proxy | |
|---|---|---|
| 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 | Removed on 2026-10-16 Version: 0.1.1 Forks (GitHub): 0 Stars (GitHub): 1 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 | mcp-pulseno longer listed · |
|---|---|---|
| Marketplaces that list it (differs) | 1 | 0 |
| Stars (GitHub) (differs) | 137 | 1 |
| Pulls (Docker Hub) (differs) | 36 108 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 30 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/pluggedin-mcp-proxy) | Remote server (mcp-pulse.ulehla.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 | github.com/ondraulehla/mcp-pulse |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of mcp-pulse
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
MCP Scan — weekly registry health scans
Weekly scans of MCP servers for availability and consistency, with a public dashboard.
-
Meta-MCP gateway: search, inspect and call any MCP server from the public registries.
-
Monitor MCP, CI, and HTTP targets with health history, TLS expiry, assertions, and diagnostics
-
Search, vet & assemble MCP servers from your agent: verified tools, risk labels, and trust scores.
-
Search and browse every MCP server in the Model Context Protocol registry.
-
Real-time health monitoring and heartbeat tracking for agent services
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.
mcp-pulse
Health and token cost of every remote MCP registry server, probed daily. Look up, search, or probe.
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)
mcp-pulse
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of mcp-pulse publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of mcp-pulse publish no settings it asks for, so we do not compare settings.
What it can do: Plugged.in Proxy · What it can do: mcp-pulse · 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.