Integration

Chargeblast integration

Chargeblast prevents card chargebacks with pre-dispute alerts (Ethoca, Visa CDRN and RDR, Amex, Discover). List and read alerts and action them (refund or decline) before they turn into chargebacks, list chargeback disputes with their win likelihood and evidence status, upload orders and disputes so alerts can be matched, check an order's Compelling Evidence eligibility, and enroll or unenroll merchants' billing descriptors in the alert programs. Card numbers, authorization codes, customer emails and ids, external links, evidence file links and free-form alert metadata are not returned; the order list, the raw order and receipt record, deflection logs, IP-data upload, the separate credit-request route and all account settings (integrations, keys, users, invitations, billing) are not exposed. Webhooks are set up in the Chargeblast dashboard. Authentication is an API key sent in the X-API-Key header (Chargeblast dashboard, Settings, Developer); each company has its own key.

Connect Chargeblast How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Chargeblast.Built from the 13 Chargeblast tools below, on the connection you add once.

What you can do with Chargeblast

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Alert, 3 operations

get_alertGet alertGETReturns one alert by its Chargeblast id (from list_alerts or a webhook): network, amount, descriptor, reason code, credit and resolution state.
list_alertsList alertsGETLists alerts, newest page first, filtered by network, reason code, match state or creation date. Pages start at 1 (per, default 10). Use the id with get_alert or update_alert.
update_alertUpdate alertPOSTActions an alert for real: tells the issuing bank whether a refund will be issued. Only the first update is acted on by the bank; a decline code lets the chargeback go ahead. Unactioned alerts are declined after 48 hours.

Merchant, 3 operations

enroll_merchantEnroll merchantPOSTFiles a real enrollment request with the card network for one program. ethoca, cdrn: descriptors. rdr: arns and/or paired bins and caids. amex, discover: legal, SE and address fields. Records start Pending.
get_merchantGet merchantGETReturns one merchant with its sites and the descriptors enrolled for each (network, status). Leave merchant_id out for the merchant tied to the API key.
list_merchantsList merchantsGETLists the merchants of the account (id and name) for multi-merchant accounts. Pages start at 1 (per, default 10). Use the id with get_merchant or enroll_merchant.

Descriptor, 2 operations

list_descriptorsList descriptorsGETLists descriptor records, one per descriptor, with program, status, name (or BIN and CAID for RDR) and merchant id. Filter by program or status. Pages start at 1 (per, default 10, max 1000).
unenroll_descriptorsUnenroll descriptorsPOSTUnenrolls descriptors for real. Pending ones are removed at once (removed); live ones are queued for provider removal (queued, status PendingRemoval). Ids come from list_descriptors.

Dispute, 2 operations

list_disputesList disputesGETLists chargeback disputes with status, reason, amount, response deadline, win likelihood and linked alerts, deflections and evidence submissions. Pages start at 1 (per, default 10, max 100).
upload_disputesUpload disputesPOSTUploads up to 100 disputes; each references an order by chargeId (from upload_orders) or carries an order to create. Re-uploading an id updates it. Returns succeeded ids and failed ones with reasons.

Order, 2 operations

get_order_compelling_evidenceGet order compelling evidenceGETReturns whether an uploaded order is eligible for Compelling Evidence 3.0 (pre-dispute re-presentment) and, if not, why. Pass the order id sent with upload_orders.
upload_ordersUpload ordersPOSTUploads orders (charges) so Chargeblast can match alerts and disputes to them, and for digital receipts and Compelling Evidence. Amounts in cents. Rate limit: 100 requests per 10 seconds.

Enrollment, 1 operation

get_enrollment_statusGet enrollment statusGETReports the merchant's enrollment status per program (ethoca, cdrn, rdr, amex, discover): none, pending or enrolled, with the descriptor records behind each and the RDR ARNs on file.

Use Chargeblast from Claude Code, Cursor or Codex

Connect Chargeblast in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Chargeblast operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Chargeblast

Create your workspace
Sign up free. Nothing to install.
Connect Chargeblast once
Add your Chargeblast connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.