Prototyp · Vorschau: alle Server aus der offiziellen Registry, alle 30 Minuten synchronisiert. Bewertungen und Benutzerkonten folgen in einem späteren Schritt.
PopNx MCPMCP-Server für alle, die KI nutzen · in einfachen Worten erklärt

CoinVello

von CoinVelloVersion 0.1.4i★ –iComputer oder Cloud
Name in der Registryio.github.CoinVello/coinvello

Installieren

Überblick

Beschreibung vom Entwickler (englisches Original)

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

Die drei Säulen von PopNx MCP

Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.

Was du damit machen kannst

Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.

  • Verbindung: Computer oder Cloud
  • Transport: stdio, Streamable HTTP
  • Kategorie: Krypto & Blockchain
  • Das musst du eintragen: COINVELLO_API_KEY, Authorization

Installation

Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.

Bevor du installierst

  • Basischecks: 3 von 3 bestanden
  • Läuft auf dem Server des Entwicklers: Was du fragst, läuft über dessen Server.
  • Kann 18 Dinge (Tools) create_checkout_session, get_invoice, list_invoices, list_payments …
  • Das trägst du selbst ein: COINVELLO_API_KEY, COINVELLO_API_BASE, COINVELLO_ALLOW_LIVE, Authorization

Als geheim markierte Werte sind Schlüssel zu deinem Konto. Gib sie nie weiter und füge sie nie in einen Chat ein.

Du brauchst

  • Läuft in der CloudNichts zu installieren; die Verbindung läuft übers Internet
  • npmNode.js installiert (für den Befehl npx)

Welche App nutzt du?

Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.

Diese Adresse braucht einen Schlüssel in einem Header der Anfrage, und das Menü zum Hinzufügen von Connectors kann ihn nicht setzen. Nutze stattdessen Claude Code, Cursor oder VS Code.

Oder führ ihn auf deinem Computer aus

Öffne Claude Desktop → Settings → Developer → Edit Config und füge dies in claude_desktop_config.json ein

{
  "mcpServers": {
    "coinvello": {
      "command": "npx",
      "args": [
        "-y",
        "@coinvello/mcp"
      ],
      "env": {
        "COINVELLO_API_KEY": "your-value",
        "COINVELLO_API_BASE": "your-value",
        "COINVELLO_ALLOW_LIVE": "your-value"
      }
    }
  }
}

Führe das in deinem Terminal aus

claude mcp add --transport http coinvello https://mcp.coinvello.com/mcp --header 'Authorization: your-value'

Oder führ ihn auf deinem Computer aus

claude mcp add coinvello --env COINVELLO_API_KEY=your-value --env COINVELLO_API_BASE=your-value --env COINVELLO_ALLOW_LIVE=your-value -- npx -y @coinvello/mcp

Trag die leeren Werte ein, bevor du ihn startest.

In Cursor öffnen

Oder kopier die Einstellungen selbst

In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen

