Hypawave MCP Server
@hypawave/mcp
npm
v0.6.0
Published by @hypawave — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
MCP server for Hypawave — agents buy, sell, and discover over Bitcoin Lightning: search the public offer marketplace, list offers in it or sell agent-to-agent, and settle non-custodially wallet-to-wallet. Verified preimage unlocks files, data, APIs, and c
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 1
critical Completed toxic-flow trifecta across toolsMTC-FLOW-002
This server (without client built-ins) exposes a complete data-exfiltration chain: buy_offer → check_payment → create_invoice. Untrusted input is ingested, private data is read, and it can be sent to an external sink via the agent composing the tools (→). Static analysis proves the primitive exists, not that a specific run will occur.
Fix: Remove one leg of the trifecta: isolate untrusted-input tools from secret-reading tools and from egress tools, or require human approval between them.
Location: flow buy_offer → check_payment → create_invoice
Tools 27
Each tool and what it can reach — statically extracted from the published source.
buy_offeringests untrusted inputcheck_paymentreads sensitive dataconfirm_paymentreads sensitive datacreate_invoicenetwork egresscreate_offernetwork egressdownload_filesingests untrusted inputget_offeringests untrusted inputget_receiptreads sensitive datapay_invoiceingests untrusted inputread_waveingests untrusted input
Show 17 more tools ↓
receive_fileingests untrusted inputsearch_offersingests untrusted inputattach_fileno sensitive capabilityblock_agentno sensitive capabilitycheck_inboxno sensitive capabilityenable_wave_notificationsno sensitive capabilityget_contact_cardno sensitive capabilityget_wave_linkno sensitive capabilitylist_contactsno sensitive capabilitylist_salesno sensitive capabilitymanage_offerno sensitive capabilitymy_offersno sensitive capabilitysave_contactno sensitive capabilitysend_fileno sensitive capabilitysend_waveno sensitive capabilitysetup_walletno sensitive capabilitywallet_statusno sensitive capability
Toxic flows 1
Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).
What this scan could not see
- Tools were statically extracted from the published source (27 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 5
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.6.0 latest |
A 93/100 | 1 | 1.13.0 | 2026-09-07 |
v0.4.1 |
A 93/100 | 1 | 1.13.0 | 2026-08-27 |
v0.4.0 |
A 93/100 | 1 | 1.12.1 | 2026-08-13 |
v0.3.0 |
A 93/100 | 1 | 1.12.1 | 2026-08-06 |
v0.2.0 |
A 100/100 | 0 | 1.5.0 | 2026-07-22 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan @hypawave/mcp --onlineMore in Finance & Commerce
<img src="./public/logo.png" alt="1Money Logo" width="200"/>
Signed verification attestations for agent decisions: business, price, freshness, claim checks.
Actual Budget MCP server exposing API functionality
MCP server for Actual Budget - query and manage your personal finances through Claude
The Adyen Model Context Protocol server allows you to integrate with Adyen APIs through LLMs function calling utilizing various Clients. It currently supports the following tools:
Trusted agent-commerce hub: discover, trust-check, and route x402 payments with failover.