
Kipurse
com.kipursePublished by kipurse.comOfficial publisherv0.1.0Updated Nov 4, 2026
Self-custodial USDC wallet on Base for AI agents: on-chain caps, Face ID, one-tap pause.
Overview
Remote MCP server for Kipurse, a self-custodial USDC wallet on Base that lets an AI agent make small payments within owner-set caps.
- What you can do
- Let an assistant make USDC payments from the user's own Base smart wallet, within hard daily and per-payment caps.
- Route payments above the caps or to new recipients to the owner for Face ID approval on an iPhone.
- Stop all AI-initiated payments, including Siri, with a single pause switch.
- Keep keys in the iPhone Secure Enclave and let the owner withdraw everything even if the Kipurse server is down.
- When to use it
- For people who want an AI agent to pay small amounts in USDC on Base while keeping self-custody and hard spending limits, with owner approval for anything unusual.
- Requirements
- A remote Streamable HTTP endpoint with OAuth sign-in; no local package or environment variables. An iPhone with the Kipurse app for Face ID approval, a Coinbase Verified identity attestation, and funding through Coinbase or Coinbase Onramp. Fees are paid in USDC from the wallet.
Installation
In SourceWeft
- Open Kipurse 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/com.kipurse%2Fkipurse/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": {
"kipurse": {
"type": "http",
"url": "https://pay.kipurse.com/mcp"
}
}
}README
Kipurse(启付)
A self-custodial USDC wallet on Base that lets AI agents pay within limits you set, with Face ID approval on your iPhone. 一个在 Base 上的自托管 USDC 钱包:AI 只能在你设定的额度内付款,超额、新收款人都要你在 iPhone 上用 Face ID 批准。
Use with an AI agent (MCP)
Remote MCP server: https://pay.kipurse.com/mcp (Streamable HTTP, OAuth). Setup for Cline and other MCP clients: llms-install.md.
Layout
ios/— iOS app (SwiftUI), widget,KipurseCoreSwift package, unit and UI tests.server/— Kipurse production gateway (cleaned copy): owner API, AI agent MCP (OAuth), Siri endpoint, pause, caps, onboarding sponsor caps, rescue (offline withdraw) page, SDK. Operator values (addresses, keys, URLs) come from config outside the repo.contracts/— Solidity V5 contracts (trust, adapter, phone approver, vaults) with Foundry tests;install-deps.shfetches pinned libs.docs/compliance/— compliance notes (not legal advice).
Principles
- Self-custody only: keys stay in the iPhone Secure Enclave / the user's own smart wallet. No pooled custody.
- One wallet per person. The owner can always withdraw everything, even if the Kipurse server is down.
- Hard AI caps (default 20 payments/day, $2/day, $0.25 per payment). One "Pause AI payments" switch stops every AI, including Siri.
- Identity: Coinbase Verified attestation only. Funding: Coinbase / Coinbase Onramp only. Fees are in USDC, paid from the wallet.
Build (iOS, simulator)
Server
Operator config lives OUTSIDE the repo (see server/kit/operator.mjs); KIPURSE_DEMO=1 runs unbranded.
Configuration comes from environment variables; see examples/ and DEVELOPMENT_SETUP.md. Never commit .env files or keys.
License
Copyright © 2026 Blessbridge Global Trading LLC / Kipurse.
Why: wallets, contracts and SDKs are permissive so anyone can build on them; the hosted gateway is AGPL so improvements to a hosted fork come back to the community. See LICENSE and each directory's LICENSE. Security issues: SECURITY.md.
Source: README.md at commit adf4c51
Tools
0Version history
1- v0.1.0LatestNov 4, 2026
Score
75% 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
Declare a license in the repository or the registry entry.