An MCP server for checking and revoking ERC-20 token allowances across multiple EVM chains, offering endpoints to list approvals, revoke allowances and check transaction status.
https://github.com/kukapay/token-revoke-mcpStop shipping DeFi apps that leave your users exposed to unlimited token approval risks.
Every time your users interact with DeFi protocols, they're granting token allowances – often unlimited ones. That USDC approval to Uniswap from six months ago? Still active. That experimental DEX that got hacked last week? Your users probably still have active approvals there.
The token-revoke-mcp server puts allowance management directly into your development workflow, giving you natural language control over one of DeFi's biggest attack vectors.
Cross-Chain Visibility: Query token approvals across 50+ EVM chains with a single prompt. No more manually checking Etherscan across different networks or maintaining separate RPC connections.
"Show me all risky token approvals for this wallet on Polygon"
Risk Quantification: Get immediate USD value exposure for each approval. Know exactly how much is at stake before deciding what to revoke.
Natural Language Interface: Skip the web3 boilerplate. Ask questions in plain English and get actionable transaction data back.
Transaction Management: Submit revocations and track their status without building your own transaction monitoring.
Wallet Security Dashboards: Build allowance review features that actually get used. Surface high-risk approvals by USD value and let users revoke with conversational commands.
DeFi App Health Checks: Before users interact with your protocol, scan for stale approvals to competitors or compromised contracts. Build this into your onboarding flow.
Portfolio Management Tools: Include allowance hygiene as part of portfolio health scoring. Flag wallets with excessive exposure to deprecated protocols.
Security Auditing: Quickly assess approval patterns across user bases. Identify which protocols are accumulating the most allowances and potential risk concentration.
This isn't another Web3 library to learn. The MCP protocol means you're working with natural language requests that map directly to user intent. No more translating between "revoke this sketchy approval" and contract interaction code.
The server handles chain detection, RPC management, and transaction formatting. You focus on the user experience, not the Web3 infrastructure.
Perfect for developers building:
Ready to ship DeFi features that don't compromise on security? The allowance management problem is solved – now you can focus on building the features that matter to your users.