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

dogechain

https://dogechain.com

Registry code: af274035f1550137

api record

Dogecoin blockchain data from Dogechain (dogechain.com), live. Amounts are DOGE with up to 8 decimals. Quote addresses and transaction ids in full, never shortened. Say which block height or UTC time numbers are as of. Pass on any lookalike (address-poisoning) warnings. When unsure what a string is, call `find` first. Every answer names the matching dogechain.com page: share it with the user.

endpoint
https://dogechain.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
998ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 9 tools
3 open 6 never probed 3 of 9 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.

  • get_fees open 2h ago

    What it costs to send DOGE right now: the least a payment can pay, what people actually paid lately, next-block fee rates and how many transactions are waiting.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {},
  "additionalProperties": false
}
    arguments 6 lines
  • get_network open 2h ago

    The Dogecoin network now: the newest block, the mempool and next-block fees, hashrate, difficulty, the latest blocks and the biggest recent transfers.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {},
  "additionalProperties": false
}
    arguments 6 lines
  • get_rich_list open 2h ago

    The 1,000 addresses holding the most DOGE, 100 a page, with how concentrated holdings are. Big holders are often exchanges.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "page": {
      "type": "integer",
      "maximum": 10,
      "minimum": 1,
      "description": "Page 1 to 10 (default 1)."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • find unknown never probed

    Works out whether a string is a Dogecoin block height, block hash, transaction id or address, and which tool to call next. Use it when unsure.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "maxLength": 100,
      "description": "A block height, block hash, transaction id or address."
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • get_transaction unknown never probed

    A Dogecoin transaction in plain English: who paid whom, how much, the likely change, the fee, its confirmations, every input and output, and any address-poisoning (lookalike) warning.

    mcp-tool

    {
  "type": "object",
  "required": [
    "txid"
  ],
  "properties": {
    "txid": {
      "type": "string",
      "pattern": "^[0-9a-fA-F]{64}$",
      "description": "The transaction id: 64 hex characters."
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • get_address unknown never probed

    A Dogecoin address: balance (with its dollar value), totals received and sent, transaction count, its mining-pool name if any, rank among the largest holders, lookalike warnings, and its history newest first, 10 a page.

    mcp-tool

    {
  "type": "object",
  "required": [
    "address"
  ],
  "properties": {
    "page": {
      "type": "integer",
      "minimum": 1,
      "description": "Page, from 1 (default 1)."
    },
    "address": {
      "type": "string",
      "description": "A Dogecoin address, e.g. D8AXXiGEZeZnMKTKnC9AWB3YUU4jfMAmYU."
    }
  },
  "additionalProperties": false
}
    arguments 18 lines
  • get_block unknown never probed

    A Dogecoin block: when it was found, who mined it (pool name and payout address), reward and fees, size, confirmations, and its transactions as one-line stories, 25 a page.

    mcp-tool

    {
  "type": "object",
  "required": [
    "block"
  ],
  "properties": {
    "page": {
      "type": "integer",
      "minimum": 1,
      "description": "Page, from 1 (default 1)."
    },
    "block": {
      "type": "string",
      "description": "A height, a 64-hex block hash, or \"latest\"."
    }
  },
  "additionalProperties": false
}
    arguments 18 lines
  • get_supply unknown never probed

    How many DOGE exist, how many are added each day and year (10,000 per block, no maximum), and inflation now and ahead.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {},
  "additionalProperties": false
}
    arguments 6 lines
  • get_chart unknown never probed

    A Dogecoin chart series over time, oldest first: e.g. tx_count, fees_median, hashrate, difficulty, supply, price_usd, block_interval, active_addresses, pool_share, holder_share.

    mcp-tool

    {
  "type": "object",
  "required": [
    "series"
  ],
  "properties": {
    "last": {
      "type": "integer",
      "maximum": 500,
      "minimum": 1,
      "description": "How many of the latest points (default 30)."
    },
    "series": {
      "enum": [
        "tx_count",
        "block_size",
        "active_addresses",
        "new_addresses",
        "transfers",
        "transfers_sent",
        "fees_median",
        "fees_total",
        "hashrate",
        "difficulty",
        "block_interval",
        "pool_share",
        "lookalikes",
        "lookalike_senders",
        "supply",
        "price_usd",
        "holder_share",
        "tx_per_min"
      ],
      "type": "string"
    },
    "interval": {
      "enum": [
        "minute",
        "hour",
        "day",
        "week",
        "month"
      ],
      "type": "string",
      "description": "Default day. minute is for tx_per_min only; pool_share, transfers and holder_share come by day or hour."
    }
  },
  "additionalProperties": false
}
    arguments 49 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.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/af274035f1550137/badge.svg)](https://brick.blue/agent/af274035f1550137)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

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