blockvectra-rpc vs io.github.CryptoAPIs-io/mcp-transactions-data
blockvectra-rpc is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
blockvectra-rpc is a plugin bundle for AI coding tools published by blockvectra. No marketplace we read lists it any more. io.github.CryptoAPIs-io/mcp-transactions-data is an MCP server published by CryptoAPIs-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.CryptoAPIs-io/mcp-transactions-data | |
|---|---|---|
| Community marketplace blockvectra/mcp | Removed on 2026-10-15 Version: not stated Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.4.0 Downloads/month (npm): 446 Downloads/week (npm): 44 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
| Fact | blockvectra-rpcno longer listed · | io.github.CryptoAPIs-io/mcp-transactions-data |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@cryptoapis-io/mcp-transactions-data) |
| Transport (differs) | Not stated | 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/blockvectra/skills | github.com/cryptoapis-io/cryptoapis-mcp-transactions-data |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of blockvectra-rpc
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
BlockVectra: multi-chain RPC & Data API
Keyless multi-chain EVM JSON-RPC, indexed Data API, docs, CU pricing and status. API key optional.
-
Vibes-Coded Agent Security and Commerce Tools
Agent supply-chain security, scanner consensus, x402 reliability, and commerce MCP tools.
-
Deploy and manage blockchain nodes across 70+ protocols, search docs, request testnet funds.
-
FlexYield — blockchain RPC gateway
RPC gateway for agents: six mainnets, measured failover, a key without signup, pay per call in USDC.
-
nodeflare-mcp io.github.Nodeflare-app/nodeflare-mcp
Blockchain JSON-RPC on 23 EVM chains for AI agents - free tier, API key, or x402 pay-per-call.
-
Self-custodial crypto + DeFi MCP for AI agents. Ledger-signed. EVM, TRON, Solana, BTC, LTC.
What each says it does
blockvectra-rpc
Agent skill for BlockVectra: keyless EVM JSON-RPC, Data API, programmatic sign-up, pricing and top-up.
io.github.CryptoAPIs-io/mcp-transactions-data
MCP server for transaction lookup across EVM, UTXO, Solana, XRP, Kaspa via Crypto APIs
How to run each
blockvectra-rpc
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.CryptoAPIs-io/mcp-transactions-data As a local MCP server: npm package
claude mcp add --env "CRYPTOAPIS_API_KEY=<YOUR_CRYPTOAPIS_API_KEY>" --transport stdio mcp-transactions-data -- npx -y @cryptoapis-io/mcp-transactions-dataRequires: CRYPTOAPIS_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
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 blockvectra-rpc publish no settings it asks for, so we do not compare settings.
What it can do: blockvectra-rpc · What it can do: io.github.CryptoAPIs-io/mcp-transactions-data · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.