canli-mcp / Markets
token_check
What an ERC-20 token's contract can do and how much of it exists, read from the chain: mint, pause, blacklist and upgrade powers, owner, proxy, source verification, supply, and an unlock schedule you give set against it. It names what the code allows. A clean reading never means safe, and it cannot detect a rug pull.
The tool is token_check in canli-mcp 0.22.0, free and MIT-licensed, with no account and no API key. It comes from canli-markets-mcp, which canli-mcp includes, and it is also its own server.
Arguments
| Argument | Required | Type |
|---|---|---|
address | yes | string |
chain | no | ethereum|base|arbitrum|optimism|... |
announced_max_supply | no | number |
schedule | no | {date,amount,note}[] |
How a model reaches it
Ask in plain words. The model finds token_check with canli-mcp's find_tool, reads its arguments with describe_tool if it needs to, and runs it with run_tool. The call has this shape, with your values in place of the angle brackets:
{
"name": "token_check",
"arguments": {
"address": "<string>"
}
}Words that find it
Besides its name, title and description, find_tool matches a question to token_check on these words: token, tokenomics, erc20, contract, mint, supply, unlock, schedule, vesting, inflation, owner, proxy, upgradeable, blacklist, pause, honeypot, rug, pull, defi, crypto, on-chain, due, diligence.
More
Nothing here is investment advice.