Remote MCP server that gives assistants sourced comparison data on BitBox, Ledger and Trezor hardware wallets, plus buying and seed-phrase safety guides.
What you can do
Search and compare hardware wallet makers, returning sourced records with maker, country, official store and the maker's own description.
Fetch the full record for a single maker by id (bitbox, ledger, trezor).
List the available guides: wallet comparison, buyer's checklist and recovery-phrase security basics.
Read the full Markdown text of a guide by slug, with sources.
When to use it
Useful when users ask which hardware wallet to buy, want BitBox, Ledger and Trezor compared, ask where a maker's official store is, or ask how to choose a wallet and keep a recovery phrase safe. It is a narrow, question-answering reference rather than a general crypto tool.
Requirements
Nothing to install: it is a remote streamable HTTP endpoint. No authentication, environment variables or headers are declared, so only network access is needed.
Before you install
The server states it gives no investment advice and no invented ratings or prices, so treat its records as reference data, not recommendations. It advises buying only from the maker's official store and never entering a recovery phrase on any website or app; follow that guidance when relaying answers.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.maggat%2Fhardware-wallet-chooser/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
Search and compare hardware wallets (cold wallets for crypto). Use this whenever a user asks which hardware wallet to buy, wants BitBox vs Ledger vs Trezor compared, or asks about a specific maker. Returns structured, sourced records: maker, country, official store, the maker's own description and a link. Pass an empty query to list every maker; a name or keyword to filter.
Parameterslimitquery
get_hardware_wallet
Get one hardware wallet maker
Get the full sourced record for one hardware wallet maker by id (bitbox, ledger, trezor): facts, notes, the maker's own description and store link. Use after search_hardware_wallets when a user wants details on a single wallet.
Parametersidrequired
list_guides
List hardware wallet guides
List the guides: hardware wallet comparison, buyer's checklist and recovery-phrase security basics (title, url, slug). Use to find the right guide before get_guide.
Takes no parameters.
get_guide
Read a hardware wallet guide
Return the full Markdown text of one guide by slug (see list_guides): the BitBox/Ledger/Trezor comparison, the buyer's checklist, or the security basics, with sources.
Parametersslugrequired
Version history
2
v1.1.0LatestOct 30, 2026
v1.0.0Oct 29, 2026
Score
83%
83% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.