_ registry / mcp http-sse · checked 2h ago

heyanon-mcp

https://api.heyanon.ai

Registry code: 4d266ff26a606042

api record

API key: it must be set as the X-API-Key (or Authorization: Bearer) header in the MCP connection config; ping and get_api_key_setup_url need no key. Never ask the user to paste the key into the chat. If a tool fails with "API key not set": call get_api_key_setup_url and show the user the URL and the config snippet; the user creates a key, puts it into the MCP connection config as the X-API-Key header and reconnects. ask_anon is asynchronous: it returns a background task ID; poll background_task with that ID until status is no longer "pending"; on "completed" read the reply from result, any…

endpoint
https://api.heyanon.ai/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is heyanon-mcp live?
Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is heyanon-mcp free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does heyanon-mcp have?
21 tools: scheduled_task_delete, background_task_delete, scheduled_task_get, get_api_key_setup_url, ask_gemma, ask_anon, abort, transfer_native, ….
Is heyanon-mcp safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98.8%

90 days 98.5%· all time 98.5%

latency
103ms

last good check

priced tools
0

of 21 tools

_ answered our checks, 90 days 388 checks · signed record
  • down → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
crypto & onchain trading & defi
used for
  • ask a defi assistant to trade
  • read wallet token and defi positions
  • read cex portfolio balances
  • manage scheduled trading tasks
  • confirm a pending background task
