Server facts
tyi-mcp
Project
- Author
- TychiWallet
- Repository
- github.com/TychiWallet/tyi-mcp
- License
- Not specified
- Category
- Blockchain & Web3
Tech
- Runtime / language
- Not specified
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 3
- Last commit
- Data as of
Tags
- agent payments
- agentic wallet
- ai agent
- local signing
- mcp
- multi wallet
- onchain agent
- policy gated
- self custody
- wallet
Overview
Wallet setup and transaction handling take separate paths in tyi-mcp, which serves agents using stdio MCP hosts such as Cursor, Claude Desktop, and OpenClaw. The workflow starts with tyi_route to select a tool and tyi_status to identify readiness or missing setup. Onboarding has a schema tool and supports initial configuration or adding LLM credentials to an existing wallet. Dedicated tools create named wallets, import a mnemonic or private key, and change the active wallet within a shared keystore. Imports support EVM, Solana, and Sui.
Once setup is ready, tyi_chat handles balance inquiries, transfers, payments, spending policies, limits, and history. Spending caps are checked before transactions are signed. A hosted service interprets intent and routes LLM requests, while signing stays on the operator’s device and stored keys are encrypted locally. UGF payment rails handle cross-chain gas settlement. Local activity records provide an audit trail, and a separate reset tool removes local data with operator confirmation. Wallet imports go through their dedicated tool rather than chat.
tyi-mcp setup notes
- tyi-mcp records stdio only; confirm a network transport upstream before planning remote access.
- tyi-mcp has no recorded license; confirm reuse terms in its repository.