Summary
Private tokens handled end to end, decryption included.
COTI's point is that token amounts stay encrypted onchain, which normally means reading a balance and decoding it are two separate jobs. Here the same server holds both, so a private balance comes back as a number rather than a ciphertext.
What it is
An MCP server for the COTI blockchain, built around private token operations that use COTI's multi-party computation, where amounts stay encrypted onchain.
What you get
- Private ERC20 contracts deployed and minted, with balance, allowance, decimals and total supply readable
- Private ERC721 collections deployed and minted, with owner, approvals and token URI readable
- Values encrypted and decrypted with a COTI AES key, and a key generated when you need one
- Accounts created, messages signed with the account private key, and signatures verified
- Native COTI balance read and transferred
- Arbitrary contract functions called, with transaction status, logs and decoded event data
- Networks switched, and the current network readable before you act on the wrong one
- Tools spanning accounts, ERC20, ERC721, transactions and native transfers
Requirements
COTI account credentials: the server signs with an account private key and decrypts with a COTI AES key. Both an account and a key can be created through the server's own tools.
Setup effort
One command plus a key — npx -y @smithery/cli install @davibauer/coti-mcp --client claude, then supply credentials