Skip to content

monerometrics MCP server

io.github.nowi333/monerometricsnowi333streamable-httpv0.5.2Scanned

Live Monero network metrics: reorgs, orphans, pool centralization and the Haveno order book.

19 tools: 1 do something that can't be undone, 14 change things and 4 only read.

Tools: 0 delete, 1 irreversible, 14 write, 4 read.
  • Reads private data · 0
  • Reads text others write · 19
  • Can send data out · 1
  • 1 finding

Tools listed without sign-in. Remote posture

Anlyon alternative

15 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the monerometrics MCP server can do

The monerometrics MCP server is published by the GitHub account nowi333. It has 19 tools. It can do things that cannot be undone, such as sending, paying or publishing (chain_fork_window) and create or change data (14 tools: network_info, price, haveno_book, haveno_premium and 10 more), but cannot delete data. 4 tools only read.

19 tools bring in text other people can write (network_info, price, haveno_book and 16 more); 1 tool can send data out of your system (chain_fork_window).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 19, 2026, version 0.5.2.

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.

19 tools

Can't be undone 1Claude Code: ask
  • chain_fork_windowRange of consecutive heights ending at `to` (default the current tip), listing every canonical block and any competing orphan, with fork-point flags.Reads text others writeCan send data out1 finding

    Why it is in this group

    • The name "chain_fork_window" says "fork": a word for a change.
    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Warn

      The server marks "chain_fork_window" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "chain_fork_window" says "fork": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Range of consecutive heights ending at `to` (default the current tip), listing every canonical block and any competing orphan, with fork-point flags. Use this to browse a stretch of the chain or see recent blocks; for a single block use search_block or get_block.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
Changes things 14Claude Code: ask
  • chain_provenanceEvidence quality behind pool attribution over a window: share of blocks proven cryptographically by view key, claimed by a pool API, inferred from the coinbase, or unattributed, pl…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Evidence quality behind pool attribution over a window: share of blocks proven cryptographically by view key, claimed by a pool API, inferred from the coinbase, or unattributed, plus claims a pool could not prove with its own key and the merge-mined share. Use this to judge how far to trust pool_distribution.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
  • haveno_bookLive Haveno XMR/USD order book as price levels, both sides, each priced against centralized spot.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Live Haveno XMR/USD order book as price levels, both sides, each priced against centralized spot. Each level carries cumulative depth, offer count, payment methods and a reversible flag. `asks` are makers selling XMR (taking one means buying); `bids` are makers buying (taking one means selling). Offers are advertisements with differing payment methods, not a matched book, so the best bid can sit at or above the best ask. Use this to see liquidity at each price; for a single headline price use price. Takes no arguments.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
  • haveno_payment_methodsExecuted Haveno trades grouped by payment method (PayPal, Zelle, cash by mail...), with trade count, volume and the average, median and standard deviation of the premium over spot.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Executed Haveno trades grouped by payment method (PayPal, Zelle, cash by mail...), with trade count, volume and the average, median and standard deviation of the premium over spot. Use this to compare what each payment rail costs. The premium tracks how reversible the rail is (chargeback risk), not privacy. The reversible flag is our own classification, not a Haveno field; methods with few trades give a fragile premium.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
  • haveno_premiumTime series of the Haveno peer-to-peer premium over centralized spot, both sides of the book, sampled every 10 minutes.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Time series of the Haveno peer-to-peer premium over centralized spot, both sides of the book, sampled every 10 minutes. Use this to see how the P2P premium moved over time; for the current value only, use price. Series carry price, amount and offer count but not the payment method (see haveno_payment_methods for that). History starts on 24 August 2026, when recording began.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
  • network_blocktimeTime series of the actual time between consecutive canonical blocks, in seconds (target 120 s), one point per block, capped at 1500 points.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Time series of the actual time between consecutive canonical blocks, in seconds (target 120 s), one point per block, capped at 1500 points. Use this to spot unusually slow or fast block production, e.g. around a hashrate shift or selfish-mining episode.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
  • network_emissionTime series of the average block reward in XMR per block (Monero tail emission is about 0.6 XMR plus fees).Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Time series of the average block reward in XMR per block (Monero tail emission is about 0.6 XMR plus fees). Use this to follow emission and fee income over time.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
  • network_hashrateTime series of the Monero network hashrate in H/s, derived from difficulty / 120 s target, bucketed to about 300 points per window.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Time series of the Monero network hashrate in H/s, derived from difficulty / 120 s target, bucketed to about 300 points per window. Use this for hashrate trends; for the current value only, use network_info.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
  • network_infoLive snapshot of the Monero network right now: node sync status, latest indexed height, difficulty, estimated hashrate and current mempool size.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Live snapshot of the Monero network right now: node sync status, latest indexed height, difficulty, estimated hashrate and current mempool size. Use this for "what is the state of the network now". For how a metric evolved over time, use network_hashrate, network_blocktime, network_mempool or network_emission instead. Takes no arguments.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
  • network_mempoolTime series of the mempool size: number of transactions waiting to be mined.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Time series of the mempool size: number of transactions waiting to be mined. Use this for congestion trends; for the current count only, use network_info. This series is observed live and cannot be rebuilt, so it starts when monitoring began.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
  • pool_distributionShare of blocks mined by each pool over a window, plus the largest pool's share, the top-two combined share and the Nakamoto coefficient (fewest pools controlling over 50% of block…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Share of blocks mined by each pool over a window, plus the largest pool's share, the top-two combined share and the Nakamoto coefficient (fewest pools controlling over 50% of blocks). Use this to assess mining centralization. Unattributed blocks stay in the denominator but are credited to no pool, so the coefficient is an upper bound. For how each attribution was established, use chain_provenance.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
  • pool_sourcesHealth of each mining-pool API used for block attribution: whether it is reachable and how many blocks it returned.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Health of each mining-pool API used for block attribution: whether it is reachable and how many blocks it returned. Use this to explain a high unattributed share in pool_distribution. Takes no arguments.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
  • priceCurrent XMR price in one call: the centralized spot (CoinGecko, Kraken fallback) and the Haveno peer-to-peer quote on both sides.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Current XMR price in one call: the centralized spot (CoinGecko, Kraken fallback) and the Haveno peer-to-peer quote on both sides. Returns the best offer and the amount-weighted average on each side, resting depth, offer counts and round_trip_cost_pct, the cost of buying XMR and selling it straight back (an upper bound, usually far above the headline premium). Use this for "what does XMR cost now". For the premium history use haveno_premium; for individual price levels use haveno_book. Takes no arguments.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
  • recent_orphansOrphan blocks (blocks that lost a fork race) paired with the canonical block that won at the same height, newest first.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Orphan blocks (blocks that lost a fork race) paired with the canonical block that won at the same height, newest first. Use this to list losing blocks and which pool mined them; for whole reorg events (depth, fork point) use reorgs. The default window "all" returns the last N orphans however old.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
  • reorg_statsSummary statistics of reorganizations per period (24h, 7d, 30d, 90d and everything recorded): event count, average and maximum depth, transactions affected, plus the date monitorin…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Summary statistics of reorganizations per period (24h, 7d, 30d, 90d and everything recorded): event count, average and maximum depth, transactions affected, plus the date monitoring began. Use this for "how many reorgs and how deep"; for the individual events use reorgs. Takes no arguments.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
