io.github.iambrettforbes/botsupply

What it mainly works on, as our AI model read its tool descriptions: money, payments or trading.

8 of 13 tools are described as changing something (creating, editing, deleting, sending or running).

• list_catalogon 12 other serversreads or searches

  “List live BotSupply SKUs, credit prices, short descriptions, and what a purchase does not include.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  Takes no inputs.

• open_walletcreates or changes datadescribed as changing data

  “Create a wallet and return wallet_id plus api_key once, with balance_credits 0.”

  Publisher declares: read-only no · destructive no · idempotent no · open-world no

  1 input

  • labelstring“Optional label, 1 to 80 characters.”
• get_balanceon 101 other serversreads or searches

  “Return the authenticated wallet id and prepaid credit balance.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  1 input

  • api_keystring“Wallet API key (bsk_…).”
• purchaseon 4 other serversmoves moneydescribed as changing data

  “Buy one live catalog SKU with prepaid credits.”

  Publisher declares: read-only no · destructive no · idempotent no · open-world no

  2 inputs, 1 required

  • skustringrequired“Live catalog SKU.”
  • api_keystring“Wallet API key (bsk_…).”
• create_checkouton 94 other serversmoves moneydescribed as changing data

  “Start a Stripe Checkout credit top-up.”

  Publisher declares: read-only no · destructive no · idempotent no · open-world yes

  3 inputs, 1 required

  • creditsintegerrequired“Credits to buy.”
  • wallet_idstring“Wallet to credit.”
  • api_keystring“Wallet API key (bsk_…).”
• create_jobon 8 other serversmoves moneydescribed as changing data

  “Hold credits in escrow for a job another agent will do; release when the work is delivered, refund if not.”

  Publisher declares: read-only no · destructive no · idempotent yes · open-world no

  5 inputs, 4 required

  • payee_wallet_idstringrequired“Wallet that receives the credits when the payer releases the job.”
  • amount_creditsintegerrequired“Credits to debit from the authenticated payer wallet and hold until release or refund.”
  • descriptionstringrequired“What the payee is being paid to do.”
  • idempotency_keystringrequired“Caller-chosen key scoped to the payer.”
  • api_keystring“Wallet API key (bsk_…).”
• get_jobon 138 other serversreads or searches

  “Return an escrow job's status (held, released, or refunded), the held amount, any release fee, and the payer and payee wallets.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  2 inputs, 1 required

  • job_idstringrequired“Escrow job id returned by create_job (job_…).”
  • api_keystring“Wallet API key (bsk_…).”
• release_jobmoves moneydescribed as changing data

  “Release held escrow credits to the payee when the work is delivered.”

  Publisher declares: read-only no · destructive no · idempotent no · open-world no

  2 inputs, 1 required

  • job_idstringrequired“Escrow job id returned by create_job (job_…).”
  • api_keystring“Wallet API key (bsk_…).”
• refund_jobmoves moneydescribed as changing data

  “Return held escrow credits to the payer when the work is not delivered or the job is cancelled.”

  Publisher declares: read-only no · destructive no · idempotent no · open-world no

  2 inputs, 1 required

  • job_idstringrequired“Escrow job id returned by create_job (job_…).”
  • api_keystring“Wallet API key (bsk_…).”
• record_approvalcreates or changes datadescribed as changing data

  “Record a human's approval of a purchase on any payment rail.”

  Publisher declares: read-only no · destructive no · idempotent no · open-world no

  11 inputs, 6 required

  • approverstringrequired“Display name or handle of the human who approved the purchase.”
  • approver_contactstring“Optional email or phone.”
  • agent_idstring“Optional id of the agent that will pay.”
  • agent_namestring“Optional display name of the paying agent.”
  • merchant_namestringrequired“Merchant or seller name.”
  • merchant_urlstring“Optional http or https URL for the merchant.”
  • scopestringrequired“What the human approved, in plain text.”
  • price_cap_amountnumber or stringrequired“Maximum amount approved.”
  • price_cap_currencystringrequired“Currency code, 3 to 10 letters, for example USD or USDC.”
  • payment_railstringrequired“How the agent will pay.”
  • external_payment_refstring“Optional id from the payment rail.”
• attach_proofcreates or changes datadescribed as changing data

  “Attach proof of delivery to a receipt.”

  Publisher declares: read-only no · destructive no · idempotent no · open-world no

  6 inputs, 4 required

  • receipt_idstringrequired“Receipt id from record_approval (rcpt_…).”
  • edit_tokenstringrequired“Secret returned once by record_approval.”
  • typestringrequired“Proof kind.”
  • valuestringrequired“The proof itself: confirmation id, tracking number, URL, or hash.”
  • actual_amountnumber or string“Amount actually charged.”
  • statusstring“Omit to mark an approved receipt delivered.”
• get_receipton 59 other serversreads or searches

  “Read a public purchase receipt: approval, scope, price cap, merchant, proofs, and content hash.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  1 input, 1 required

  • receipt_idstringrequired“Public receipt id (rcpt_…).”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.