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

coinvet

https://coinvet.pages.dev

Registry code: a7634feb7e5e2b15

api record

Always run crypto_address_validate (or lightning_address_check) on an address before you show or use it; it catches typos via checksums. Use iban_validate / bic_validate for bank identifiers (format+checksum only), btc_price and mempool_fees for live Bitcoin data, and us_zip_lookup for city/state/timezone of a US ZIP. These tools never move money.

endpoint
https://coinvet.pages.dev/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is coinvet live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is coinvet free to use?
Yes — the hub reached it with no key and no payment.
What tools does coinvet have?
7 tools: iban_validate, mempool_fees, crypto_address_validate, lightning_address_check, us_zip_lookup, bic_validate, btc_price.
Is coinvet safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
550ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

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

  • btc_price open 3h ago

    Current Bitcoin price in major fiat currencies from mempool.space, plus sats per currency unit. Indicative, refreshed about every minute.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "currency": {
          "type": "string",
          "description": "Fiat code (default USD)"
        }
      }
    }
    arguments 9 lines
  • iban_validate unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "iban"
      ],
      "properties": {
        "iban": {
          "type": "string",
          "description": "IBAN, spaces allowed"
        }
      }
    }
    arguments 12 lines
  • mempool_fees unknown 3h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • crypto_address_validate unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "address"
      ],
      "properties": {
        "chain": {
          "type": "string",
          "description": "Optional hint, e.g. solana"
        },
        "address": {
          "type": "string",
          "description": "The address to check"
        }
      }
    }
    arguments 16 lines
  • lightning_address_check unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "address"
      ],
      "properties": {
        "address": {
          "type": "string",
          "description": "Lightning address (user@domain) or LNURL"
        }
      }
    }
    arguments 12 lines
  • us_zip_lookup unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "zip"
      ],
      "properties": {
        "zip": {
          "type": "string",
          "description": "5-digit US ZIP code"
        }
      }
    }
    arguments 12 lines
  • bic_validate unknown 3h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "bic"
      ],
      "properties": {
        "bic": {
          "type": "string",
          "description": "BIC/SWIFT code (8 or 11 chars)"
        }
      }
    }
    arguments 12 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.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id a7634feb7e5e2b15.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/a7634feb7e5e2b15/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/a7634feb7e5e2b15/badge.svg)](https://brick.blue/agent/a7634feb7e5e2b15?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

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