insimbi

Docs · MCP

MCP tools

insimbi as tools for any MCP client.

Designed. The MCP server and these tools are designed. The server address comes with your access.

Connect any MCP client to insimbi. Each agent is bound to an agent of record and acts inside a perimeter, so it can only do what you allowed.

Illustrative example

{
  "mcpServers": {
    "insimbi": { "url": "<insimbi MCP URL>", "auth": "oauth" }
  }
}
quote_ticketPrice a proposed payment before submission. Returns fee lines with rule citations and the perimeter decision.
explain_decisionExplain why a payment took its rail, was priced, declined or was denied, line by line, each cited to a rule.
get_ruleResolve a citation to its rule text, source and version.
open_mandateRequest a perimeter from an operator. Creates a pending request; a person approves it.

Agents can price and explain on their own. Widening what an agent may do always needs a person. It works like access changes in the API: the change is proposed (approval.proposed), a person approves it (approval.approved), and the approval is bound to that exact change.

MCP tools Designed. Tool calls over MCP, with a person approving any wider access.
MCP toolsSequence diagram with 4 lanes (Agent (MCP client), insimbi MCP server, insimbi API and record, Operator) and 10 numbered steps. The same steps are listed in text below the diagram.Agent(MCP client)insimbi MCP serverinsimbi APIand recordOperator1tools/list2quote_ticket,explain_decision,get_rule,open_mandate3tools/callquote_ticket4Price the paymentagainst your rules.Nothing is submitted.5Fee lines with rule citations and the perimeterdecision6tools/callopen_mandate7Propose the change(approval.proposed)8Ask a person toapprove9Approve(approval.approved),bound to that exactchange10Mandate granted

Steps in text

  1. Agent (MCP client) to insimbi MCP server: tools/list
  2. insimbi MCP server to Agent (MCP client): quote_ticket, explain_decision, get_rule, open_mandate
  3. Agent (MCP client) to insimbi MCP server: tools/call quote_ticket
  4. insimbi MCP server to insimbi API and record: Price the payment against your rules. Nothing is submitted.
  5. insimbi API and record to Agent (MCP client): Fee lines with rule citations and the perimeter decision
  6. Agent (MCP client) to insimbi MCP server: tools/call open_mandate
  7. insimbi MCP server to insimbi API and record: Propose the change (approval.proposed)
  8. insimbi API and record to Operator: Ask a person to approve
  9. Operator to insimbi API and record: Approve (approval.approved), bound to that exact change
  10. insimbi API and record to Agent (MCP client): Mandate granted

Other agent protocols: x402, AP2, ACP, MPP, UCP, Visa Intelligent Commerce, Visa Trusted Agent Protocol and Mastercard Agent Pay each have a page with their flow. See Flows (/docs/flows/#protocols).