{
  "mcpServers": {
    "coinvello": {
      "url": "https://mcp.coinvello.com/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Oder führ ihn auf deinem Computer aus

In Cursor öffnen

Oder kopier die Einstellungen selbst

In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen

{
  "mcpServers": {
    "coinvello": {
      "command": "npx",
      "args": [
        "-y",
        "@coinvello/mcp"
      ],
      "env": {
        "COINVELLO_API_KEY": "your-value",
        "COINVELLO_API_BASE": "your-value",
        "COINVELLO_ALLOW_LIVE": "your-value"
      }
    }
  }
}

Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.

In VS Code öffnen

Oder kopier die Einstellungen selbst

In .vscode/mcp.json in deinem Projekt einfügen

{
  "servers": {
    "coinvello": {
      "type": "http",
      "url": "https://mcp.coinvello.com/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Oder führ ihn auf deinem Computer aus

In VS Code öffnen

Oder kopier die Einstellungen selbst

In .vscode/mcp.json in deinem Projekt einfügen

{
  "servers": {
    "coinvello": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@coinvello/mcp"
      ],
      "env": {
        "COINVELLO_API_KEY": "your-value",
        "COINVELLO_API_BASE": "your-value",
        "COINVELLO_ALLOW_LIVE": "your-value"
      }
    }
  }
}

Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.

Diese Adresse braucht einen Schlüssel in einem Header der Anfrage, und das Menü zum Hinzufügen von Connectors kann ihn nicht setzen. Nutze stattdessen Claude Code, Cursor oder VS Code.

Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.

Werte, die du selbst einträgst

  • COINVELLO_API_KEY geheim erforderlich env
    CoinVello API key. Use a cv_test_ key while developing; cv_live_ keys are refused unless COINVELLO_ALLOW_LIVE=1.
  • COINVELLO_API_BASE env
    API base URL. Default https://api.coinvello.com/v1; http://localhost:4242/v1 for the local reference server.
  • COINVELLO_ALLOW_LIVE env
    Set to 1 to allow a live key.
  • Authorization geheim erforderlich HTTP header
    Bearer followed by your CoinVello API key, e.g. Bearer cv_test_... (test keys only on the hosted server).

Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.

Was er kann

Tool-Namen und -Beschreibungen genau so, wie der Server sie am 6. Nov. 2026 gemeldet hat. Geschrieben hat sie der Entwickler, nicht wir; wir zeigen sie als reinen Text.

  • create_checkout_session

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

  • get_invoice

    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.

  • list_invoices

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

  • list_payments

    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.

  • create_wallet

    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 o

  • list_wallets

    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.

  • create_webhook

    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"].

  • verify_webhook_signature

    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 " . ", 300 s tolerance, constant-time compare against any v1. Returns valid=t

  • get_credits_balance

    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 l

  • list_credit_bundles

    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%).

  • create_credit_purchase

    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 da

  • list_records

    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 t

  • get_records_summary

    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 occu

  • create_export

    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 s

  • get_export

    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.

  • get_rates

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

  • list_assets

    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 wi

  • simulate_test_payment

    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/larg

Basischecksi

Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 9. Nov. 2026

  • ✓ Bestanden

    Entwickler passt zum Repo

    Der Registry-Name wurde mit dem GitHub-Konto CoinVello bestätigt, dem das Repo gehört

  • … Noch nicht geprüft

    Wird noch gepflegt

    Dieses Repo haben wir noch nicht von GitHub gelesen

  • … Noch nicht geprüft

    Hat eine Lizenz

    Dieses Repo haben wir noch nicht von GitHub gelesen

  • ✓ Bestanden

    Endpunkt antwortet

    Antwort in 419 ms (HTTP 200)

  • – Nicht zutreffend

    Anmeldung mit OAuth

    Keine Anmeldung nötig

  • ✓ Bestanden

    Keine versteckten Anweisungen in Tool-Beschreibungen

    Wir haben 18 Tool-Beschreibungen gelesen und keine versteckten Anweisungen an die KI gefunden

Im Vergleich mit anderen in Krypto & Blockchaini

  • Mehr Sterne als 0 % der anderen 1629 Server in dieser Kategorie
  • Neuer in der Registry veröffentlicht als 87 % der anderen 1629 Server in dieser Kategorie
  • Basischecks gleich gut wie oder besser als bei 100 % der anderen 1629 Server in dieser Kategorie

Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.

Häufige Fragen

Ist CoinVello sicher?

Er hat 3 von 3 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.

Welche Schlüssel oder Codes braucht er?

Das musst du eintragen: COINVELLO_API_KEY, Authorization

Läuft er auf meinem Computer oder in der Cloud?

Beides geht: Installiere ihn auf deinem Computer oder verbinde dich mit der Cloud-Version.

Wird er noch gepflegt?

Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (0.1.4) kam vor 9 Tagen in die Registry.

Welche Apps können ihn nutzen?

Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Er verbindet sich per URL, also funktionieren auch Apps, die Remote-MCP-Server akzeptieren, zum Beispiel ChatGPT im Entwicklermodus.

Was kann ich stattdessen nutzen?

In derselben Kategorie: Kyte, Bykaranteli MCP, Recta

Alternativen

Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.

So liest du eine Karte:↓ Downloads pro Wochei★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti

Kyte

Options on Robinhood Chain: live offers, prices, positions, staking; prepares trades you sign.

von usekyte-orgAm AnfangAktualisiert heute

Läuft in der Cloud✓ kyte.sh

Bykaranteli MCP

Crypto derivatives data: funding, OI, liquidations, options, ETF flows. Free account key required.

von bykarantelicomWachsend↓ 759/Wo.Aktualisiert heute

Computer oder Cloud✓ bykaranteli.com

Recta

Cheaper cross-chain stablecoin routes for AI agents; 5 % of the verified saving, nothing if none.

von RectaBuildAm AnfangAktualisiert heute

Computer oder Cloud

README vom Entwickler

README öffnen

Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.

@coinvello/mcp

Model Context Protocol server for the CoinVello API, the non-custodial crypto payment processor (no KYC, merchant keeps the keys, fees as prepaid credits, 11 networks).

Give Claude, Cursor, Windsurf, ChatGPT or any MCP client the ability to create checkout sessions, inspect invoices and payments, register webhooks, verify webhook signatures, manage credits and simulate test payments while it writes your integration.

npx -y @coinvello/mcp            # stdio (what every desktop client uses)

npx -y @coinvello/mcp --http 3333 # Streamable HTTP on http://127.0.0.1:3333/mcp

# from a checkout of this repo instead

npm install && npm run build && node dist/index.js

Hosted (nothing to install)

https://mcp.coinvello.com/mcp runs this server for you over Streamable HTTP. Send your own key with every request as Authorization: Bearer cv_test_... (or X-CoinVello-Api-Key, or an api_key setting in clients that only take query parameters). The hosted server stores nothing, accepts test keys only, and never logs keys. Run it yourself with npx -y @coinvello/mcp --http --hosted.

{ "mcpServers": { "coinvello": { "url": "https://mcp.coinvello.com/mcp", "headers": { "Authorization": "Bearer cv_test_..." } } } }

Documentation

Website and setup for AI assistantshttps://coinvello.com/ai
Complete integration guide (one file, written for LLMs)https://coinvello.com/llms-full.txt
Developer docs and SDKshttps://coinvello.com/developers
OpenAPI 3.1 referencehttps://coinvello.com/.well-known/openapi.yaml
MCP Registryio.github.CoinVello/coinvello
Sourcehttps://github.com/CoinVello/coinvello-ai (api/ai/mcp-server)
Supportsupport@coinvello.com

Configuration

VariableRequiredMeaning
COINVELLO_API_KEYyescv_test_... from https://coinvello.com/app/settings.php (Settings -> API keys). Any cv_test_ string works against the local mock.
COINVELLO_API_BASEnoDefault https://api.coinvello.com/v1. Use http://localhost:4242/v1 for the reference mock server.
COINVELLO_ALLOW_LIVEnoThe server refuses to start with a `cv_live_` key unless this is 1. Agents should develop against test mode.
COINVELLO_API_VERSIONnoPins CoinVello-Version (default: account version, currently 2026-10-01).

Client setup

Claude Desktop

claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\):

{

"mcpServers": { "coinvello": { "command": "npx", "args": ["-y", "@coinvello/mcp"], "env": { "COINVELLO_API_KEY": "cv_test_..." } } } }

Claude Code
claude mcp add coinvello -e COINVELLO_API_KEY=cv_test_... -- npx -y @coinvello/mcp

or in .mcp.json at the project root (shared with the team, key via env):

{

"mcpServers": { "coinvello": { "command": "npx", "args": ["-y", "@coinvello/mcp"], "env": { "COINVELLO_API_KEY": "${COINVELLO_API_KEY}" } } } }

Cursor

.cursor/mcp.json (project) or ~/.cursor/mcp.json (global):

{

"mcpServers": { "coinvello": { "command": "npx", "args": ["-y", "@coinvello/mcp"], "env": { "COINVELLO_API_KEY": "cv_test_..." } } } }

Windsurf

~/.codeium/windsurf/mcp_config.json:

{

"mcpServers": { "coinvello": { "command": "npx", "args": ["-y", "@coinvello/mcp"], "env": { "COINVELLO_API_KEY": "cv_test_..." } } } }

VS Code (Copilot agent mode)

.vscode/mcp.json:

{

"servers": { "coinvello": { "type": "stdio", "command": "npx", "args": ["-y", "@coinvello/mcp"], "env": { "COINVELLO_API_KEY": "cv_test_..." } } } }

Remote / HTTP clients (ChatGPT connectors, hosted agents)

Run coinvello-mcp --http 3333 behind your own HTTPS reverse proxy and point the client at https://your-host/mcp. The HTTP mode is stateless (one server instance per request) and binds to 127.0.0.1 by default (MCP_HTTP_HOST=0.0.0.0 to change). It uses the key from the environment, so put it behind authentication: it is meant for your own agents, not the public.

Tools

ToolDoes
create_checkout_sessionPOST /checkout-sessions: hosted payment page; returns url to redirect to and invoice_id
get_invoiceGET /invoices/{id} (or GET /checkout-sessions/{cs_id}?expand=invoice)
list_invoicesGET /invoices with status / order_id / email filters
list_paymentsGET /payments with invoice_id / status / chain / tx_hash filters
create_walletPOST /wallets (xpub for BTC, address for EVM/Solana/Tron). Refuses xprv locally.
list_walletsGET /wallets
create_webhookPOST /webhooks; returns the whsec_ secret once
verify_webhook_signatureLocal HMAC check of a CoinVello-Signature header against a raw body (no API call)
get_credits_balanceGET /credits/balance
list_credit_bundlesGET /credits/bundles
create_credit_purchasePOST /credits/purchases; returns payment options + checkout_url
get_ratesGET /rates
list_assetsGET /assets (optional chain filter)
simulate_test_paymentPOST /test/simulate_payment (test keys only)
list_recordsGET /records: the book of record (payments, fees, credit purchases) valued when they happened; filters type / asset / chain / invoice / order / tx / dates / currency
get_records_summaryGET /records/summary: sales, market value received, refunds, fees, net received for a period, optionally grouped
create_exportPOST /exports: CSV, Excel or JSON file of records or any dataset (QuickBooks, Xero, Koinly, CoinTracker, CoinLedger presets); returns the export with download_url
get_exportGET /exports/{id}: poll status until ready, read file.sha256 and download_url

Every tool returns the raw API JSON (also as structuredContent). API errors come back as tool errors containing http_status, the CoinVello error envelope (type, code, message, request_id) and a hint.

Resources

URIContent
coinvello://docs/llms-full.txtComplete single-file integration guide (auth, checkout, redirect, webhook verification, polling, credits, errors, examples in curl/Node/Python/PHP)
coinvello://docs/llms.txtShort llms.txt index
coinvello://openapi.yamlOpenAPI 3.1 specification

Documents are bundled at build time; if missing they are fetched from coinvello.com.

Prompts

integrate-coinvello-into- for nextjs, express, fastapi, flask, django, laravel, rails, sinatra, go, woocommerce, shopify, generic, plus integrate-coinvello-into-framework with a free-form framework argument. Optional arguments: currency, assets. Each prompt tells the agent to read the guide resource, add a checkout route, a raw-body webhook route with signature verification and event.id dedupe, and to verify end to end with simulate_test_payment.

Typical agent session

  1. list_assets -> pick assets the merchant can accept.
  2. create_webhook with the app's /webhooks/coinvello URL -> store the secret in the env file.
  3. Write the code (see the integrate-coinvello-into-* prompt or api/ai/cookbook).
  4. create_checkout_session -> simulate_test_payment on invoice_id with enough confirmations.
  5. get_invoice shows paid; the app's webhook handler was called with a real signed event.
  6. verify_webhook_signature to debug a handler that rejects deliveries.
  7. Bookkeeping: list_records (with include_simulated: true in test mode) -> get_records_summary for a period -> create_export (format: "xlsx") -> get_export until ready -> download the download_url and check file.sha256.

Development

npm install

npm run build # copies docs into dist/docs and compiles TypeScript npm test # smoke test against the mock: needs api/reference-server running on :4242 npm run dev # tsx src/index.ts (stdio)

Smoke test: cd api/reference-server && npm install && npm start, then COINVELLO_API_BASE=http://localhost:4242/v1 npm test here. It exercises all 18 tools, the three resources and the prompts, verifies a real signed delivery captured by the mock's webhook sink, and checks the xprv guard. The mock does not implement wallet CRUD, so create_wallet / list_wallets are expected to return a clean 404 tool error there.

Security notes

  • Keep the server on test keys while an agent is writing code. COINVELLO_ALLOW_LIVE=1 is a deliberate opt-in.
  • The server never logs the API key or webhook secrets. Tool output does include secret from create_webhook because that is the only time the API returns it.
  • create_wallet rejects anything that looks like an extended private key before it leaves the machine.
  • Nothing here moves funds: CoinVello is non-custodial, and the API has no "send" operation.

License MIT. Source: https://github.com/CoinVello/coinvello-ai (mirror). Issues: https://github.com/CoinVello/coinvello-ai/issues or support@coinvello.com

PopNx fragen