Finance · Remote MCP server
Wallet
A muse's wallet on Robinhood Chain: stock tokens, USDG payments via rh777, vaults, on-chain ceiling.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
lol.metamuse/wallet- Version
- 0.1.2
- Status
- Active
- Category
- finance
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-09-19
- Updated
- 2026-09-19
- Publisher
- lol.metamuse
- Namespace
- Namespace verified by the MCP Registry via the domain metamuse.lol · how
- Website
- metamuse.lol/mcp/
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.metamuse.lol/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 502)
- Handshake
- HTTP 502
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | metamuse-mcp | 0.1.2 | stdio |
How to connect Wallet
Wallet is a remote MCP server: there is nothing to install. Its endpoint is https://api.metamuse.lol/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: metamuse-mcp version 0.1.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y metamuse-mcp@0.1.2. It reads these environment variables: METAMUSE_MAX_USD_PER_CALL and METAMUSE_HOME; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"wallet": {
"command": "npx",
"args": [
"-y",
"metamuse-mcp@0.1.2"
],
"env": {
"METAMUSE_MAX_USD_PER_CALL": "<value>",
"METAMUSE_HOME": "<value>"
}
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More finance servers
| Server | Runs |
|---|---|
| WafeqWafeq accounting API: all 251 endpoints as safety-categorized MCP tools, over stdio or HTTP. | Local · stdio |
| WagyuSwap crypto across chains, including Monero (XMR): quote, create and track swaps. | Remote · HTTPLive check: ✓ handshake |
| Wake Word TrainingTrain custom wake words from your agent: estimator, GPU training, benchmarks. Card or crypto. | Remote · HTTPLive check: ✓ handshake |
| WalleKPersonal finance ledger: log expenses, track bills and cards, import statements. | Remote · HTTPLive check: sign-in required |
| Wallet DoctorSolana wallet forensics SDK, x402 pay-per-call, AI agents. | Remote & Local · HTTP, stdioLive check: ✗ no handshake |
| Wallet Doctor x402Multi-chain wallet MCP. 18 tools: balance, swap, bridge, stake, claim. Pay-per-call USDC (x402 v2). | Remote · HTTPLive check: ✓ handshake |
| Wallet Portfolio Tracker APICrypto wallet balances, ERC-20 tokens, USD values across Base and Ethereum. x402. | Remote · SSELive check: ✗ no handshake |
| Wallet TrackerKOL and money wallet tracking on 5 chains: live trades, PnL, signals, Jito bundle detection. | Remote · HTTPLive check: ✓ handshake |