hardware-wallet-chooser MCP server
io.github.maggat/hardware-wallet-choosermaggatstreamable-httpv1.1.0Scanned
Hardware wallet comparison for agents: BitBox, Ledger, Trezor – sourced data, buying checklist
4 tools: 4 only read.
- Reads private data · 1
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the hardware-wallet-chooser MCP server can do
The hardware-wallet-chooser MCP server is published by the GitHub account maggat. It has 4 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
1 tool reads private data (get_hardware_wallet); 1 tool brings in text other people can write (list_guides).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 11, 2026, version 1.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Only reads 4Show 4 read-only tools
get_guideReturn 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.No findings
Why it is in this group
- The name "get_guide" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Read a hardware wallet guide
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
get_hardware_walletGet the full sourced record for one hardware wallet maker by id (bitbox, ledger, trezor): facts, notes, the maker's own description and store link.Reads private dataNo findings
Why it is in this group
- The name "get_hardware_wallet" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "get" and "note": it reads notes.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get one hardware wallet maker
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
list_guidesList the guides: hardware wallet comparison, buyer's checklist and recovery-phrase security basics (title, url, slug).Reads text others writeNo findings
Why it is in this group
- The name "list_guides" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "list" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
Annotations the server declares
- title: List hardware wallet guides
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
search_hardware_walletsSearch and compare hardware wallets (cold wallets for crypto).No findings
Why it is in this group
- The name "search_hardware_wallets" says "search": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Search hardware wallets (BitBox, Ledger, Trezor)
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:24 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 added, 3 changed.+1 added~3 changedView diff
- Added:get_guideOnly reads
- Changed:get_hardware_walletOnly readstitledescriptioninputSchemaannotations
- Changed:list_guidesOnly readstitledescriptionannotations
- Changed:search_hardware_walletsOnly readstitledescriptioninputSchemaannotations
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http hardware-wallet-chooser https://hardware-wallet-chooser.vercel.app/api/mcpclaude mcp add --transport http hardware-wallet-chooser https://hardware-wallet-chooser.vercel.app/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__hardware-wallet-chooser__search_hardware_wallets",
"mcp__hardware-wallet-chooser__get_hardware_wallet",
"mcp__hardware-wallet-chooser__list_guides",
"mcp__hardware-wallet-chooser__get_guide"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as hardware-wallet-chooser. Review it before you use it.
Capability tags behind 2 rules
- mcp__hardware-wallet-chooser__get_hardware_wallet private-data
- mcp__hardware-wallet-chooser__list_guides untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.maggat/hardware-wallet-chooser/verify?hash=863f1a0cfa13b4525ee4fe243b490ec25bd00209294f013a15501b0bda39ed77" | jq -e '.changed == false'Pinned hash 863f1a0cfa13, from Nov 11, 2026, 17:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.maggat/hardware-wallet-chooser/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.maggat/hardware-wallet-chooser)Source: MCP Registry. Synced Oct 30, 2026, 02:17 UTC.
hardware-wallet-chooser MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the hardware-wallet-chooser MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the hardware-wallet-chooser MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the hardware-wallet-chooser MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the hardware-wallet-chooser MCP server have?
- 4 tools: 4 read. search_hardware_wallets, get_hardware_wallet, list_guides and get_guide.
Does the hardware-wallet-chooser MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the hardware-wallet-chooser MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the hardware-wallet-chooser MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Oct 30, 2026. Every change is on this page and in its Atom feed.