Pulse Verity vs x402 SEC, DeFi and Bittensor data
Pulse Verity is an MCP server published by PulseBet. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). x402 SEC, DeFi and Bittensor data is an MCP server published by overwatchdominion-stack. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-05. 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 |  x402 SEC, DeFi and Bittensor data |
|---|---|---|
| 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.1.0 Forks (GitHub): 0 (last published figure) Stars (GitHub): 0 (last published figure) 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 | x402 SEC, DeFi and Bittensor data |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 4 | 0 (last published figure) |
| Forks (GitHub) (differs) | 0 | 0 (last published figure) |
| Last release (differs) | 2026-10-19 | Not published |
| Where it runs (differs) | Remote server or your machine | On your machine (https://github.com/overwatchdominion-stack/x402-sec-defi-data-mcp/releases/download/v0.1.0/x402-sec-defi-data-mcp-0.1.0.mcpb) |
| Transport (differs) | Streamable HTTP | stdio |
| 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/overwatchdominion-stack/x402-sec-defi-data-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-22 |
| Endpoint at the last check (differs) | Status out of date: last check 4 days ago returned HTTP 405 | no 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
Pulse Verity
Signed Bitcoin and crypto prices for AI agents: multi-exchange prices anyone can verify offline.
x402 SEC, DeFi and Bittensor data
25 pay-per-call x402 tools (USDC on Base): SEC EDGAR, 8-K feed, DeFi math, Bittensor.
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)
x402 SEC, DeFi and Bittensor data
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Pulse Verity has a remote endpoint we check. How we check endpoints
Tools each declares
Neither the marketplaces of x402 SEC, DeFi and Bittensor data nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
The marketplaces of x402 SEC, DeFi and Bittensor data publish no settings it asks for, so we do not compare settings.
What it can do: Pulse Verity · What it can do: x402 SEC, DeFi and Bittensor data · 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.