Dogechain MCP server
com.dogechain/dogechaindogechain.comstreamable-httpv1.0.0Scanned
Dogecoin blockchain lookups: transactions explained, addresses, blocks, fees, supply and charts.
9 tools: 9 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Dogechain MCP server can do
The Dogechain MCP server is published by dogechain.com, a domain the MCP Registry verified. It has 9 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 13, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
9 tools
Only reads 9Show 9 read-only tools
findWorks out whether a string is a Dogecoin block height, block hash, transaction id or address, and which tool to call next.No findings
Why it is in this group
- The name "find" says "find": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Find anything
get_addressA 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, a…No findings
Why it is in this group
- The name "get_address" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Address
get_blockA 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.No findings
Why it is in this group
- The name "get_block" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Block
get_chartA Dogecoin chart series over time, oldest first: e.g.No findings
Why it is in this group
- The name "get_chart" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Chart data
get_feesWhat it costs to send DOGE right now: the fee we suggest to confirm within a few minutes, the least that still gets mined, what people actually paid lately, next-block fee rates an…No findings
Why it is in this group
- The name "get_fees" says "get": a word for reading.
Description, as the server wrote it What it costs to send DOGE right now: the fee we suggest to confirm within a few minutes, the least that still gets mined, what people actually paid lately, next-block fee rates and how many transactions are waiting.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Fees
get_networkThe Dogecoin network now: the newest block, the mempool and next-block fees, hashrate, difficulty, the latest blocks and the biggest recent transfers.No findings
Why it is in this group
- The name "get_network" says "get": a word for reading.
Description, as the server wrote it The Dogecoin network now: the newest block, the mempool and next-block fees, hashrate, difficulty, the latest blocks and the biggest recent transfers.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Network right now
get_rich_listThe 1,000 addresses holding the most DOGE, 100 a page, with how concentrated holdings are.No findings
Why it is in this group
- The name "get_rich_list" says "get": a word for reading.
Description, as the server wrote it The 1,000 addresses holding the most DOGE, 100 a page, with how concentrated holdings are. Big holders are often exchanges.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Top Doges
get_supplyHow many DOGE exist, how many are added each day and year (10,000 per block, no maximum), and inflation now and ahead.No findings
Why it is in this group
- The name "get_supply" says "get": a word for reading.
Description, as the server wrote it How many DOGE exist, how many are added each day and year (10,000 per block, no maximum), and inflation now and ahead.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Supply
get_transactionA 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) warni…No findings
Why it is in this group
- The name "get_transaction" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Transaction, explained
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:37 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http dogechain https://dogechain.com/mcpclaude mcp add --transport http dogechain https://dogechain.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__dogechain__find",
"mcp__dogechain__get_transaction",
"mcp__dogechain__get_address",
"mcp__dogechain__get_block",
"mcp__dogechain__get_network",
"mcp__dogechain__get_fees",
"mcp__dogechain__get_supply",
"mcp__dogechain__get_rich_list",
"mcp__dogechain__get_chart"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as dogechain. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.dogechain/dogechain/verify?hash=870b0e48bab4eb2c7a62530f4b87c0f3f48e0ed2020f99b72b83de738a2eddad" | jq -e '.changed == false'Pinned hash 870b0e48bab4, from Nov 13, 2026, 01:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.dogechain/dogechain/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.dogechain/dogechain)Source: MCP Registry. Synced Oct 21, 2026, 17:54 UTC.
Dogechain MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Dogechain MCP server safe?
- No scan can promise that. What its definitions show: 9 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the Dogechain MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Dogechain MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Dogechain MCP server have?
- 9 tools: 9 read. find, get_transaction, get_address, get_block, get_network, get_fees, get_supply, get_rich_list and 1 more.
Does the Dogechain MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Dogechain MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Dogechain MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.