← Back to directory

Bitpont MCP

Bitpont · Crypto & Digital Assets

MCP ServerCommunity

Bitpont provides remote and local MCP access to crypto market discovery, wallet and position reads, and DeFi transaction workflows across supported networks and venues. It documents transaction preparation, wallet-authorized submission, and settlement recovery for supported actions. Advisory investment and operations teams could use it to research digital assets, inspect client-authorized wallet activity, and reconcile transactions, while developers could integrate these workflows into internal tools.

cryptodefiwallet datatransaction preparationsettlement trackinglocal signingremote mcp
Status
Community
Auth
None
Hosting
Both
Community rating
Not rated yet
Role

Normalizes several systems behind one interface. Hides many underlying providers behind a single normalized shape. More on Aggregator servers → All seven roles →

Open documentation →

Caveats

  • Capabilities and integration coverage are vendor-reported and have not been independently verified. Published market identities and catalogue entries do not establish live liquidity, rates or executable routes.
  • This is not read-only or limited to unsigned drafts. The vendor documents submission of authorized signatures or signed transactions, local wallet execution, and customer sessions that can execute previously authorized actions without another wallet prompt.
  • Keyless access is the vendor-reported default, with public rate limits. Scoped partner access uses BITPONT_API_KEY; native venues and private account workflows can impose additional wallet, session or access requirements.
  • Local execution does not mean all workflow data stays local. The vendor documents private workspaces holding tasks and execution receipts, with a reusable workspace secret. The supplied page does not specify retention terms or a complete data-custody policy.
  • Coverage is product-, network- and venue-specific. The vendor warns that simulations do not guarantee settlement or all-in costs, bridge source confirmation is distinct from destination delivery, and a submission timeout may still mean a transaction was sent.
  • The vendor specifies Node.js 20 or newer for the local adapter and an owner-controlled local signer for Options MCP workflows. No adapter license or independent production-readiness assessment is provided in the supplied material.
  • Start with read-only scopes and keep client-side approval prompts on until the connection is proven.
Rate this server

How to connect Bitpont MCP

Step 1

Remote server: paste a URL

Bitpont MCP publishes a remote (Streamable HTTP) endpoint, so nothing is installed locally. Add it as a custom connector in Claude, ChatGPT or your IDE and paste the endpoint below.

Endpoint

https://www.bitpont.com/api/v1/mcp

Client config snippet

{
  "mcpServers": {
    "25b695f6-548d-4caa-855d-406966642d1f": {
      "url": "https://www.bitpont.com/api/v1/mcp"
    }
  }
}

Step 2

Authenticate with no credentials

No credentials are required for public data. Rate limits still apply, so avoid bulk pulls from a chat client.

Step 3

Verify, then widen access

Restart your client, confirm the server's tools appear, and run one read-only question first. Keep client-side approval prompts on for any tool that can write, trade or send. Confirm with your firm's compliance policy before connecting systems holding client data.

Prompts that use this server

Starter prompts from the Practice Stacks that rely on Crypto & Digital Assets.

Digital asset holdings snapshot

One consolidated view across exchanges and wallets.

Crypto & Digital AssetsCrypto & Digital AssetsBrokerage & Trade Execution

Read-only: consolidate my digital asset holdings across every connected source, exchange accounts, on-chain wallet or explorer tools, and any brokerage account holding crypto or crypto ETPs, into one table: asset, quantity, venue, source tool, USD value and share of total. Show a per-source subtotal so I can see which tool reported what, and flag any asset that appears in more than one source so it is not double-counted. Mask wallet addresses beyond the first and last four characters. Do not trade, transfer, approve or sign anything.

Guardrail · Read-only keys only. Never give a chat tool withdrawal or signing permissions.

Cost basis and realised gains review

A tax-ready view of what was sold and when.

Crypto & Digital AssetsCrypto & Digital AssetsAccounting & Tax

Read-only: list realised gains and losses on digital assets for <tax year> by combining exchange transaction history with on-chain transfer data, then compare the result to what is already recorded in my accounting or tax system. Show acquisition date, disposal date, proceeds, basis and the source tool for each line, and flag every transaction where basis is missing, inferred, or disagrees between the exchange and the books. Do not file, submit, amend or post any journal entry. This is a working draft for the tax preparer.

Guardrail · Draft only. Crypto basis data is often incomplete, verify before filing.

Venue and counterparty risk review

Where the assets actually sit and what that exposes you to.

Crypto & Digital AssetsCrypto & Digital AssetsBrokerage & Trade Execution

Read-only: map where my digital asset exposure actually sits by combining exchange or custodial venue data, on-chain wallet and staking or DeFi data, and any crypto exposure held through brokerage accounts. For each venue describe the counterparty, smart-contract and liquidity risk, and note any concentration above <threshold>% of total digital assets across all sources combined. State which figures came from which tool and what you could not verify on-chain. No recommendations to move funds and no transactions.

Guardrail · Read-only. Never approve token allowances or transactions from a chat session.

Read the full connection guide →