Ext Ops Panel
Open dashboard
Comparison

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

Pulse Verity is an MCP server published by PulseBet. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). 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-23. 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
MarketplacePulse VerityVoicescape — on-chain identity and tipping for AI agents
Official MCP Registry Listed
Version: 1.3.6
Downloads/month (npm): 1 370
Downloads/week (npm): 629
Forks (GitHub): 0
Stars (GitHub): 3
Not marked · First seen
Listed
Version: 1.2.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
npm registry (MCP servers) Listed
Version: 1.3.6
Downloads/month (npm): 1 370
Downloads/week (npm): 629
Forks (GitHub): 0
Stars (GitHub): 3
Not marked · First seen
Not listed

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

Pulse Verity vs Voicescape — on-chain identity and tipping for AI agents
FactPulse VerityVoicescape — on-chain identity and tipping for AI agents
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)3 (better)0 (worse)
Forks (GitHub)00
Last release (differs)2026-10-19 (worse)2026-10-20 (better)
Where it runs (differs)Remote server or your machineRemote server (voicescape.vercel.app/api/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/pulsebet/pulse-veritygithub.com/voicescapee/voicescape
Changes in the last 7 days (differs)92
First seen2026-10-112026-10-11
Endpoint at the last check (differs)not checked yetResponded 6 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

Pulse Verity

In its own words, on Official MCP Registry:

Signed Bitcoin and crypto prices for AI agents: multi-exchange prices anyone can verify offline.

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

Pulse Verity As a remote MCP server

Claude Code
claude mcp add --transport http pulse-verity https://mcp.thepulse.markets/api/index/mcp

Requires: PULSE_API_KEY (secret)

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 Pulse Verity nor its endpoint list any tools, so we do not compare tools.

Settings each asks for

The marketplaces of Voicescape — on-chain identity and tipping for AI agents publish no settings it asks for, so we do not compare settings.

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

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