Pulse Verity vs Crypto Pulse
Pulse Verity is an MCP server published by PulseBet. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). Crypto Pulse is an MCP server published by midnight232. Marketplaces we read that list it: 1 (Official MCP Registry). 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
| Marketplace |  Pulse Verity |  Crypto Pulse |
|---|---|---|
| Official MCP Registry | Listed Version: 1.3.6 Downloads/month (npm): 1 042 Downloads/week (npm): 192 Forks (GitHub): 0 Stars (GitHub): 4 Not marked · First seen |
Listed Version: 0.7.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| npm registry (MCP servers) | Listed Version: 1.3.6 Downloads/month (npm): 1 042 Downloads/week (npm): 192 Forks (GitHub): 0 Stars (GitHub): 4 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
| Fact | Pulse Verity | Crypto Pulse |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 4 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-10-19 (worse) | 2026-11-03 (better) |
| Where it runs (differs) | Remote server or your machine | Remote server (cryptopulseapi.com/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/pulsebet/pulse-verity | github.com/midnight232/crypto-pulse-api |
| Changes in the last 7 days (differs) | 0 | 3 |
| First seen (differs) | 2026-10-11 | 2026-10-31 |
| Endpoint at the last check (differs) | Responded 12 h ago | Responded 20 h 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
Signed Bitcoin and crypto prices for AI agents: multi-exchange prices anyone can verify offline.
Crypto Pulse
x402 Solana crypto pulse for agents + free BTC/ETH/SOL prediction arena
How to run each
Pulse Verity As a remote MCP server
claude mcp add --transport http pulse-verity https://mcp.thepulse.markets/api/index/mcpRequires: PULSE_API_KEY (secret)
Crypto Pulse As a remote MCP server
claude mcp add --transport http crypto-pulse https://cryptopulseapi.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints responded at the last daily check. How we check endpoints
Tools each declares
Neither the marketplaces of Crypto Pulse nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
The marketplaces of Crypto Pulse publish no settings it asks for, so we do not compare settings.
What it can do: Pulse Verity · What it can do: Crypto Pulse · 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.