Comparison

Plugged.in Proxy vs net.hookpulse/hookpulse

Plugged.in Proxy is an MCP server published by VeriTeknik. Marketplaces we read that list it: 1 (Docker MCP Catalog). net.hookpulse/hookpulse is an MCP server published by hookpulse.net. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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

Where each is published
Marketplace	Plugged.in Proxy	net.hookpulse/hookpulse
Docker MCP Catalog	Listed Version: sha256:b7c32590b270 Forks (GitHub): 30 Pulls (Docker Hub): 35 817 Stars (Docker Hub): 3 Stars (GitHub): 136 Not marked · First seen 2026-10-11	Not listed
Official MCP Registry	Not listed	Listed Version: 1.0.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen 2026-10-11

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

Plugged.in Proxy vs net.hookpulse/hookpulse
Fact	Plugged.in Proxy	net.hookpulse/hookpulse
Marketplaces that list it	1	1
Stars (GitHub) (differs)	136 (better)	0 (worse)
Pulls (Docker Hub) (differs)	35 817	No figure on Docker Hub
Forks (GitHub) (differs)	30 (better)	0 (worse)
Last release (differs)	Not published	2026-10-15
Where it runs (differs)	On your machine (mcp/pluggedin-mcp-proxy)	Remote server (hookpulse.net/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/wrpbr/hookpulse
Changes in the last 7 days (differs)	0	2
First seen	2026-10-11	2026-10-11
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

In its own words, on Docker MCP Catalog:

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.

net.hookpulse/hookpulse

In its own words, on Official MCP Registry:

Dead-man switch for cron and webhooks: ingest URL, miss detection, alerts and a status feed.

How to run each

Plugged.in Proxy As a local MCP server: Docker image

Claude Code

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-proxy

Requires: PLUGGEDIN_API_KEY (secret)

net.hookpulse/hookpulse As a remote MCP server

Claude Code

claude mcp add --transport http hookpulse https://hookpulse.net/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only net.hookpulse/hookpulse has a remote endpoint we check. How we check endpoints

Tools each declares

Only Plugged.in Proxy has

pluggedin_ask_knowledge_base
pluggedin_delete_notification
pluggedin_discover_tools
pluggedin_list_notifications
pluggedin_mark_notification_done
pluggedin_send_notification

Only net.hookpulse/hookpulse has

api_index
contact
create_collection
create_device_input
create_endpoint
create_environment
create_guest
delete_collection
delete_device_input
delete_endpoint
delete_environment
get_collection_series

Show the remaining 27

get_device_input_batch
get_device_input_setup
get_endpoint
get_environment
health
import_crontab
ingest_key
ingest_key_rotate
list_collections
list_device_input_history
list_device_inputs
list_endpoints
list_environments
list_events
list_input_fleet
list_templates
ping_ingest
ping_slug
report_environment
set_device_input_active
signal_exit_code
signal_fail
signal_start
status_feed_rotate
status_feed_url
update_collection
update_environment

Both have

None

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (net.hookpulse/hookpulse 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 net.hookpulse/hookpulse publish no settings it asks for, so we do not compare settings.

What it can do: Plugged.in Proxy · What it can do: net.hookpulse/hookpulse · 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 2026-10-17. We publish no contact details for plugin publishers.