takes → gives
text → text, data
tools
13 reads3 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 21 tools
1 open9 auth-required 11 never probed 10 of 21 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • ping reads open 26h ago

    Health check for the Hey Anon MCP server. Returns "pong" and the server time (ISO 8601). No API key required.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {},
  "additionalProperties": false
}
    arguments 6 lines
  • projects reads auth-required 20h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {},
  "additionalProperties": false
}
    arguments 6 lines
  • portfolio_cex reads auth-required 2h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "address": {
      "type": "string",
      "description": "EVM wallet address (from wallet_list). Required when the account has several EVM wallets."
    }
  },
  "additionalProperties": false
}
    arguments 11 lines
  • portfolio_defi reads auth-required 2h ago

    DeFi positions (LP, staking, lending, vaults, etc.) for every user wallet (addresses taken from wallet_list). Returns JSON [{ walletAddress, data }].

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {},
  "additionalProperties": false
}
    arguments 6 lines
  • portfolio_tokens reads auth-required 20h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {},
  "additionalProperties": false
}
    arguments 6 lines
  • background_task_list reads auth-required 10d ago

    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 }.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {},
  "additionalProperties": false
}
    arguments 6 lines
  • portfolio_transactions reads auth-required 20h ago

    Recent transactions for every user wallet (addresses taken from wallet_list). Returns JSON [{ walletAddress, data }]. Output can be large with many wallets.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {},
  "additionalProperties": false
}
    arguments 6 lines
  • scheduled_task_list reads auth-required 10h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {},
  "additionalProperties": false
}
    arguments 6 lines
  • wallet_list reads auth-required 10h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {},
  "additionalProperties": false
}
    arguments 6 lines
  • isProcessing reads auth-required 2h ago

    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).

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {},
  "additionalProperties": false
}
    arguments 6 lines
  • scheduled_task_delete changes data unknown never probed

    Delete (cancel) a scheduled task by id. Irreversible: the automation will not run again. Returns a confirmation.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Scheduled task ID to delete (from scheduled_task_list)"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • background_task_delete changes data unknown never probed

    Delete a background task record by id.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Background task ID to delete (from ask_anon or background_task_list)"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • scheduled_task_get reads unknown 26h ago

    Get one scheduled task by id (from scheduled_task_list). Returns id, description, status, type and taskExecutorResponse (the last execution result).

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Scheduled task ID (from scheduled_task_list)"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • get_api_key_setup_url reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {},
  "additionalProperties": false
}
    arguments 6 lines
  • ask_gemma unknown 10h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "text"
  ],
  "properties": {
    "text": {
      "type": "string",
      "description": "Research question for Gemma, e.g. \"Analyze token 0x... on Sonic\" or \"Latest news about Aave\""
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • ask_anon unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "text",
    "wallets"
  ],
  "properties": {
    "text": {
      "type": "string",
      "description": "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": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "url",
          "mimetype"
        ],
        "properties": {
          "url": {
            "type": "string",
            "description": "Publicly accessible file URL"
          },
          "mimetype": {
            "type": "string",
            "description": "MIME type, e.g. image/png"
          }
        },
        "additionalProperties": false
      },
      "description": "Optional attachments (publicly reachable URL + MIME type), e.g. a screenshot or document for Anon to analyze"
    },
    "wallets": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "minItems": 1,
      "description": "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."
    }
  },
  "additionalProperties": false
}
    arguments 45 lines
  • abort changes data unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {},
  "additionalProperties": false
}
    arguments 6 lines
  • transfer_native unknown never probed

    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).

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "chain",
    "from",
    "to",
    "amount"
  ],
  "properties": {
    "to": {
      "type": "string",
      "description": "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": {
      "type": "string",
      "description": "Sender: one of the user wallet addresses from wallet_list, of the type matching the network (evm / solana / ton)"
    },
    "chain": {
      "enum": [
        "ethereum",
        "optimism",
        "bsc",
        "gnosis",
        "polygon",
        "sonic",
        "zksync",
        "base",
        "avalanche",
        "arbitrum",
        "scroll",
        "solana",
        "ton",
        "hyperevm",
        "plasma",
        "monad",
        "robinhood"
      ],
      "type": "string",
      "description": "Network name: ethereum, optimism, bsc, gnosis, polygon, sonic, zksync, base, avalanche, arbitrum, scroll, solana, ton, hyperevm, plasma, monad, robinhood"
    },
    "amount": {
      "type": "string",
      "pattern": "^\\d+$",
      "description": "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": {
      "type": "boolean",
      "description": "true = send the entire balance of the asset instead of amount. Only when the user explicitly asked to send everything."
    }
  },
  "additionalProperties": false
}
    arguments 53 lines
  • transfer_asset unknown never probed

    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).

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "chain",
    "from",
    "to",
    "amount",
    "asset"
  ],
  "properties": {
    "to": {
      "type": "string",
      "description": "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": {
      "type": "string",
      "description": "Sender: one of the user wallet addresses from wallet_list, of the type matching the network (evm / solana / ton)"
    },
    "asset": {
      "type": "string",
      "description": "Token contract / mint address on that network (not the symbol)"
    },
    "chain": {
      "enum": [
        "ethereum",
        "optimism",
        "bsc",
        "gnosis",
        "polygon",
        "sonic",
        "zksync",
        "base",
        "avalanche",
        "arbitrum",
        "scroll",
        "solana",
        "ton",
        "hyperevm",
        "plasma",
        "monad",
        "robinhood"
      ],
      "type": "string",
      "description": "Network name: ethereum, optimism, bsc, gnosis, polygon, sonic, zksync, base, avalanche, arbitrum, scroll, solana, ton, hyperevm, plasma, monad, robinhood"
    },
    "amount": {
      "type": "string",
      "pattern": "^\\d+$",
      "description": "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": {
      "type": "boolean",
      "description": "true = send the entire balance of the asset instead of amount. Only when the user explicitly asked to send everything."
    }
  },
  "additionalProperties": false
}
    arguments 58 lines
  • address_book_list unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "page": {
      "type": "integer",
      "minimum": 1,
      "description": "Page number, starting at 1"
    },
    "size": {
      "type": "integer",
      "minimum": 1,
      "description": "Entries per page"
    },
    "chains": {
      "type": "array",
      "items": {
        "enum": [
          "ethereum",
          "optimism",
          "bsc",
          "gnosis",
          "polygon",
          "sonic",
          "zksync",
          "base",
          "avalanche",
          "arbitrum",
          "scroll",
          "solana",
          "ton",
          "hyperevm",
          "plasma",
          "monad",
          "robinhood"
        ],
        "type": "string"
      },
      "description": "Only entries saved for these networks: ethereum, optimism, bsc, gnosis, polygon, sonic, zksync, base, avalanche, arbitrum, scroll, solana, ton, hyperevm, plasma, monad, robinhood"
    },
    "search": {
      "type": "string",
      "description": "Filter by name or address substring"
    }
  },
  "additionalProperties": false
}
    arguments 47 lines
  • background_task reads unknown 10d ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Background task ID (returned by ask_anon or background_task_list)"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 4d266ff26a606042.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/4d266ff26a606042/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/4d266ff26a606042/badge.svg)](https://brick.blue/agent/4d266ff26a606042?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on heyanon.ai 1 entry

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.