io.github.maggat/hardware-wallet-chooser
REMOTE · HARDWARE-WALLET-CHOOSER.VERCEL.APP
Hardware wallet comparison for agents: BitBox, Ledger, Trezor – sourced data, buying checklist
Available components
Last scanned (17 hours ago)
Scores higher than 69% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 571 tokens (~142/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +50
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.10 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 31 Oct 26 −49
- Endpoint reachability: reachable → not serving MCP ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.03 → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 30 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_hardware_wallet” rewrote its description, which is the text the model reads security
- Tool “list_guides” rewrote its description, which is the text the model reads security
- Tool “search_hardware_wallets” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Schema quality: good → excellent functional
- Server version: 1.0.0 → 1.1.0 functional
- New tool “get_guide” functional
- “search_hardware_wallets” reworded the description of “limit” cosmetic
- “search_hardware_wallets” reworded the description of “query” cosmetic
- Tool “get_hardware_wallet” changed its title: Get one hardware wallet maker cosmetic
- Tool “list_guides” changed its title: List hardware wallet guides cosmetic
- Tool “search_hardware_wallets” changed its title: Search hardware wallets (BitBox, Ledger, Trezor) cosmetic
- 29 Oct 26 73
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://hardware-wallet-chooser.vercel.app/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.vercel.app | CN=WR1,O=Google Trust Services,C=US | 31 Oct 2026 | 29 Jan 2027 | RSA 2048 | SHA256-RSA | 9c5f0e6a35c955e113044c86848e4cd5 |
| SANs: *.vercel.app | ||||||
| CN=WR1,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7fd9e2c2d2048a0474b627a26d0868a7 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of hardware-wallet-chooser.vercel.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| vercel.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://hardware-wallet-chooser.vercel.app/api/mcp | Verified | 200 | |
| http (plaintext) | http://hardware-wallet-chooser.vercel.app/api/mcp | HTTPS enforced | 308 | https://hardware-wallet-chooser.vercel.app/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_guide Read a hardware wallet guide ~62
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Guide slug from list_guides. |
No output schema declared.
No examples provided.
get_hardware_wallet Get one hardware wallet maker ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Listing id. |
No output schema declared.
No examples provided.
list_guides List hardware wallet guides ~44
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_hardware_wallets Search hardware wallets (BitBox, Ledger, Trezor) ~135
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results (default 20, max 50). |
| query | string | – | Optional filter: maker name or keyword (e.g. 'ledger', 'open source'). Empty returns all. |
No output schema declared.
No examples provided.
How do I install the io.github.maggat/hardware-wallet-chooser MCP server?
io.github.maggat/hardware-wallet-chooser is a hosted endpoint at https://hardware-wallet-chooser.vercel.app/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · hardware-wallet-chooser.vercel.app
claude mcp add --transport http maggat-hardware-wallet-chooser 'https://hardware-wallet-chooser.vercel.app/api/mcp'
What is the io.github.maggat/hardware-wallet-chooser MCP server?
io.github.maggat/hardware-wallet-chooser is an MCP server listed in the public MCP registry as io.github.maggat/hardware-wallet-chooser. Hardware wallet comparison for agents: BitBox, Ledger, Trezor – sourced data, buying checklist. This page covers its hosted endpoint (https://hardware-wallet-chooser.vercel.app/api/mcp).
Is the io.github.maggat/hardware-wallet-chooser MCP server safe to use?
io.github.maggat/hardware-wallet-chooser scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.maggat/hardware-wallet-chooser MCP server expose?
io.github.maggat/hardware-wallet-chooser exposes 4 tools: search_hardware_wallets, get_hardware_wallet, list_guides, get_guide. Their descriptions and schemas cost roughly 311 tokens of context every time the server is loaded.
Does the io.github.maggat/hardware-wallet-chooser MCP server require authentication?
No. We connected to io.github.maggat/hardware-wallet-chooser without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.maggat/hardware-wallet-chooser MCP server still maintained?
io.github.maggat/hardware-wallet-chooser is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.