Direct answer

Live Crypto Prices in Claude via MCP

For a live crypto price MCP server for Claude, live_price returns a current price with a verifiable receipt for the call, so a price your agent quotes can be checked later. Without a tool, Claude answers prices from training data: fluent, precise looking, and stale by months. With the tool, the price is read from public market data at the moment you ask, and the receipt fixes what was returned and when. This page covers setup, the ask, and how to read the receipt.

See a receipt before you set anything up: the live demo runs one real call, and this worked example receipt can be checked free at zambo.dev/verify/: zambo.dev/run/28c79cde-20a0-48a3-b4ec-e5d0e3ac104d.

Updated October 20, 2026.

Add Zambo to Claude

Zambo is the verifiable work layer for AI. One connection gives Claude the full server: https://zambo.dev/mcp, 153 tools total, 35 on the default surface, live_price among them.

1. In Claude, open Settings, then Connectors, then add a custom connector.

2. Enter the server URL: https://zambo.dev/mcp.

3. Save the connector and enable it in a new chat.

4. Make a test ask from the next section and confirm Claude answers with a price, a time, and a receipt link. If it answers without a tool call, the connector is not enabled in that chat.

Menu names shift as Claude updates. The URL is the part that matters, and the same URL works in ChatGPT, Gemini, Grok, and Cursor, so a price workflow you build in Claude carries over.

Ask for a price

Ask in plain words and name the asset clearly. Good asks:

"What is the live price of BTC right now? Use live_price and give me the price, the time, and the receipt link."

"Get the current ETH price with live_price, then compare it with the price you quoted me yesterday and show both receipts."

"Price check for a report: SOL, current price, source time, receipt link. Do not use training data."

Naming the tool and asking for the receipt link in the request matters. It steers Claude to call the tool instead of answering from memory, and it makes the answer quotable: price, time, and a link anyone can check, instead of a bare number in a chat bubble. For a day of price and research calls, a Day Pass for $0.99 covers 24 hours. Ongoing use is the Zambo Pass at $29 a month or $290 a year, and $19 a month for $ZAMBO holders. Humans pay by PayPal or card through PayPal. Agents pay USDC on Base via x402.

Read the receipt

Every live_price call returns its result with a verifiable receipt. Read the receipt in three checks:

1. Asset and value. Confirm the receipt names the asset you asked for and the price Claude quoted. A mismatch means the quote drifted from the call.

2. Time. Read the call time on the receipt. That time is what current means for this quote.

3. Verification. Open zambo.dev/verify/ and check the receipt. A match means the saved result is the result returned at that time.

Quote prices with the receipt attached. In a report, a handover, or a client message, the line is: price, time, receipt link. A reader who doubts the number does not have to trust you or Claude; they check the record. Jobs that bundle many calls travel as one record with Zambo handover, and the day can be reviewed in zambo.dev/today.

Stocks and tokens

live_price covers both kinds of ask in the same shape: a token by symbol or name for crypto, a ticker for a stock. The workflow does not change: ask plainly, get the current value read at call time, keep the receipt.

Two habits keep quotes honest across both. First, disambiguate symbols that collide: say the asset class or the full name when a ticker could mean more than one thing. Second, if the tool reports an asset as not covered, accept that answer. A call that says no data, with a receipt saving that answer, is far more useful than a confident number invented to fill the gap.

Rate and freshness notes

Prices come from public market data at call time. That makes them current in a way training data never is, and it also sets the limits of the claim:

Freshness is a moment. The price is accurate to its source at the time on the receipt. A fast market can move seconds later. Fresh decisions need fresh calls.

Sources vary. Public market data aggregates venues that can differ slightly at the same instant. The receipt fixes what this call returned from its source; another source at the same second can print a slightly different number, and both can be honest records of what they read.

Rate is for real use. Free use covers normal asking, and paid passes cover heavier days of calls. Build workflows that call when a price is needed, quote the receipt time, and avoid polling by the second for a number nobody will act on that fast.

Honest limits

A receipt proves what was returned, not that a price was good. It proves the saved result was not changed after the fact: the value, asset, and time on the receipt are what the call returned. It does not prove the price was the best available, that the market source was right, or that acting on the price was wise. Prices also go stale the moment they are printed, so treat every quoted price as a record of a moment, and make a fresh call before any decision that depends on the number.

Frequently asked questions

How do I get a live crypto price in Claude via MCP?

Add Zambo as a connector in Claude with the server URL https://zambo.dev/mcp, then ask Claude for the current price of a token in plain words. Claude calls the live_price tool, which returns a current price from public market data at call time, plus a verifiable receipt for the call. Quote the price with its time and its receipt link, so anyone can check later what was returned and when.

How do I add Zambo to Claude?

In Claude, open Settings, then Connectors, then add a custom connector with the URL https://zambo.dev/mcp. Save it, enable it in a new chat, and ask for a price to confirm the connection works. The same server works in ChatGPT, Gemini, Grok, and Cursor, with 153 tools total and 35 on the default surface.

What does the receipt for a price call prove?

The receipt proves the saved result was not changed after the fact: the price, the asset, and the time recorded for that call are the values that were returned when the call ran, and anyone can check that free at zambo.dev/verify/ with no account. It does not prove the price was good, fair, or the best price available. It proves what was quoted, so a later dispute has a fixed record to check against.

Does live_price cover stocks as well as tokens?

Yes. live_price returns a current crypto or stock price with a verifiable receipt for the call. Ask for a token by its symbol or name, or a stock by its ticker, in the same plain request. If an asset is not covered by the public market data the tool reads, the call says so instead of inventing a number, and that answer is what the receipt saves.

How fresh is the price?

The price is read from public market data at call time, not from model training data and not from a cached page answer. Markets move, so a price is current for the moment on its receipt and stale afterwards by however far the market has moved since. For any decision that matters, make a fresh call and quote the new receipt time rather than reusing an older price.

Related