Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

CoinVello

REMOTE · MCP.COINVELLO.COM · 2 COMPONENTS

Non-custodial crypto payments: checkout sessions, invoices, webhooks and test payments. No KYC.

67 Trust /100

Last scanned (13 hours ago)

Scores higher than 53% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability73
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 3546 tokens (~168/item across 21 items; 18 tools + 3 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 60% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 18 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 1 Nov 26 65

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://mcp.coinvello.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.coinvello.com CN=YE2,O=Let's Encrypt,C=US 1 Nov 2026 30 Jan 2027 ECDSA 256 ECDSA-SHA384 5d82b7c64d4df2b371f1af3200f5f7b7631
SANs: mcp.coinvello.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.coinvello.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
coinvello.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
referrer-policy no-referrer

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.coinvello.com/mcp Verified 200
http (plaintext) http://mcp.coinvello.com/mcp HTTPS enforced
MCP tools · 18 exposed · ~3,241 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
create_checkout_session ~401

Create a CoinVello hosted checkout session (an invoice plus a payment page at pay.coinvello.com). Redirect the customer to the returned `url`. Amounts are decimal strings. `currency` is an ISO code (USD, EUR...) or an asset id to price in crypto. Fulfil orders from the invoice.paid webhook, never from the redirect.

NameTypeReqDescription
accepted_assetsarray–Assets the customer may pay with; defaults to all assets with an enabled wallet.
amountstringyesTotal to charge, e.g. "49.99".
brandingobject––
cancel_urlstring––
collect_emailboolean––
currencystringyesISO 4217 code such as USD/EUR/GBP, or an asset id such as btc:bitcoin.
customerobject––
descriptionstring––
expires_ininteger–Seconds until expiry (default 1800).
idempotency_keystring–Stable key per order so retries do not create duplicate sessions, e.g. order-123-checkout.
line_itemsarray––
localestring––
metadataobject–Up to 50 string key/value pairs returned on the object and in webhooks.
order_idstring–Your order reference; indexed and searchable.
redirect_onstring–When the hosted page redirects to success_url (default confirming).
success_urlstringyesWhere the hosted page sends the customer after payment.
taxobject–The tax portion of the sale as you computed it, in the invoice currency and included in `amount` (e.g. {"amount":"7.98","rate":"0.19","label":"VAT 19%","jurisdiction":"DE"}); copied to the records an…

No output schema declared.

No examples provided.

create_credit_purchase ~199

Create a crypto credit purchase (cpu_...). Returns payment.payment_options with the address/amount to pay (CoinVello's operator wallet) and a hosted checkout_url. Credits are added when the payment confirms. Card purchases and automatic top-up are set up by the merchant in the dashboard, not through this tool. In test mode credits are free, so this is mainly for exercising the flow (pay it with simulate_test_payment).

NameTypeReqDescription
bundle_idstringyesFrom list_credit_bundles, e.g. bnd_growth_15000.
expires_ininteger––
idempotency_keystring––
metadataobject–Up to 50 string key/value pairs returned on the object and in webhooks.
pay_assetstring–Asset symbol to pay with, lowercase, e.g. usdt. Requires pay_chain. Omit for every option.
pay_chainstring––

No output schema declared.

No examples provided.

create_export ~341

Create an export of the records (default), another dataset, or `all` (the year-end package) for a period, or for the entire history when period is null or omitted. Returns the export object: small exports are already `ready` with `file` (name, content_type, bytes, sha256) and a signed `download_url` valid until `download_expires_at` (files are kept 7 days); while `queued` or `processing` call get_export. Vendor presets (quickbooks, xero, koinly, cointracker, coinledger) and journal need dataset=records and format=csv (otherwise 422). Verify the downloaded file against file.sha256. With a test key pass include_simulated=true to include simulated payments.

NameTypeReqDescription
currencystring–Reporting currency of the value columns.
datasetstring–Default records.
formatstringyes–
idempotency_keystring–Stable key so a retry does not start a second export, e.g. records-2026-q3.
include_simulatedboolean–Test mode only: include rows created by simulate_test_payment, which the sandbox hides by default. Ignored with a live key.
metadataobject–Up to 50 string key/value pairs returned on the object and in webhooks.
period––Read in `timezone`. Null or omitted exports the entire history.
presetstring–Column layout for the records dataset (default generic).
timezonestring–IANA zone, e.g. America/New_York. Default: the account's records timezone.

No output schema declared.

No examples provided.

create_wallet ~351

Register a receiving wallet the merchant controls. type=xpub for bitcoin (CoinVello derives a fresh address per invoice from the extended PUBLIC key); type=address for ethereum, base, arbitrum, optimism, polygon, bnb, avalanche, robinhood, solana, tron. Never pass a private key or seed phrase. The wallet is usable at once in live and test mode; addresses are validated strictly (format, checksum, network, no token contracts). For xpubs, show the returned first_address so the merchant can compare it with their wallet's first receive address. Signed-message verification (POST /wallets/{id}/verification then /verify) is optional and never required.

NameTypeReqDescription
addressstring–Checksummed EVM address, Solana pubkey or Tron address. Required when type=address.
address_typestring––
assetsarray–Assets accepted at this address, e.g. ["usdc:polygon","usdt:polygon"]. Defaults to the native asset. Each must be listed by list_assets for the key's mode.
chainstringyes–
derivation_pathstring–Account path such as m/84'/0'/0'. Inferred from the prefix when omitted.
enabledboolean––
labelstringyes–
metadataobject–Up to 50 string key/value pairs returned on the object and in webhooks.
start_indexinteger––
typestringyes–
xpubstring–xpub/ypub/zpub (BTC), tpub/upub/vpub (testnets) or an output descriptor. Required when type=xpub.

No output schema declared.

No examples provided.

create_webhook ~162

Register a webhook endpoint. The response contains `secret` (whsec_...) ONCE: store it as COINVELLO_WEBHOOK_SECRET. Live endpoints must be HTTPS; test endpoints may be http://localhost. Use events ["*"] for everything or a list such as ["invoice.paid","invoice.expired"].

NameTypeReqDescription
descriptionstring––
enabledboolean––
eventsarrayyesEvent types or ["*"]. Common: invoice.paid, invoice.confirming, invoice.underpaid, invoice.overpaid, invoice.expired, payment.detected, checkout_session.completed.
metadataobject–Up to 50 string key/value pairs returned on the object and in webhooks.
urlstringyes–

No output schema declared.

No examples provided.

get_credits_balance ~98

Return the merchant's prepaid processing-credit balance: balance (= available + reserved, never negative), available (free to spend), reserved (estimated fees of open invoices paid with credits), low_balance_threshold, estimated_payments_remaining, auto_topup. There are no free live credits. 1 credit = $0.01 nominal; a confirmed payment consumes about 30 bps of its fiat value (floor 2, cap 2000).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_export ~74

Retrieve an export (exp_...): status (queued, processing, ready, failed, expired), rows, file { name, content_type, bytes, sha256 }, download_url and download_expires_at, failure_reason. Poll after create_export until ready.

NameTypeReqDescription
idstringyesexp_... id from create_export

No output schema declared.

No examples provided.

get_invoice ~77

Retrieve an invoice (inv_...) with its status, payment_options (address, amount, payment_uri, qr_payload) and paid summary. Use for polling or reconciliation. Accepts a checkout session id (cs_...) too and returns the session with the invoice expanded.

NameTypeReqDescription
idstringyesinv_... or cs_... id

No output schema declared.

No examples provided.

get_rates ~65

Mid-market rates for supported assets against a fiat base (default USD). Indicative only; invoices lock their own rate at creation.

NameTypeReqDescription
assetsarray–Restrict to these asset ids.
basestring–ISO 4217 code or asset id, default USD.

No output schema declared.

No examples provided.

get_records_summary ~257

Sales (invoiced at the locked rates), received_market_value (what the coins were worth when they landed), valuation_difference, tax_collected, refunds, fees_prepaid and credits_consumed, fees_onchain, network_fees, credit_purchases and net_received, with payment counts, over occurred_at in the given timezone and currency. period_start is inclusive and period_end exclusive (a date such as 2026-01-01, or a date-time). group_by returns the same totals per month, asset, chain, type or address in `groups`. With a test key, simulated rows count only with include_simulated=true.

NameTypeReqDescription
currencystring––
group_bystring––
include_simulatedboolean–Test mode only: include rows created by simulate_test_payment, which the sandbox hides by default. Ignored with a live key.
period_endstringyesExclusive.
period_startstringyesInclusive, read in `timezone`: a date (2026-01-01) or a date-time.
timezonestring–IANA zone used to bucket occurred_at, e.g. Europe/Berlin. Default: the account's records timezone.

No output schema declared.

No examples provided.

list_assets ~145

Every asset CoinVello accepts in the API key's mode: id (btc:bitcoin, usdc:polygon, eurc:base...), symbol, chain, kind (native/token), contract_address, decimals, required_confirmations, min_amount, testnet name and the wallet_type (xpub or address) needed to accept it. Tokens without a testnet contract (DAI, usdc:bnb, usdt on base/arbitrum/optimism/avalanche/solana, and the Bitcoin tokens wbtc/cbbtc/btcb) are live-only, so a test key does not list them.

NameTypeReqDescription
chainstring–Filter by chain.

No output schema declared.

No examples provided.

list_credit_bundles ~53

List purchasable credit bundles with USD price, price_per_credit and indicative crypto_prices per asset. Bigger bundles cost less per credit (effective rate ~0.30% down to <0.10%).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_invoices ~119

List invoices, newest first, filterable by status, order_id or customer_email. Returns { object: 'list', data, has_more, next_cursor }.

NameTypeReqDescription
created_gtestring–RFC 3339 timestamp
created_ltestring–RFC 3339 timestamp
cursorstring–next_cursor from the previous page.
customer_emailstring––
limitinteger–Page size (default 20).
order_idstring––
statusstring––

No output schema declared.

No examples provided.

list_payments ~104

List on-chain payments (pay_...) with tx_hash, confirmations, amount and status (detected, confirming, confirmed, failed). Filter by invoice_id, status, chain or tx_hash.

NameTypeReqDescription
chainstring––
cursorstring–next_cursor from the previous page.
invoice_idstring––
limitinteger–Page size (default 20).
statusstring––
tx_hashstring––

No output schema declared.

No examples provided.

list_records ~352

List the account's book of record, newest first: one immutable row per movement of value (payment_received, fee_prepaid, credit_purchase, refund_sent, fee_onchain, conversion, offramp_payout...) valued when it happened. Each record has `value` (market value at the block time in the reporting currency, rate and source included), `value_usd`, `contract_value` (what the customer owed at the invoice's locked rate), `tax`, the on-chain proof (tx_hash, block_height, addresses, explorer_url) and an invoice snapshot. `currency` re-values from value_usd at the historical rate. With a test key, rows created by simulate_test_payment appear only with include_simulated=true. Returns { object: 'list', data, has_more, next_cursor }.

NameTypeReqDescription
assetstring–Records whose received, sent or fee leg is this asset.
chainstring––
currencystring–Re-value `value` into this currency (default: the account's reporting currency).
cursorstring–next_cursor from the previous page.
include_simulatedboolean–Test mode only: include rows created by simulate_test_payment, which the sandbox hides by default. Ignored with a live key.
invoice_idstring––
limitinteger–Page size (default 20).
occurred_gtestring–RFC 3339 timestamp; block time at or after.
occurred_ltestring–RFC 3339 timestamp; block time at or before.
order_idstring––
tx_hashstring––
typestring––

No output schema declared.

No examples provided.

list_wallets ~83

List registered wallets with chain, type, status (active/verified/archived) and accepted assets. Use it to see which assets can be offered on an invoice.

NameTypeReqDescription
chainstring––
cursorstring–next_cursor from the previous page.
limitinteger–Page size (default 20).
statusstring––

No output schema declared.

No examples provided.

simulate_test_payment ~177

Create a synthetic on-chain payment for an invoice (inv_) or credit purchase (cpu_) and run it through the real state machine and webhook pipeline. Test keys only. confirmations=0 -> payment.detected / invoice.pending; confirmations >= required -> invoice.paid. Use a smaller/larger amount to simulate underpaid/overpaid. Reuse tx_hash to advance the same payment.

NameTypeReqDescription
amountstring–Amount in the asset; defaults to the exact payment_options[].amount.
assetstring–Which payment option to pay; defaults to the first accepted asset.
confirmationsinteger–Default 0 (detected only).
delay_secondsinteger––
from_addressstring––
invoice_idstringyesinv_... or cpu_...
tx_hashstring––

No output schema declared.

No examples provided.

verify_webhook_signature ~183

Verify a webhook delivery locally (no API call). Pass the exact raw request body, the CoinVello-Signature header (t=...,v1=...) and the endpoint secret (whsec_...). Implements the spec: HMAC-SHA256 over "<t>.<raw body>", 300 s tolerance, constant-time compare against any v1. Returns valid=true/false with the reason and the parsed event. Set ignore_timestamp=true when checking an old captured delivery.

NameTypeReqDescription
ignore_timestampboolean–Skip the replay-window check (only for inspecting historical deliveries).
raw_bodystringyesRaw body bytes exactly as received (no re-serialisation).
secretstringyesEndpoint secret whsec_...
signature_headerstringyesValue of the CoinVello-Signature header.
tolerance_secondsinteger––

No output schema declared.

No examples provided.

Install

How do I install the CoinVello MCP server?

CoinVello is a hosted endpoint at https://mcp.coinvello.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.coinvello.com

# add to Claude Code
claude mcp add --transport http coinvello-coinvello 'https://mcp.coinvello.com/mcp'
Common questions

What is the CoinVello MCP server?

CoinVello is an MCP server listed in the public MCP registry as io.github.CoinVello/coinvello. Non-custodial crypto payments: checkout sessions, invoices, webhooks and test payments. No KYC. This page covers its hosted endpoint (https://mcp.coinvello.com/mcp).

Is the CoinVello MCP server safe to use?

CoinVello scores 67 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the CoinVello MCP server expose?

CoinVello exposes 18 tools: create_checkout_session, get_invoice, list_invoices, list_payments, create_wallet, and 13 more. Their descriptions and schemas cost roughly 3,241 tokens of context every time the server is loaded.

Does the CoinVello MCP server require authentication?

No. We connected to CoinVello without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the CoinVello MCP server still maintained?

CoinVello is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the CoinVello MCP server?

VerifyMCP ran 12 checks on CoinVello, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about CoinVello: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.