Token Revoke MCP MCP Server

If you already use Token Revoke MCP, the token revoke mcp mcp server is the piece that lets your assistant work with it directly. An MCP server for checking and revoking ERC-20 token allowances across multiple blockchains.

What the server does

• Fetch Token Approvals — Retrieve all ERC20 token approvals for a wallet on a specified chain, including token details, balances, and USD values at risk
• Revoke Allowances — Submit transactions to revoke ERC20 token allowances for specific spenders
• Check Transaction Status — Verify the success or failure of submitted transactions using transaction hashes
• Multi-Chain Support — Supports over 50 EVM-compatible chains, including mainnets (e.g., Ethereum, Polygon, BSC) and testnets (e.g., Goerli, Mumbai)

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Credentials and setup notes

Configuration is passed through the environment: MORALIS_API_KEY, PRIVATE_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Node.js: Version 18 or higher (for native fetch support). - Moralis API Key: Required for fetching token approval data. - Private Key: An Ethereum-compatible private key for signing revocation transactions.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. It is maintained by kukapay; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Token Revoke MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.