Finance · Remote MCP server
WalletWallet: Apple and Google Wallet passes
Create, update, and revoke Apple Wallet and Google Wallet passes from any MCP client.
Visit WalletWallet: Apple and Google Wallet passes's website
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
dev.walletwallet/wallet-passes- Version
- 1.0.0
- Status
- Active
- Category
- finance
- Transport
- Streamable HTTP
- Published
- 2026-09-17
- Updated
- 2026-09-17
- Publisher
- dev.walletwallet
- Namespace
- Namespace verified by the MCP Registry via the domain walletwallet.dev · how
- Website
- www.walletwallet.dev/integrations/
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.walletwallet.dev/mcp | Authorization (secret) |
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 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect WalletWallet: Apple and Google Wallet passes
WalletWallet: Apple and Google Wallet passes is a remote MCP server: there is nothing to install. Its endpoint is https://api.walletwallet.dev/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.
The registry entry declares an HTTP header for the connection: Authorization (secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
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 |
|---|---|
| Walletconnect MCPNon-custodial EVM wallet bridge over WalletConnect: balances, signing, transactions. | Local · stdio |
| WalletlensEVM wallet reports and Robinhood Stock Token intelligence paid with USDC over x402. | Local · stdio |
| walletlink.socialResolve wallet addresses to X and Farcaster accounts, and back again. | Remote · HTTPLive check: ✓ handshake |
| WalletTriageReal-time exploit-exposure risk check for EVM wallets, paid per query via x402 (USDC on Base). | Local · stdio |
| WarmContext and automation MCP server for Warm financial data and approved write operations. | Local · stdio |
| WarpSIP trunking, numbers, porting, messaging, billing, and CDR analytics on the Ringer WARP platform. | Local · stdio |
| WasselMENA commerce integration layer for AI agents: payments, BNPL, logistics, e-commerce, tax. | Remote · HTTPLive check: sign-in required |
| WatchdogWho can change a Solana program or EVM contract, dependency advisories, scans. Paid per call (x402). | Local · stdio |