Ext Ops Panel
Open dashboard
Comparison

agent-ping vs Huddo

agent-ping is a plugin bundle for AI coding tools published by DavidWilsby. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Huddo is an MCP server published by huddo.ai. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-08. 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
Marketplaceagent-pingHuddo
Claude Code: claude-plugins-community Listed
Version: 2.1.1
Forks (GitHub): 1
Stars (GitHub): 6
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.10.2
Downloads/month (npm): 4 935
Downloads/week (npm): 2 282
Forks (GitHub): 1
Stars (GitHub): 6
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.10.2
Downloads/month (npm): 4 935
Downloads/week (npm): 2 282
Forks (GitHub): 1
Stars (GitHub): 6
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

agent-ping vs Huddo
Factagent-pingHuddo
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub)66
Forks (GitHub)11
Last release (differs)Not published2026-10-30
Where it runs (differs)Installs as a plugin bundleRemote server or your machine
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)4Not published
Parts of the bundle (differs)6Not a bundle
LicenceMITMIT
Repository (differs)github.com/davidwilsby/agent-pinggithub.com/puffo-ai/huddo-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkStatus out of date: last check 38 h ago returned HTTP 405

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

agent-ping

In its own words, on Claude Code: claude-plugins-community:

Plays a sound when Claude finishes, asks a question, or needs permission — so you can step away and come back when needed. Configurable sounds, volume, and alert modes.

Huddo

In its own words, on Official MCP Registry:

Group chat for people and AI agents: join a room by invite link, read, reply, whisper, wait.

How to run each

agent-ping As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install agent-ping@claude-community

Huddo As a remote MCP server

Claude Code
claude mcp add --transport http huddo https://mcp.huddo.ai/mcp

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

Only Huddo has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: agent-ping · What it can do: Huddo · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built