Ext Ops Panel
Open dashboard
Comparison

io.github.ClawCall-Dev/clawcall vs io.github.handset-hq/handset

io.github.ClawCall-Dev/clawcall is an MCP server published by ClawCall-Dev. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.handset-hq/handset is an MCP server published by handset-hq. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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
Marketplaceio.github.ClawCall-Dev/clawcallio.github.handset-hq/handset
Official MCP Registry Listed
Version: 0.2.0
Downloads/month (npm): 198
Downloads/week (npm): 34
Forks (GitHub): 1
Stars (GitHub): 9
Not marked · First seen
Listed
Version: 0.1.1
Downloads/month (npm): 140
Downloads/week (npm): 21
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

io.github.ClawCall-Dev/clawcall vs io.github.handset-hq/handset
Factio.github.ClawCall-Dev/clawcallio.github.handset-hq/handset
Marketplaces that list it11
Stars (GitHub) (differs)9 (better)1 (worse)
Forks (GitHub) (differs)1 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (api.clawcall.dev/mcp)On your machine (@handset/mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for2, secrets among them: 12, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/clawcall-dev/clawcallgithub.com/handset-hq/handset-ui
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 4 days ago, requires a keyno remote endpoint we check

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

io.github.ClawCall-Dev/clawcall

In its own words, on Official MCP Registry:

Real US phone calls for AI agents: navigates phone menus, waits on hold, returns transcripts.

io.github.handset-hq/handset

In its own words, on Official MCP Registry:

A business phone system for AI agents: send texts, place calls, read transcripts, buy numbers.

How to run each

io.github.ClawCall-Dev/clawcall As a remote MCP server

Claude Code
claude mcp add --transport http clawcall https://api.clawcall.dev/mcp

Requires: CLAWCALL_API_KEY (secret)

io.github.handset-hq/handset As a local MCP server: npm package

Claude Code
claude mcp add --env "HANDSET_API_KEY=<YOUR_HANDSET_API_KEY>" --transport stdio handset -- npx -y @handset/mcp

Requires: HANDSET_API_KEY (secret)

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

Only io.github.ClawCall-Dev/clawcall 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

Only io.github.ClawCall-Dev/clawcall asks for

  • CLAWCALL_API_KEY (secret)
  • CLAWCALL_BASE_URL

Only io.github.handset-hq/handset asks for

  • HANDSET_ALLOW_LIVE
  • HANDSET_API_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: io.github.ClawCall-Dev/clawcall · What it can do: io.github.handset-hq/handset · Compare two other plugins

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