Only reads 4Show 4 read-only tools
  • get_blockFull detail of one block given its exact 64-character hash: height, previous hash, timestamp, size, difficulty, reward, coinbase, transaction hashes, merge-mining tag, mining pool …Reads text others writeNo findings

    Why it is in this group

    • The name "get_block" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Full detail of one block given its exact 64-character hash: height, previous hash, timestamp, size, difficulty, reward, coinbase, transaction hashes, merge-mining tag, mining pool and, when proven, the view-key proof inputs. Use this when you already have a block hash (e.g. from recent_orphans or chain_fork_window). If you only have a height, use search_block.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
  • lookup_transactionLook up one transaction by its 64-character hash: in the mempool or mined, block height, confirmations, whether it is spendable yet, the pool that mined its block, and whether that…Reads text others writeNo findings

    Why it is in this group

    • The name "lookup_transaction" says "lookup": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Look up one transaction by its 64-character hash: in the mempool or mined, block height, confirmations, whether it is spendable yet, the pool that mined its block, and whether that height was ever contested by a reorg. Use this for any transaction-hash question. It never returns amounts, senders or recipients: the Monero protocol encrypts them.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
  • reorgsList of individual chain reorganizations detected, most recent first: fork point height, depth in blocks, old and new chain tips, transactions displaced, detection time.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    List of individual chain reorganizations detected, most recent first: fork point height, depth in blocks, old and new chain tips, transactions displaced, detection time. Use this to inspect specific reorg events. For counts and depth summaries per period use reorg_stats; for the losing blocks themselves use recent_orphans. Takes no arguments.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
  • search_blockFind one block from a height or a hash, anywhere from the genesis block (height 0) to the tip.Reads text others writeNo findings

    Why it is in this group

    • The name "search_block" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Find one block from a height or a hash, anywhere from the genesis block (height 0) to the tip. Returns the same detail as get_block plus is_canonical and, for a height, any orphan blocks competing at that height. Use this when the user gives a height, or when unsure whether a value is a height or a hash. For a range of consecutive blocks use chain_fork_window.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true

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.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write19
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
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.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:08 UTC, unchanged since Nov 13, 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
15
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://api.monerometrics.net/.well-known/oauth-protected-resource/mcp
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 15 tools that change things (1 irreversible, 14 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.monerometrics.net/mcp: tools/list returned 19 tools to an anonymous client, including chain_fork_window (irreversible), network_info (write), price (write), haveno_book (write), haveno_premium (write) and 10 more

    What this check looks for

Posture changes

  1. Nov 13, 2026
    • Tools that change things, listed without credentials: 16 to 15

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "chain_fork_window" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "chain_fork_window" says "fork": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools19 changed.~19 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 16 -> 15.View diff
    • Tools that change things, listed without credentials: 16 to 15
  3. Tools19 changed.~19 changedView diff

Install

Pinned to version 0.5.2. Values in angle brackets are yours to fill in.

claude mcp add --transport http monerometrics https://api.monerometrics.net/mcp
claude mcp add --transport http monerometrics https://api.monerometrics.net/mcp

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

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__monerometrics__reorgs",
      "mcp__monerometrics__get_block",
      "mcp__monerometrics__search_block",
      "mcp__monerometrics__lookup_transaction"
    ],
    "ask": [
      "mcp__monerometrics__network_info",
      "mcp__monerometrics__price",
      "mcp__monerometrics__haveno_book",
      "mcp__monerometrics__haveno_premium",
      "mcp__monerometrics__haveno_payment_methods",
      "mcp__monerometrics__network_hashrate",
      "mcp__monerometrics__network_blocktime",
      "mcp__monerometrics__network_mempool",
      "mcp__monerometrics__network_emission",
      "mcp__monerometrics__reorg_stats",
      "mcp__monerometrics__recent_orphans",
      "mcp__monerometrics__pool_distribution",
      "mcp__monerometrics__pool_sources",
      "mcp__monerometrics__chain_provenance",
      "mcp__monerometrics__chain_fork_window"
    ],
    "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 monerometrics. Review it before you use it.

