Hash Encoding Direct Credits vs Ethereum Keystore Encryption
Hash Encoding Direct Credits is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑14.
Hash Encoding Direct Credits is an MCP server published by PGhannmmn. No marketplace we read lists it any more. Ethereum Keystore Encryption is an MCP server published by nirholas. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. 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 |  Ethereum Keystore Encryption | |
|---|---|---|
| Official MCP Registry | Removed on 2026-10-14 Version: 0.1.0 No figure published Not marked · First seen |
Listed Version: 1.0.0 Downloads/month (PyPI): 64 Downloads/week (PyPI): 29 Forks (GitHub): 5 Stars (GitHub): 29 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 | Hash Encoding Direct Creditsno longer listed · | Ethereum Keystore Encryption |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 29 |
| Forks (GitHub) (differs) | No figure on GitHub | 5 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (hash-encoding-001d.qqqa16521-dce.workers.dev/mcp) | On your machine (keystore-mcp-server) |
| 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) | Not stated | github.com/nirholas/ethereum-wallet-toolkit |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 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 Hash Encoding Direct Credits
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Skavio USDC Payment Verification & Proof MCP
USDC x402 proof/DNS and authenticated prepaid OCR, document and audio processing via card or USDC.
-
70+ pay-per-call security, crypto, and data tools for AI agents via x402 USDC micropayments on Base
-
mcp-signer io.github.CryptoAPIs-io/mcp-signer
Local transaction signing for EVM, UTXO, Tron, XRP, Kaspa, Solana and Tezos — no API calls
-
mcp-utils io.github.CryptoAPIs-io/mcp-utils
MCP server for address derivation and encoding utilities across multiple blockchains via Crypto APIs
-
geld machen x402 agent utilities
x402 pay-per-call agent tools (Base USDC): web search, URL extract, OCR, Base tx & allowance scans
-
hederatoolbox io.github.mountainmystic/hederatoolbox
Hedera blockchain intelligence for AI agents. 23 tools, 7 modules. HBAR micropayments. No signup.
What each says it does
Hash Encoding Direct Credits
Deterministic SHA, HMAC, Base64 and JWT decode tools with prepaid direct-USDC API credits on Base.
Ethereum Keystore Encryption
Encrypt/decrypt Ethereum keystore JSON V3 with scrypt/PBKDF2 for secure cold storage
How to run each
Hash Encoding Direct Credits
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Ethereum Keystore Encryption As a local MCP server: PyPI package
claude mcp add --transport stdio keystore-mcp-server -- uvx keystore-mcp-serverCommands 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
Neither one's marketplaces publish the settings it asks for.
What it can do: Hash Encoding Direct Credits · What it can do: Ethereum Keystore Encryption · 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.