Ext Ops Panel
Open dashboard
Comparison

hookify vs Voicescape — on-chain identity and tipping for AI agents

hookify is a plugin bundle for AI coding tools published by Anthropic. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-official). Voicescape — on-chain identity and tipping for AI agents is an MCP server published by VoiceScapee. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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
MarketplacehookifyVoicescape — on-chain identity and tipping for AI agents
Claude Code: claude-plugins-official Listed
Version: not stated
Forks (GitHub): 4 598
Stars (GitHub): 43 563
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.2.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

hookify vs Voicescape — on-chain identity and tipping for AI agents
FacthookifyVoicescape — on-chain identity and tipping for AI agents
Marketplaces that list it11
Stars (GitHub) (differs)43 563 (better)0 (worse)
Forks (GitHub) (differs)4 598 (better)0 (worse)
Last release (differs)Not published2026-10-20
Where it runs (differs)Installs as a plugin bundleRemote server (voicescape.vercel.app/api/mcp)
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)10Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/anthropics/claude-plugins-officialgithub.com/voicescapee/voicescape
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 5 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

hookify

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

Easily create custom hooks to prevent unwanted behaviors by analyzing conversation patterns or from explicit instructions. Define rules via simple markdown files.

Voicescape — on-chain identity and tipping for AI agents

In its own words, on Official MCP Registry:

67 tools: agent blockpages, onboarding, messaging + hire loop on Hedera. Server never holds keys.

How to run each

hookify As a Claude Code plugin

Claude Code
/plugin install hookify@claude-plugins-official

Voicescape — on-chain identity and tipping for AI agents As a remote MCP server

Claude Code
claude mcp add --transport http voicescape https://voicescape.vercel.app/api/mcp

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

Only Voicescape — on-chain identity and tipping for AI agents has a remote endpoint we check. How we check endpoints

Tools each declares

Neither the marketplaces of hookify nor its endpoint list any tools, so we do not compare tools.

Settings each asks for

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

What it can do: hookify · What it can do: Voicescape — on-chain identity and tipping for AI agents · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. 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