com.theaslangroupllc.pulse/pulsenetwork vs OpenPulsechain Analytics
com.theaslangroupllc.pulse/pulsenetwork is an MCP server published by pulse.theaslangroupllc.com. Marketplaces we read that list it: 1 (Official MCP Registry). OpenPulsechain Analytics is an MCP server published by openpulsechain. 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 |  com.theaslangroupllc.pulse/pulsenetwork |  OpenPulsechain Analytics |
|---|---|---|
| Official MCP Registry | Listed Version: 1.4.0 Forks (GitHub): 1 Stars (GitHub): 3 Not marked · First seen |
Listed Version: 2.1.0 Downloads/month (npm): 228 Downloads/week (npm): 119 Forks (GitHub): 1 Stars (GitHub): 3 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
| Fact | com.theaslangroupllc.pulse/pulsenetwork | OpenPulsechain Analytics |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 3 | 3 |
| Forks (GitHub) | 1 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (pulse.theaslangroupllc.com/api/mcp) | On your machine (@openpulsechain/mcp-server) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/gtcc777/mcp-pulsenetwork | github.com/openpulsechain/public |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Status out of date: no HTTP response at the last check 4 days ago | 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
com.theaslangroupllc.pulse/pulsenetwork
914 paid market-data & token-safety endpoints — keyless x402 USDC: Base, Solana, XRPL, +8 chains
OpenPulsechain Analytics
PulseChain analytics: 28 tools — safety scores, signals, whale alerts, pair analytics, AML.
How to run each
com.theaslangroupllc.pulse/pulsenetwork As a remote MCP server
claude mcp add --transport http pulsenetwork https://pulse.theaslangroupllc.com/api/mcpOpenPulsechain Analytics As a local MCP server: npm package
claude mcp add --env "OPENPULSECHAIN_API_KEY=<YOUR_OPENPULSECHAIN_API_KEY>" --transport stdio analytics -- npx -y @openpulsechain/mcp-serverRequires: OPENPULSECHAIN_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only com.theaslangroupllc.pulse/pulsenetwork 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
The marketplaces of com.theaslangroupllc.pulse/pulsenetwork publish no settings it asks for, so we do not compare settings.
What it can do: com.theaslangroupllc.pulse/pulsenetwork · What it can do: OpenPulsechain Analytics · 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.