accueil / serveurs / Finance & Paiement / io.github.RealWagmi/heyanon
io.github.RealWagmi/heyanon
serveur MCP (Model Context Protocol) · heyanon-mcp 1.0.0
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que io.github.RealWagmi/heyanon est sûr ?
Au dernier audit MCP Hub, le serveur MCP « io.github.RealWagmi/heyanon » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 21 outils
- abort≈ 126 tokens
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.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "abort", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - address_book_list≈ 518 tokens
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.
Paramètres, retour & exemple (4)
Paramètrespage· integer · optionnel
Page number, starting at 1size· integer · optionnel
Entries per pagechains· array · optionnel
Only entries saved for these networks: ethereum, optimism, bsc, gnosis, polygon, sonic, zksync, base, avalanche, arbitrum, scroll, solana, ton, hyperevm, plasma, monad, robinhoodsearch· string · optionnel
Filter by name or address substring
Exemple d'appel{"name": "address_book_list", "arguments": {"page": 1, "size": 1, "chains": [], "search": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"whitelist": [], "pagination": {}}} - ask_anon≈ 702 tokens
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.
Paramètres, retour & exemple (3)
Paramètrestext· string · requis
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 amountfiles· array · optionnel
Optional attachments (publicly reachable URL + MIME type), e.g. a screenshot or document for Anon to analyzewallets· array · requis
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.
Exemple d'appel{"name": "ask_anon", "arguments": {"text": "texte", "wallets": []}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - ask_gemma≈ 230 tokens
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.
Paramètres, retour & exemple (1)
Paramètrestext· string · requis
Research question for Gemma, e.g. "Analyze token 0x... on Sonic" or "Latest news about Aave"
Exemple d'appel{"name": "ask_gemma", "arguments": {"text": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - background_task≈ 353 tokens
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.
Paramètres, retour & exemple (1)
Paramètresid· string · requis
Background task ID (returned by ask_anon or background_task_list)
Exemple d'appel{"name": "background_task", "arguments": {"id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "logs": [], "prompt": "texte", "result": "texte", "status": "texte", "createdAt": "texte", "updatedAt": "texte"}} - background_task_delete≈ 184 tokens
Delete a background task record by id.
Paramètres, retour & exemple (1)
Paramètresid· string · requis
Background task ID to delete (from ask_anon or background_task_list)
Exemple d'appel{"name": "background_task_delete", "arguments": {"id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "deleted": true}} - background_task_list≈ 308 tokens
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 }.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "background_task_list", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"tasks": []}} - get_api_key_setup_url≈ 149 tokens
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.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "get_api_key_setup_url", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - isProcessing≈ 123 tokens
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).
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "isProcessing", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - ping≈ 97 tokens
Health check for the Hey Anon MCP server. Returns "pong" and the server time (ISO 8601). No API key required.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "ping", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - portfolio_cex≈ 174 tokens
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.
Paramètres, retour & exemple (1)
Paramètresaddress· string · optionnel
EVM wallet address (from wallet_list). Required when the account has several EVM wallets.
Exemple d'appel{"name": "portfolio_cex", "arguments": {"address": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - portfolio_defi≈ 114 tokens
DeFi positions (LP, staking, lending, vaults, etc.) for every user wallet (addresses taken from wallet_list). Returns JSON [{ walletAddress, data }].
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "portfolio_defi", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - portfolio_tokens≈ 141 tokens
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.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "portfolio_tokens", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - portfolio_transactions≈ 117 tokens
Recent transactions for every user wallet (addresses taken from wallet_list). Returns JSON [{ walletAddress, data }]. Output can be large with many wallets.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "portfolio_transactions", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - projects≈ 132 tokens
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.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "projects", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - scheduled_task_delete≈ 142 tokens
Delete (cancel) a scheduled task by id. Irreversible: the automation will not run again. Returns a confirmation.
Paramètres, retour & exemple (1)
Paramètresid· string · requis
Scheduled task ID to delete (from scheduled_task_list)
Exemple d'appel{"name": "scheduled_task_delete", "arguments": {"id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - scheduled_task_get≈ 140 tokens
Get one scheduled task by id (from scheduled_task_list). Returns id, description, status, type and taskExecutorResponse (the last execution result).
Paramètres, retour & exemple (1)
Paramètresid· string · requis
Scheduled task ID (from scheduled_task_list)
Exemple d'appel{"name": "scheduled_task_get", "arguments": {"id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - scheduled_task_list≈ 199 tokens
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.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "scheduled_task_list", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - transfer_asset≈ 623 tokens
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).
Paramètres, retour & exemple (6)
Paramètresto· string · requis
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 firstfrom· string · requis
Sender: one of the user wallet addresses from wallet_list, of the type matching the network (evm / solana / ton)asset· string · requis
Token contract / mint address on that network (not the symbol)chain· string · requis · ethereum | optimism | bsc | gnosis | polygon | sonic | zksync | base
Network name: ethereum, optimism, bsc, gnosis, polygon, sonic, zksync, base, avalanche, arbitrum, scroll, solana, ton, hyperevm, plasma, monad, robinhoodamount· string · requis
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· boolean · optionnel
true = send the entire balance of the asset instead of amount. Only when the user explicitly asked to send everything.
Exemple d'appel{"name": "transfer_asset", "arguments": {"to": "texte", "from": "texte", "asset": "texte", "chain": "ethereum", "amount": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"hash": "texte", "link": "texte"}} - transfer_native≈ 600 tokens
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).
Paramètres, retour & exemple (5)
Paramètresto· string · requis
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 firstfrom· string · requis
Sender: one of the user wallet addresses from wallet_list, of the type matching the network (evm / solana / ton)chain· string · requis · ethereum | optimism | bsc | gnosis | polygon | sonic | zksync | base
Network name: ethereum, optimism, bsc, gnosis, polygon, sonic, zksync, base, avalanche, arbitrum, scroll, solana, ton, hyperevm, plasma, monad, robinhoodamount· string · requis
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· boolean · optionnel
true = send the entire balance of the asset instead of amount. Only when the user explicitly asked to send everything.
Exemple d'appel{"name": "transfer_native", "arguments": {"to": "texte", "from": "texte", "chain": "ethereum", "amount": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"hash": "texte", "link": "texte"}} - wallet_list≈ 166 tokens
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.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "wallet_list", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».