Capability tags behind 19 rules
  • mcp__monerometrics__network_info untrusted-input
  • mcp__monerometrics__price untrusted-input
  • mcp__monerometrics__haveno_book untrusted-input
  • mcp__monerometrics__haveno_premium untrusted-input
  • mcp__monerometrics__haveno_payment_methods untrusted-input
  • mcp__monerometrics__network_hashrate untrusted-input
  • mcp__monerometrics__network_blocktime untrusted-input
  • mcp__monerometrics__network_mempool untrusted-input
  • mcp__monerometrics__network_emission untrusted-input
  • mcp__monerometrics__reorgs untrusted-input
  • mcp__monerometrics__reorg_stats untrusted-input
  • mcp__monerometrics__recent_orphans untrusted-input
  • mcp__monerometrics__pool_distribution untrusted-input
  • mcp__monerometrics__pool_sources untrusted-input
  • mcp__monerometrics__chain_provenance untrusted-input
  • mcp__monerometrics__get_block untrusted-input
  • mcp__monerometrics__search_block untrusted-input
  • mcp__monerometrics__lookup_transaction untrusted-input
  • mcp__monerometrics__chain_fork_window untrusted-input, outbound

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/io.github.nowi333/monerometrics/verify?hash=f087811b8a22f34e018f3c2abc4ceef97a25b3a51a90ae5bd9e99181065d3d9e" | jq -e '.changed == false'

Pinned hash f087811b8a22, from Nov 19, 2026, 11:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.nowi333/monerometrics/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.nowi333/monerometrics
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.nowi333/monerometrics.svg)](https://radar.anlyon.com/servers/io.github.nowi333/monerometrics)

Source: MCP Registry · repository. Synced Nov 5, 2026, 15:18 UTC.

monerometrics MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the monerometrics MCP server safe?

No scan can promise that. What its definitions show: 19 tools, 15 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the monerometrics MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the monerometrics MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: chain_fork_window.

What tools does the monerometrics MCP server have?

19 tools: 1 irreversible, 14 write, 4 read. chain_fork_window, network_info, price, haveno_book, haveno_premium, haveno_payment_methods, network_hashrate, network_blocktime and 11 more.

Does the monerometrics MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the monerometrics MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): chain_fork_window.

Has the monerometrics MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 19, 2026. Every change is on this page and in its Atom feed.