Chainstack vs io.github.CryptoAPIs-io/mcp-signer
Chainstack is an MCP server published by chainstack.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.CryptoAPIs-io/mcp-signer 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-15. 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 |  Chainstack |  io.github.CryptoAPIs-io/mcp-signer |
|---|---|---|
| Official MCP Registry | Listed Version: 1.11.1 Forks (GitHub): 0 Stars (GitHub): 4 Not marked · First seen |
Listed Version: 0.5.0 Downloads/month (npm): 953 Downloads/week (npm): 90 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 | Chainstack | io.github.CryptoAPIs-io/mcp-signer |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 4 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-10-12 | Not published |
| Where it runs (differs) | Remote server (mcp.chainstack.com/mcp) | On your machine (@cryptoapis-io/mcp-signer) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/chainstacklabs/mcp-server | github.com/cryptoapis-io/cryptoapis-mcp-signer |
| Changes in the last 7 days (differs) | 1 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 41 h 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
Chainstack
Deploy and manage blockchain nodes across 70+ protocols, search docs, request testnet funds.
io.github.CryptoAPIs-io/mcp-signer
Local transaction signing for EVM, UTXO, Tron, XRP, Kaspa, Solana and Tezos — no API calls
How to run each
Chainstack As a remote MCP server
claude mcp add --transport http chainstack https://mcp.chainstack.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
io.github.CryptoAPIs-io/mcp-signer As a local MCP server: npm package
claude mcp add --transport stdio mcp-signer -- npx -y @cryptoapis-io/mcp-signerCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Chainstack 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
Neither one's marketplaces publish the settings it asks for.
What it can do: Chainstack · What it can do: io.github.CryptoAPIs-io/mcp-signer · 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.