FinCobra MCP connects an AI client to a FinCobra Checkout (invoicing) and Watchlist (portfolio) account over Streamable HTTP with OAuth, exposing 5 tools.
Create Checkout invoices (create_invoice, checkout:write): make a USD invoice with optional description, customer email, and merchant reference; returns the hosted payment URL and status.
Look up invoices (get_invoice, checkout:read): fetch status, payment URL, and USD amounts (received, confirmed, remaining) by invoice id.
Read net worth (get_net_worth, watchlist:read): banks, cash, property, and manual totals plus source counts and notes; note that live crypto USD balances always come back as null.
List portfolio sources (list_sources, watchlist:read): wallets, exchanges, and manual bank/cash/property entries with values, mortgage balances, and stored token cost-basis (PnL) rows.
Get one source (get_source, watchlist:read): retrieve a single source by id (e.g. wallet:12, exchange:binance, manual:3).
No editing of watchlist data: the server does not add wallets, edit assets, or manage cars, and it cannot create or modify anything except Checkout invoices.
Provides read-only access to Binance exchange data from the Watchlist, allowing retrieval of source information for a specific Binance wallet or account.
Supports creating USD invoices payable in Bitcoin (BTC) on the Bitcoin network and tracking their payment status.
Supports accepting USDT and USDC payments on the Ethereum mainnet for created invoices.
Supports accepting USDT and USDC payments on the Solana network for created invoices.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@FinCobra MCP Create a $250 invoice for consulting services"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
FinCobra MCP 0.4.0 connects an AI client to your Checkout and Watchlist account. Use this Streamable HTTP server URL:
https://watch.fincobra.com/api/mcpAdd the URL as a remote MCP server in your client. Select Connect or Sign in, complete FinCobra sign-in in your browser, and approve the permissions shown. Return to your AI client when the browser finishes.
For Codex:
codex mcp add fincobra --url https://watch.fincobra.com/api/mcp
codex mcp login fincobra --scopes watchlist:read,checkout:readCodex can start browser authorization during mcp add and request all supported permissions. For a read-only connection, close that initial prompt and use the explicit mcp login --scopes command above.
For Claude Code:
claude mcp add --transport http fincobra https://watch.fincobra.com/api/mcpThen use /mcp in Claude Code to sign in. In clients with an MCP settings screen, use the same URL and their connection control. The client must support Streamable HTTP and MCP OAuth.
The client stores OAuth credentials and renews access automatically. Access tokens last one hour. A connection lasts up to 90 days. After expiry or revocation, the client opens browser authorization again. Revoke a connection in FinCobra Settings → Security → Connected MCP clients.
Related MCP server: Yolfi MCP Server
Ask your agent: “Check my FinCobra connection.” It should call get_connection_status and return the account ID, approved scopes, access expiry, and server version. To read your portfolio, ask it to call get_net_worth.
A saved server entry alone does not prove that the client loaded its tools. If tools are absent, check the MCP server status in the client, sign in if required, and use its reload control. Clients that load tool definitions only when a conversation starts require a new conversation after setup.
When a client omits scopes, FinCobra uses watchlist:read and checkout:read. Some clients request all advertised scopes. Check the permissions on the consent page. Only tools covered by the approved scopes are listed. To enable writes, request the additional scope in your MCP client's OAuth settings and approve it in the browser. In Codex, use:
codex mcp login fincobra --scopes watchlist:read,checkout:read,watchlist:write,checkout:writeTool | Required scope | Result |
| Any valid connection | Account, scopes, access expiry, and version |
|
| Portfolio totals and all sources |
|
| Wallets, exchanges, bank/cash entries, property, and cars |
|
| One source selected by its ID |
|
| One Checkout invoice selected by its ID |
|
| Add a manual car valuation |
|
| Create an invoice and return its payment URL |
get_net_worth, list_sources, and get_source accept an optional currency. USD is the default. Original amounts and USD values remain in the response when another reporting currency is selected. sourceBalances keeps available, staked, Spot, Funding, and Earn amounts separate where the source provides them. lockedBalance is separate from these available source amounts.
Supported reporting currencies are USD, VND, EUR, GBP, JPY, SGD, AUD, CAD, CHF, CNY, RUB, GEL, THB, BTC, and XAU. XAU means one troy ounce of gold.
Responses include tracked wallets, exchanges (including Hyperliquid), and manual assets. Property values use net equity after the recorded mortgage. Manual entries are estimates that you maintain in Watchlist.
Unsupported tokens hidden by Watchlist have includedInTotal: false, exclusionReason: "unsupported_token", and no invented price. They do not block portfolio totals. If a supported asset or source cannot be valued, the response marks its status and leaves affected totals unavailable. Check valuationStatus and notes before using an incomplete total.
FinCobra Identity provides authorization-code OAuth with S256 PKCE, resource binding, dynamic client registration, public client metadata documents, rotating refresh tokens, and revocation. Browser consent uses your FinCobra account and applies only to the listed permissions.
Protected resource metadata: https://watch.fincobra.com/.well-known/oauth-protected-resource/api/mcp
Authorization server metadata: https://watch.fincobra.com/.well-known/oauth-authorization-server
MCP resource: https://watch.fincobra.com/api/mcp
An unauthenticated MCP request returns HTTP 401 with the protected resource metadata URL in WWW-Authenticate. OAuth clients discover the endpoints from these documents. Authorization codes and tokens are bound to their client and resource. Refresh token reuse revokes the connection. Account security changes also invalidate access.
The fincobra-mcp npm package contains the hosted MCP handler and typed FinCobra clients. FinCobra Identity uses version 0.4.0. Client setup uses the hosted URL above.
createFincobraMcpHandler takes trusted service URLs and a resolveAccessToken callback. The callback must validate the bearer token against the authorization server and return its account, client, scopes, resource, and expiry. The handler checks the resource, expiry, and browser origin before it creates the MCP context for that request.
Development checks:
npm ci
npm run build
npm run lint
npm testCreate a FinCobra Checkout invoice in USD and return the hosted payment URL. Payment methods (Bitcoin, Ethereum USDT/USDC, Solana USDT/USDC, Arbitrum One USDC, Base USDC) are those enabled in the merchant dashboard.
Inputs: amountUsd (required), description, customerEmail, merchantReference. Returns: id, status, amountUsd, paymentUrl, +6 more
Look up a known FinCobra Checkout invoice by id. Returns status, hosted payment URL, and amounts.
Inputs: invoiceId (required). Returns: id, status, amountUsd, paymentUrl, +6 more
Read Watchlist net worth from existing list APIs. Banks, cash, and property are manual entries. Live crypto USD balances are not on the list API and come back as null.
Inputs: no named parameters. Returns: notes, cashUsd, banksUsd, cryptoUsd, +4 more
Look up one Watchlist source by the id returned from list_sources.
Inputs: sourceId (required). Returns: id, kind, label, value, +8 more
List Watchlist wallets, exchanges, and manual bank/cash/property sources. Includes stored token PnL cost-basis rows when the API has them. Does not add wallets or edit assets.
Inputs: no named parameters. Returns: sources
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 5 tools
All five tools have clearly distinct responsibilities: invoice lookup/creation are separate, and net-worth/source actions are separate. get_source and list_sources follow the standard item-vs-collection pattern. There is no meaningful overlap.
Names consistently follow a verb_noun pattern: get_invoice, create_invoice, list_sources, get_source, and get_net_worth. The convention is uniform and predictable across both subdomains.
Five tools is a compact, appropriate size for a server covering Checkout invoices and Watchlist reads. Each tool serves a distinct need without redundancy.
The invoice side covers create and lookup but not list, cancel, or update operations, and the Watchlist side is read-only with no way to add or edit sources. These are notable lifecycle gaps, though the core read and checkout workflows are present.
Manage Apollo invoices and customers with entity-scoped OAuth and optional read/write access.
Create and manage checkout pages, event ticketing, forms, customers, payments and subscriptions.
Non-custodial crypto payments: checkout sessions, invoices, webhooks and test payments. No KYC.
Read payment settings, orders and receipts, create payment links and API keys.
