MCP Server

The Findustry AI MCP server exposes chargeback tools returning outcomes rather than a raw database row. All requests authenticate with a secret key.

Connecting

Setting	Value
Transport	`http` (streamable)
Host	`https://mcp.findustryai.com/`
Authentication Header	`Authorization: sk_findustryai_kkkkkkkkkkkk_nnnn`

Tools

Tool	Category	Description
`chargeback_list`	Read	List chargebacks for a merchant, with status and due date
`chargeback_get`	Read	Full detail for one chargeback, including activity history
`chargeback_due`	Read	Chargebacks requiring action, soonest due first
`chargeback_recommend`	Read	Recommendation to respond or accept, with rationale
`chargeback_status`	Read	Submission status for one chargeback
`evidence_requirements`	Read	The defense requirements and time limit for a card network reason code
`evidence_check`	Read	Evidence gaps against the reason code requirements
`evidence_attach`	Write	Attach an evidence document to a chargeback
`letter_generate`	Write	Draft a response letter with rule citations
`chargeback_respond`	Write	Approve and submit the response for a chargeback requiring action
`chargeback_accept`	Write	Accept liability for a chargeback requiring action
`metrics_query`	Analysis	Win rate, repeat-payer, prior-transaction, Compelling Evidence 3.0, and amount statistics across reachable merchants
`portfolio_summary`	Analysis	Metrics rolled up across reachable merchants
`merchant_list`	Admin	Every merchant a system-level key can reach, with the id and external merchant id `merchantId` accepts elsewhere

Write tools require an idempotencyKey.

Calling a tool

POST /
Authorization: sk_findustryai_kkkkkkkkkkkk_nnnn
Content-Type: application/json

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "chargeback_list",
    "arguments": {
      "merchantId": "565500000928297"
    }
  }
}

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "content": [
      {
        "type": "text",
        "text": "{ \"data\": [ { \"id\": \"...\", \"status\": \"action_required\", \"dueDate\": \"...\" } ] }"
      }
    ]
  }
}

Merchant Scope

merchantId is required to scope requests to a single merchant. Requests without merchantId will fail with 400 Bad Request. merchant_list, metrics_query, and portfolio_summary do not take merchantId.

Errors

Status	Cause
`401 Unauthorized`	Missing, malformed, or revoked secret key
`403 Forbidden`	Key lacks an `organization:mcp` permission for the tool, or organization does not have MCP server enabled
`400 Bad Request`	A key reaching several merchants omitted `merchantId`
`404 Not Found`	No chargeback or merchant returned
`405 Method Not Allowed`	Requests other than `POST`