OurPay Wallet
io.github.OurpayPublished by GitHub account Ourpayv0.10.0Updated Oct 24, 2026
Crypto wallet for AI agents: balances, payments, swaps and trading with owner controls.
Overview
A remote crypto wallet MCP server that lets an AI assistant check balances, send transfers, swap, fund gas, make merchant purchases and trade on Hyperliquid, g.
- What you can do
- Read wallet state: account sign-in, EVM and Solana addresses, supported networks and assets, balances, market feeds and Hyperliquid market, book, candle and account data. Move funds: native, ERC-20 and SPL transfers with receipt tracking and retries, same-chain swaps and cross-chain routes with output, slippage and fee limits, and funding quotes for gas or Hyperliquid collateral. Shop and pay: search OurPay products, open checkouts, prepare crypto invoices, quote, convert and pay, and track orders, including bounded USDC subscriptions. Trade: Hyperliquid spot and perpetual orders with leverage, margin, stop-loss and take-profit, cancellation and fills, plus server-run bounded trading plans.
- When to use it
- Use it when an assistant should operate a real crypto wallet under owner control: checking balances and markets, paying merchants, moving or swapping funds, or placing trades on Hyperliquid. It suits users who want one account-owned wallet shared across several AI hosts with separately revocable connections.
- Requirements
- A remote Streamable HTTP endpoint with OAuth sign-in to the OurPay account that owns the wallet; no API key or npm install is needed. Local packages require Node.js 24 or newer. The wallet must be funded on the chosen network, and availability depends on enabled networks, assets, liquidity and owner permissions.
Installation
In SourceWeft
- Open OurPay Wallet in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.Ourpay%2Fourpay-wallet/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"ourpay-wallet": {
"type": "http",
"url": "https://mcp.ourpay.dev/wallet/mcp"
}
}
}README
OurPay Wallet
One account-owned crypto wallet for you and your authorized AI agents. Sign in to the same OurPay account from ChatGPT, Claude, a coding agent or a compatible application to use the same wallet, with separately revocable connections.
57 tools · 6 native packages · 18 client profiles · 5 model tool formats · 4 framework examples
Open wallet · Connect an agent · Release downloads · All tools
What it can do
Availability depends on enabled networks, exact assets/markets, liquidity, provider/venue state and owner permissions. General wallet signing is not a complete integration with every dApp. Persistent plans execute bounded instructions; they do not host an LLM that invents or revises strategies. Complete Polymarket trading, arbitrary internet checkout and fiat/card/UPI payments remain outside the wallet. Full capability boundaries.
Connect with OAuth
Add this Streamable HTTP MCP server to a host that supports remote MCP with OAuth:
Use the full /wallet/mcp path. Follow OurPay sign-in and consent, using the account that owns your wallet. The host's plan, version and administrator settings can affect connector availability. Custom-connector support and repository installation are separate from vendor public-directory approval.
Then ask:
Call
ourpay_wallet_guidewith topicoverview, then read my wallet and supported networks. Do not submit any payment, signature or trade.
The guide provides task-specific instructions. A fresh 0.11.0 catalog has 57 tools: three checkout tools and 54 wallet tools. Purchase tools support bounded USDC subscriptions with explicit recurring consent and automatic settlement progress. Restart a host that cached an older schema; update the executable as well if using a local package. An ordinary tool update does not require a new wallet. Refresh and troubleshooting.
Install in coding agents
Local packages require Node.js 24 or newer and include the MCP runtime. The server does not need a merchant API key or an npm install to run. Its first wallet call returns account authorization; it does not ask for your recovery phrase.
Claude Code
Codex
Add the public repository marketplace, then install ourpay-wallet from OurPay in the plugin browser:
Gemini CLI
GitHub Copilot CLI
The repository root implements the portable Agent Plugins format:
Cursor and Claude Desktop
Use their native release packages from downloads. Cursor includes a local plugin manifest; Claude Desktop uses .mcpb. If a managed runtime is older than Node 24, use the generated configuration with a compatible external Node executable.
OpenCode and other hosts
OpenCode can use the hosted OAuth URL directly. The complete integrations archive generates profiles for Codex, Claude Code, Claude Desktop, Cursor, VS Code/Copilot, Windsurf, Cline, Roo Code, Continue, Gemini CLI, OpenCode, Kiro, Goose, Zed, Copilot CLI, LM Studio, Kilo and generic MCP clients.
From the complete extracted bundle:
Merge the generated server entry into your existing configuration. Do not replace unrelated servers. Private local connection files must remain on your machine and persist across restarts. The SDK is not published on npm; do not use npx @ourpay/agent-wallets as an installation method. Complete integration instructions.
Fund once, then authorize the task
Send the correct asset to the wallet address for your chosen network. EVM networks share one EVM address; Solana uses another. Every chain's balance remains separate.
Agents can use native USDC on enabled Ethereum, Optimism, Polygon, Base, Arbitrum and Avalanche networks to obtain gas or mainnet Hyperliquid collateral through supported funding routes. Fees come from the authorized USDC input. Routes, minimum sizes and liquidity still matter; this does not provide free gas or universal support for every chain. Solana can receive gas through supported routes but is not a zero-SOL USDC gasless source.
HyperCore exchange collateral, HyperEVM HYPE and on-chain USDC are distinct balances. A funding quote does not prove delivery, and an exchange account value does not mean all collateral is withdrawable. Funding and settlement workflow.
Permissions and recovery
Standard mode requires owner review for new payments, trades, contract submissions, signatures and app connections. OurPay sends an email review link and returns the owner URL to the agent. The default $10,000 daily USD allowance is shared across agents and resets at 00:00 UTC; owners can adjust it. Reservations are authorization estimates, not maximum-loss guarantees.
Owner-enabled Risky mode skips supported per-action approvals and shared spending restrictions. Pause, revocation, supported-action validation and the host's own controls still apply. It does not authorize an agent to invent a trading strategy or spend outside your task.
Save the initial recovery phrase privately. You can reveal it later in wallet Settings after recent owner authentication. OurPay retains an encrypted backup; the owner-held phrase is an independent backup. Agents never receive it. Recovery preserves addresses and revokes prior connections. Owner guide.
Agent and developer documentation
Model adapters support OpenAI Responses, Chat Completions-compatible function tools, Anthropic Messages, Gemini and tool-capable Ollama models. Framework examples cover OpenAI Agents SDK, LangChain/LangGraph, PydanticAI and Google ADK. The application supplies its model credentials, tool filters and execution loop; the wallet does not select a model or run a strategy for it.
Source and verification
Build the distributed SDK source with Node 24+:
The application repository owns the full tests and generation pipeline; this public repository includes the SDK source, plugin manifests, packaged runtime and documentation. Local packaging/schema/fixture tests, live read checks and funded execution are different evidence. See the v0.10.0 release verification for live deployments, all 57 tools observed in ChatGPT, snapshot benchmarks and the funded acceptance tests that remain unverified. Earlier release evidence remains in TESTING.md.
Documentation on main can be newer than a tagged package. Tags, archives and checksums remain fixed; changes to this README do not upgrade an installed executable. Pin a reviewed tag/commit for reproducible Git installs and use the matching release archive when updating a runtime.
Licensed under Apache-2.0. Bundled dependencies are documented in THIRD_PARTY_NOTICES.txt. No recovery phrase, connection credential or backend custody secret belongs in this repository.
Source: README.md at commit 2f4d6dc
Tools
0Version history
2- v0.10.0LatestSep 27, 2026
- v0.9.1Sep 26, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
