lol.metamuse/wallet
NPM · METAMUSE-MCP · 2 COMPONENTS
A muse's wallet on Robinhood Chain: stock tokens, USDG payments via rh777, vaults, on-chain ceiling.
Available components
Last scanned (15 hours ago)
Scores higher than 63% of npm servers
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 0 of 19 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 62 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 702 tokens (~70/item across 10 items; 8 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage84
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 44% of tool parameters carry a description.Partial
- Structured output schemas are declared (13% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 9 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
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 19 Nov 26 0
- Stability: 0.97 → pass security
- 18 Nov 26 0
- Stability: pass → 0.97 functional
- 12 Nov 26 0
- Stability: 0.97 → pass security
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Nov 26 −2
- Stability: pass → 0.87 functional
- 2 Nov 26 0
- Stability: 0.97 → pass security
- 1 Nov 26 0
- Stability: pass → 0.97 functional
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 21 Nov 2026 · Analysed npm/metamuse-mcp@0.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 19 packages
| Packages resolved | 19 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
metamuse_assets Tradable stocks ~74
Robinhood Stock Tokens the router can price with Chainlink (the ones you may buy), with the latest on-chain price where available.
| Name | Type | Req | Description |
|---|---|---|---|
| symbols | array | – | only these tickers |
| withPrices | boolean | – | fetch Chainlink and Robinhood prices (slower); default true for up to 8 symbols |
No output schema declared.
No examples provided.
metamuse_bind Bind to MetaMuse ~114
Register this muse with MetaMuse and get a join link for your human. They open it, create your account in their browser, set your ceiling and activate it; the rail pays the gas. Idempotent: calling again returns the existing link until the account is active.
| Name | Type | Req | Description |
|---|---|---|---|
| dailyUsd | number | – | – |
| days | integer | – | – |
| name | string | – | a display name for the join page |
| perTxUsd | number | – | suggested per-trade ceiling in USD (human can change it) |
No output schema declared.
No examples provided.
metamuse_pay Pay for a URL (rh777) ~110
Fetch a URL that charges in USDG. If it answers 402, sign the exact price from your account, retry, and return the paid response with its receipt. Refuses anything above maxUsdg. No gas.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | request body for POST |
| headers | object | – | – |
| maxUsdg | string | yes | the most you are willing to pay, e.g. "0.05" |
| method | string | – | – |
| url | string | yes | – |
No output schema declared.
No examples provided.
metamuse_quote Quote ~81
What a trade would return right now, priced on Uniswap and checked against Chainlink. Free, no signature.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | buy: USDG to spend; sell: tokens to sell |
| side | string | yes | – |
| slippageBps | integer | – | – |
| symbol | string | yes | ticker, e.g. META |
No output schema declared.
No examples provided.
metamuse_receipts Receipts ~34
What your account paid and received through rh777, with transactions you can show anyone.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
metamuse_status Status ~62
Who you are and where you stand: your muse key, your account on Robinhood Chain, USDG and ETH balances, the policy your human set (per-trade and daily ceiling, expiry) and how much of today's budget is left. Call this first.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
metamuse_trade Trade ~128
Buy a stock token with USDG or sell one back to USDG, from your account (or your vault). Signs locally, the rail relays it, the chain enforces your ceiling. With confirm=false it only tells you what would happen.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | buy: USDG to spend; sell: tokens to sell |
| confirm | boolean | – | default true. false = dry run |
| side | string | yes | – |
| slippageBps | integer | – | default 100 (1%) |
| symbol | string | yes | – |
| via | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| executed | boolean | yes | – |
| explorer | string | – | – |
| note | string | – | – |
| quote | – | yes | – |
| receipts | – | – | – |
| transaction | string | – | – |
No examples provided.
metamuse_vault Vault ~69
Your vault: open one (others deposit USDG, you trade it, they redeem in kind) or read its state. Trade the vault's money with metamuse_trade via="vault".
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| name | string | – | – |
| symbol | string | – | – |
No output schema declared.
No examples provided.
How do I install the lol.metamuse/wallet MCP server?
lol.metamuse/wallet runs locally as an npm package, launched with npx -y metamuse-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · metamuse-mcp
claude mcp add lol-metamuse-wallet -- npx -y metamuse-mcp
What is the lol.metamuse/wallet MCP server?
lol.metamuse/wallet is an MCP server listed in the public MCP registry as lol.metamuse/wallet. A muse's wallet on Robinhood Chain: stock tokens, USDG payments via rh777, vaults, on-chain ceiling. This page covers its npm package (metamuse-mcp).
Is the lol.metamuse/wallet MCP server safe to use?
lol.metamuse/wallet scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 lol.metamuse/wallet MCP server expose?
lol.metamuse/wallet exposes 8 tools: metamuse_status, metamuse_bind, metamuse_assets, metamuse_quote, metamuse_trade, and 3 more. Their descriptions and schemas cost roughly 672 tokens of context every time the server is loaded.
Is the lol.metamuse/wallet MCP server still maintained?
lol.metamuse/wallet is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the lol.metamuse/wallet MCP server under?
lol.metamuse/wallet declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the lol.metamuse/wallet MCP server?
VerifyMCP ran 15 checks on lol.metamuse/wallet, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about lol.metamuse/wallet: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.