HeyAnon MCP
Server Details
HeyAnon on-chain agent: wallets, portfolios, DeFi and CEX actions, transfers, Gemma research.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- RealWagmi/heyanon-ai-cursor-plugin
- GitHub Stars
- 0
TDQS
Score is being calculated.
Available Tools
21 toolsabortAbort Anon requestDestructiveIdempotentInspect
Force-stop Anon processing of the current ask_anon request. Use only when isProcessing stays true for too long or the request is stuck; otherwise wait for the background task to complete.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
address_book_listList address bookRead-onlyIdempotentInspect
List the user saved recipient addresses (address book): name, networks and address. Use it to resolve a recipient the user names, e.g. "send 0.1 ETH to My work address": find the entry by name (search), take its address and confirm it with the user before calling transfer_native or transfer_asset. Informational only: transfers are not restricted to these addresses. Returns the entries and pagination, also as structuredContent.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number, starting at 1 | |
| size | No | Entries per page | |
| chains | No | Only entries saved for these networks: ethereum, optimism, bsc, gnosis, polygon, sonic, zksync, base, avalanche, arbitrum, scroll, solana, ton, hyperevm, plasma, monad, robinhood | |
| search | No | Filter by name or address substring |
Output Schema
| Name | Required | Description |
|---|---|---|
| whitelist | Yes | |
| pagination | No |
ask_anonAsk AnonDestructiveInspect
Send a message to Anon, the Hey Anon on-chain AI agent (balances, swaps, bridging, lending, staking, CEX, scheduled automations, research). Asynchronous: the output is only a confirmation with the background task ID; poll background_task with that ID until status is no longer "pending" ("completed": the reply is in result; any other status, e.g. "failed": the request did not finish, check logs). Anon keeps NO conversation context: every message is processed from a clean slate, so each message must be self-contained (repeat the wallet, network, token and amount every time; follow-ups like "and on Base?" will not work). Before sending, the tool checks that Anon is idle: if the previous request is still processing it returns an error, poll background_task until it finishes (or call abort) and retry. Anon can execute real transactions from the attached wallets: send action instructions (swap, send, bridge, stake, create an automation) only when the user explicitly asked for that action, and phrase everything else as a question. For general crypto research not tied to the user wallets, prefer ask_gemma.
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | Natural-language message or instruction for Anon. Phrase information requests as questions, e.g. "What is my S balance on Sonic?" or "Show my Aave positions". Action instructions such as "Swap 10 USDC to ETH on Base" can make Anon execute a real transaction from the attached wallet: send them only when the user explicitly requested that exact action, token and amount | |
| files | No | Optional attachments (publicly reachable URL + MIME type), e.g. a screenshot or document for Anon to analyze | |
| wallets | Yes | Wallet addresses to attach: at least one, and at most ONE per wallet type (e.g. one evm, one solana, one ton). Two addresses of the same type are rejected by the backend ("Multiple wallets found for type evm"). Take addresses from wallet_list. If the user has several wallets of the same type, use the one the user named (by displayName or address); otherwise ask which one to use rather than picking arbitrarily. |
ask_gemmaAsk GemmaRead-onlyInspect
Ask Gemma, the Hey Anon crypto research assistant: protocol analysis, community and social insights, market data, news, token analytics by contract address. Synchronous: returns the answer text directly, no polling and no wallet addresses needed. Research only: Gemma takes no wallet addresses, executes no transactions and keeps its own session, separate from the Anon conversation. Prefer ask_gemma for general crypto questions and ask_anon for anything about the user wallets or for actions.
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | Research question for Gemma, e.g. "Analyze token 0x... on Sonic" or "Latest news about Aave" |
background_taskGet background taskRead-onlyIdempotentInspect
Get one Anon background task by id. Each ask_anon call creates a task; poll this tool until status is no longer "pending": "completed" means the Anon reply is in result; any other status (e.g. "failed") means the request did not finish, check logs. Returns id, prompt, status, result ("—" while absent), logs (execution trace, appended live while the task runs), createdAt, updatedAt; the same object is returned as structuredContent.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Background task ID (returned by ask_anon or background_task_list) |
Output Schema
| Name | Required | Description |
|---|---|---|
| id | No | |
| logs | No | Execution trace lines, appended while the task runs |
| prompt | No | |
| result | No | Anon reply; present once status is completed |
| status | No | pending | completed | failed |
| createdAt | No | |
| updatedAt | No |
background_task_deleteDelete background taskDestructiveIdempotentInspect
Delete a background task record by id.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Background task ID to delete (from ask_anon or background_task_list) |
Output Schema
| Name | Required | Description |
|---|---|---|
| id | Yes | |
| deleted | Yes |
background_task_listList background tasksRead-onlyIdempotentInspect
List the user Anon background tasks (one per ask_anon message): id, prompt, status, result (Anon reply when completed), logs, createdAt, updatedAt. Use it to find earlier answers or check what is still pending. Also returned as structuredContent { tasks }.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
| tasks | Yes |
get_api_key_setup_urlAPI key setup URLRead-onlyIdempotentInspect
Get the URL of the Hey Anon page where the user logs in and creates an API key, plus the MCP config snippet where the key goes (X-API-Key header). Call this when a tool fails with "API key not set" or the user has no key yet. The key is never passed through the chat. No API key required.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
isProcessingIs Anon processingRead-onlyIdempotentInspect
Check whether Anon is still processing the previous ask_anon request. Returns "isProcessing: true|false". Use before sending another message, or when a request looks stuck (then call abort).
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
pingPingRead-onlyIdempotentInspect
Health check for the Hey Anon MCP server. Returns "pong" and the server time (ISO 8601). No API key required.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
portfolio_cexPortfolio CEXRead-onlyIdempotentInspect
Balances and positions from the exchange accounts linked to Hey Anon (e.g. Hyperliquid, keyed by exchange). Pass address (an EVM wallet from wallet_list) when the user has several EVM wallets, otherwise the backend rejects the call. Returns the raw JSON response.
| Name | Required | Description | Default |
|---|---|---|---|
| address | No | EVM wallet address (from wallet_list). Required when the account has several EVM wallets. |
portfolio_defiPortfolio DeFi positionsRead-onlyIdempotentInspect
DeFi positions (LP, staking, lending, vaults, etc.) for every user wallet (addresses taken from wallet_list). Returns JSON [{ walletAddress, data }].
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
portfolio_tokensPortfolio tokensRead-onlyIdempotentInspect
Token balances for every user wallet (addresses taken from wallet_list) across all supported networks. Returns JSON [{ walletAddress, data }]; for EVM wallets data.evm is keyed by chain id, Solana balances are in data.solana. Output can be large with many wallets.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
portfolio_transactionsPortfolio transactionsRead-onlyIdempotentInspect
Recent transactions for every user wallet (addresses taken from wallet_list). Returns JSON [{ walletAddress, data }]. Output can be large with many wallets.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
projectsList supported projectsRead-onlyIdempotentInspect
List the protocols and integrations Anon can operate (swaps, lending, staking, bridges, CEX, etc.): name, key, description, supported networks, tool count. Use it to check whether Anon supports a protocol or network before asking.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
scheduled_task_deleteDelete scheduled taskDestructiveIdempotentInspect
Delete (cancel) a scheduled task by id. Irreversible: the automation will not run again. Returns a confirmation.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Scheduled task ID to delete (from scheduled_task_list) |
scheduled_task_getGet scheduled taskRead-onlyIdempotentInspect
Get one scheduled task by id (from scheduled_task_list). Returns id, description, status, type and taskExecutorResponse (the last execution result).
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Scheduled task ID (from scheduled_task_list) |
scheduled_task_listList scheduled tasksRead-onlyIdempotentInspect
List the user scheduled tasks: automations created through Anon that run at a given time or when a price condition is met. There is no create/update tool: to create an automation, ask Anon via ask_anon (e.g. "Buy 0.1 ETH on Base when ETH drops below 2000"), then use this tool to confirm it exists. Returns id, description, status, type and, when present, taskExecutorResponse (the last execution result); the trigger time or condition is not a separate field, infer it from description.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
transfer_assetTransfer tokenDestructiveInspect
Send a token (ERC-20 / SPL / jetton) from one of the user wallets to another address. This moves real funds and cannot be undone. Call it only when the user explicitly asked to send this exact amount of this asset from this wallet to this recipient on this network; never infer, round or top up any of these values. If anything is missing or ambiguous, ask the user instead of guessing. Returns the transaction hash and an explorer link (also as structuredContent).
| Name | Required | Description | Default |
|---|---|---|---|
| to | Yes | Recipient address on the same network, exactly as the user gave it. If the user names a saved contact instead of an address, resolve it with address_book_list and confirm the address with the user first | |
| from | Yes | Sender: one of the user wallet addresses from wallet_list, of the type matching the network (evm / solana / ton) | |
| asset | Yes | Token contract / mint address on that network (not the symbol) | |
| chain | Yes | Network name: ethereum, optimism, bsc, gnosis, polygon, sonic, zksync, base, avalanche, arbitrum, scroll, solana, ton, hyperevm, plasma, monad, robinhood | |
| amount | Yes | Amount as an integer string in the smallest unit of the asset (wei, lamports, nanoton, token base units), e.g. "1000000000000000000" = 1 ETH (18 decimals); 1 USDC = "1000000" (6 decimals) | |
| allBalance | No | true = send the entire balance of the asset instead of amount. Only when the user explicitly asked to send everything. |
Output Schema
| Name | Required | Description |
|---|---|---|
| hash | Yes | Transaction hash |
| link | Yes | Block explorer link to the transaction |
transfer_nativeTransfer native coinDestructiveInspect
Send the native coin of a network (ETH, S, SOL, TON, ...) from one of the user wallets to another address. This moves real funds and cannot be undone. Call it only when the user explicitly asked to send this exact amount of this asset from this wallet to this recipient on this network; never infer, round or top up any of these values. If anything is missing or ambiguous, ask the user instead of guessing. Returns the transaction hash and an explorer link (also as structuredContent).
| Name | Required | Description | Default |
|---|---|---|---|
| to | Yes | Recipient address on the same network, exactly as the user gave it. If the user names a saved contact instead of an address, resolve it with address_book_list and confirm the address with the user first | |
| from | Yes | Sender: one of the user wallet addresses from wallet_list, of the type matching the network (evm / solana / ton) | |
| chain | Yes | Network name: ethereum, optimism, bsc, gnosis, polygon, sonic, zksync, base, avalanche, arbitrum, scroll, solana, ton, hyperevm, plasma, monad, robinhood | |
| amount | Yes | Amount as an integer string in the smallest unit of the asset (wei, lamports, nanoton, token base units), e.g. "1000000000000000000" = 1 ETH (18 decimals); 1 USDC = "1000000" (6 decimals) | |
| allBalance | No | true = send the entire balance of the asset instead of amount. Only when the user explicitly asked to send everything. |
Output Schema
| Name | Required | Description |
|---|---|---|
| hash | Yes | Transaction hash |
| link | Yes | Block explorer link to the transaction |
wallet_listList walletsRead-onlyIdempotentInspect
List the user wallets registered in Hey Anon: display name, type (evm, solana, ton, etc.), address, labels and whether the wallet is archived. Call it before ask_anon to choose which addresses to attach (at most one per type); match the wallet the user names by display name, label or address and skip archived wallets. The same addresses are used by the portfolio_* tools.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
21 tool updates
- First observed
abort - First observed
address_book_list - First observed
ask_anon - First observed
ask_gemma - First observed
background_task - First observed
background_task_delete - First observed
background_task_list - First observed
get_api_key_setup_url - First observed
isProcessing - First observed
ping - First observed
portfolio_cex - First observed
portfolio_defi - First observed
portfolio_tokens - First observed
portfolio_transactions - First observed
projects - First observed
scheduled_task_delete - First observed
scheduled_task_get - First observed
scheduled_task_list - First observed
transfer_asset - First observed
transfer_native - First observed
wallet_list
Related MCP Connectors
Blockchain analytics API for AI agents. Smart Money signals, wallet profiling, token analytics.
Blockchain analytics API for AI agents. Smart Money signals, wallet profiling, token analytics.
KOL and smart money wallet tracking on 5 chains: live trades, PnL, signals, Jito bundle detection.
Solana onchain intelligence for AI agents: wallet risk, due-diligence, perps funding, smart money.
Related MCP Servers
AlicenseNot gradedqualityBmaintenanceZerion MCP let's your agent analyze EVM and Solana wallets and summarize total portfolio value, top holdings, DeFi positions, recent transactions, PnL and more.64-- FlicenseNot gradedqualityCmaintenanceProvides tools for querying onchain data across 12+ blockchain networks, including token balances, transaction analysis, and smart contract security auditing. It enables users to interact with multiple EVM-compatible chains and perform deep contract evaluations through natural language interfaces.1-
- AlicenseBqualityDmaintenanceProvides AI agents with research tools for AI agent ecosystem analysis, DeFi protocol analysis, and general market research.329 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to analyze Ethereum wallets, simulate transactions, and draft transfers with deterministic policy and risk scoring, requiring human approval before on-chain execution.2 npmISC
Glama MCP Gateway
Add one secure layer between your agents and this server.