Ext Ops Panel
Open dashboard
Comparison

VoIP vs com.dialfetch/dialfetch

VoIP is a plugin bundle for AI coding tools published by codingjoe. Marketplaces we read that list it: 1 (Community GitHub marketplaces). com.dialfetch/dialfetch is an MCP server published by dialfetch.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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
MarketplaceVoIPcom.dialfetch/dialfetch
Community marketplace codingjoe/claude-plugins Not seen in the last pass
Version: 0.5.3
Forks (GitHub): 2
Stars (GitHub): 10
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 0
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

VoIP vs com.dialfetch/dialfetch
FactVoIPcom.dialfetch/dialfetch
Marketplaces that list it11
Stars (GitHub) (differs)10 (better)0 (worse)
Forks (GitHub) (differs)2 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (voip)Remote server (app.dialfetch.com/api/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 0Not published
Parts of the bundle (differs)5Not a bundle
Licence (differs)BSD-2-ClauseNot stated
Repository (differs)github.com/codingjoe/voipgithub.com/xneyder/dialfetch-mcp
Changes in the last 7 days (differs)20
First seen (differs)2026-10-152026-10-11
Endpoint at the last check (differs)no remote endpoint we checkNot responding since 2026-10-15

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

VoIP

In its own words, on Community GitHub marketplaces:

Async VoIP library for the AI age. Ships an MCP server to make phone calls and (planned) skills.

com.dialfetch/dialfetch

In its own words, on Official MCP Registry:

Give your AI agent a phone: place calls, navigate IVRs, wait on hold, get structured answers.

How to run each

VoIP As a Claude Code plugin

Claude Code
/plugin marketplace add codingjoe/claude-plugins
/plugin install voip@codingjoe

com.dialfetch/dialfetch As a remote MCP server

Claude Code
claude mcp add --transport http dialfetch https://app.dialfetch.com/api/mcp

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

Only com.dialfetch/dialfetch 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

The marketplaces of com.dialfetch/dialfetch publish no settings it asks for, so we do not compare settings.

What it can do: VoIP · What it can do: com.dialfetch/dialfetch · Compare two other plugins

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