Skip to content

CoinVet MCP server

dev.pages.coinvet/coinvetcoinvet.pages.devstreamable-httpv1.2.0Scanned

Money checks for agents: BTC price, fees, crypto + Lightning address checks, IBAN, BIC, US ZIP.

7 tools: 2 change things and 5 only read.

Tools: 0 delete, 0 irreversible, 2 write, 5 read.
  • Reads private data · 0
  • Reads text others write · 4
  • Can send data out · 0
  • No findings

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

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 CoinVet MCP server can do

The CoinVet MCP server is published by coinvet.pages.dev, a domain the MCP Registry verified. It has 7 tools. It can create or change data (2 tools: btc_price and mempool_fees), but cannot delete data. 5 tools only read.

4 tools bring in text other people can write (btc_price, mempool_fees, lightning_address_check and 1 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Nov 22, 2026, version 1.2.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.

7 tools

Changes things 2Claude Code: ask
  • btc_priceCurrent Bitcoin price in major fiat currencies from mempool.space, plus sats per currency unit.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 Bitcoin price in major fiat currencies from mempool.space, plus sats per currency unit. Indicative, refreshed about every minute.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
    • idempotentHint: true
  • mempool_feesRecommended Bitcoin on-chain fee rates in sat/vB (next block, ~30 min, ~1 h, economy, minimum), mempool size, current block height, and the example cost in sats of a typical 140 vB…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
    Recommended Bitcoin on-chain fee rates in sat/vB (next block, ~30 min, ~1 h, economy, minimum), mempool size, current block height, and the example cost in sats of a typical 140 vB transaction.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
    • idempotentHint: true
Only reads 5Show 5 read-only tools
  • bic_validateValidate a BIC/SWIFT code's structure (bank code, ISO country, location, optional branch) and flag test BICs.No findings

    Why it is in this group

    • The name "bic_validate" says "validate": a word for reading.
    Description, as the server wrote it
    Validate a BIC/SWIFT code's structure (bank code, ISO country, location, optional branch) and flag test BICs. Format check only, not a directory lookup.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
    • idempotentHint: true
  • crypto_address_validateCheck a cryptocurrency address offline before using it: Bitcoin legacy/P2SH (base58check), segwit/taproot (bech32/bech32m), Ethereum and all EVM chains incl.No findings

    Why it is in this group

    • The name "crypto_address_validate" says "validate": a word for reading.
    Description, as the server wrote it
    Check a cryptocurrency address offline before using it: Bitcoin legacy/P2SH (base58check), segwit/taproot (bech32/bech32m), Ethereum and all EVM chains incl. Base (EIP-55 checksum via keccak-256), Litecoin, Dogecoin, Tron and Solana. Returns valid, chain, network, type, and the correctly checksummed form. Catches typos and copy errors.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
    • idempotentHint: true
  • iban_validateValidate an International Bank Account Number: format, per-country length (80+ countries) and the ISO 7064 mod-97 checksum.No findings

    Why it is in this group

    • The name "iban_validate" says "validate": a word for reading.
    Description, as the server wrote it
    Validate an International Bank Account Number: format, per-country length (80+ countries) and the ISO 7064 mod-97 checksum. Returns country, check digits, BBAN and the formatted IBAN. Format only; does not confirm the account exists.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
    • idempotentHint: true
  • lightning_address_checkResolve a Lightning address (user@domain) or bech32 LNURL to its LNURL-pay endpoint and return whether it is valid, min/max sendable sats, comment length, Nostr zap support and des…Reads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "resolve" and "comment": it reads comments, which other people can write.
    Description, as the server wrote it
    Resolve a Lightning address (user@domain) or bech32 LNURL to its LNURL-pay endpoint and return whether it is valid, min/max sendable sats, comment length, Nostr zap support and description. Never requests an invoice or pays. Also recognizes BOLT11 invoices.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
    • idempotentHint: true
  • us_zip_lookupLook up a US ZIP code: city/place names, state, latitude/longitude and the state's primary IANA time zone.Reads text others writeNo findings

    Why it is in this group

    • The name "us_zip_lookup" 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 a US ZIP code: city/place names, state, latitude/longitude and the state's primary IANA time zone. Useful for checkout/address sanity checks and shipping estimates.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
    • idempotentHint: 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 or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
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.

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.2.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http coinvet https://coinvet.pages.dev/mcp
claude mcp add --transport http coinvet https://coinvet.pages.dev/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__coinvet__crypto_address_validate",
      "mcp__coinvet__lightning_address_check",
      "mcp__coinvet__iban_validate",
      "mcp__coinvet__bic_validate",
      "mcp__coinvet__us_zip_lookup"
    ],
    "ask": [
      "mcp__coinvet__btc_price",
      "mcp__coinvet__mempool_fees"
    ],
    "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 coinvet. Review it before you use it.

Capability tags behind 4 rules
  • mcp__coinvet__btc_price untrusted-input
  • mcp__coinvet__mempool_fees untrusted-input
  • mcp__coinvet__lightning_address_check untrusted-input
  • mcp__coinvet__us_zip_lookup untrusted-input

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/dev.pages.coinvet/coinvet/verify?hash=98162a2f5e7ebbdd10dcde2c616c9effa2d4de99b1bdebbb0a3eb9747c1b4fb8" | jq -e '.changed == false'

Pinned hash 98162a2f5e7e, from Nov 22, 2026, 07:18 UTC.

Watch

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

https://radar.anlyon.com/servers/dev.pages.coinvet/coinvet/changes.xml

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

Badge

Anlyon Radar badge for dev.pages.coinvet/coinvet
[![Anlyon Radar](https://radar.anlyon.com/badge/dev.pages.coinvet/coinvet.svg)](https://radar.anlyon.com/servers/dev.pages.coinvet/coinvet)

Source: MCP Registry. Synced Nov 22, 2026, 07:17 UTC.

CoinVet MCP server: questions and answers

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

Is the CoinVet MCP server safe?

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

Can the CoinVet MCP server delete data?

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

Can the CoinVet 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 CoinVet MCP server have?

7 tools: 2 write, 5 read. btc_price, mempool_fees, crypto_address_validate, lightning_address_check, iban_validate, bic_validate and us_zip_lookup.

Does the CoinVet MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the CoinVet MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 22, 2026.