Skip to content

check_heartbeat ​

Read · No sign-in

Get heartbeat score for a registration

A registered token's health on one chain: the heartbeat score (0-100) the oracle published for it in the latest daily epoch, the status derived from it, the three parts it is built from (age, DEX volume, holder health) and how many epochs in a row it has been under 60. A registration whose heartbeat stays under 60 for 30 epochs can lapse and become claimable again, so the score tells a live token page from a dormant one. Answers 404 for a symbol that has no registration on that chain, and for a registration past its 30-day grace period that no epoch has scored yet.

outlook reads that published leaf forward: the first daily count projected under 60, the day the name can be registered by anyone who proves the same contract, and the least trading (or the fewest more holders) that holds 60. The coin's health notices say the same.

Reads or changesReads only
Sign-inNo
CallsGET /api/v2/heartbeat/{symbol}/{chain} (API Explorer)

Input ​

JSON Schema, as the server serves it.

json
{
  "additionalProperties": false,
  "properties": {
    "chain": {
      "description": "Chain key (e.g. `arbitrum`, `base`, `solana`). A Solana registration is answered from its committed leaf alone (`chainId` 0).",
      "examples": [
        "arbitrum"
      ],
      "type": "string"
    },
    "symbol": {
      "description": "Token symbol",
      "examples": [
        "PEPE"
      ],
      "type": "string"
    },
    "tokenAddress": {
      "description": "The token's contract address, when several tokens on the chain share the ticker.",
      "type": "string"
    }
  },
  "required": [
    "chain",
    "symbol"
  ],
  "type": "object"
}

Example ​

A tools/call request:

json
{
  "name": "check_heartbeat",
  "arguments": {
    "chain": "arbitrum",
    "symbol": "PEPE"
  }
}

All MCP tools · Connect an AI app