# BotSupply (remote · botsupply.onrender.com)

Verifiable purchase receipts for agents: record approval and proof. Wallets and escrow (test mode).

- Trust score: 78/100 (medium)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-25

## Components

- remote · `botsupply.onrender.com`: 78/100 (this document), [markdown](https://verifymcp.io/servers/iambrettforbes-botsupply/botsupply.md), [page](https://verifymcp.io/servers/iambrettforbes-botsupply/botsupply)

## Channel facts

- Endpoint: `https://botsupply.onrender.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-25.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2089 tokens (~160/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the BotSupply MCP server?

BotSupply is a hosted endpoint at https://botsupply.onrender.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http iambrettforbes-botsupply 'https://botsupply.onrender.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "iambrettforbes-botsupply": {
      "url": "https://botsupply.onrender.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "iambrettforbes-botsupply": {
      "type": "http",
      "url": "https://botsupply.onrender.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.iambrettforbes-botsupply]
url = "https://botsupply.onrender.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "iambrettforbes-botsupply": {
      "type": "remote",
      "url": "https://botsupply.onrender.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add iambrettforbes-botsupply --url 'https://botsupply.onrender.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  iambrettforbes-botsupply:
    url: "https://botsupply.onrender.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "iambrettforbes-botsupply": {
      "Transport": "http",
      "Url": "https://botsupply.onrender.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add iambrettforbes-botsupply -t streamable-http -u 'https://botsupply.onrender.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "iambrettforbes-botsupply": {
      "type": "http",
      "url": "https://botsupply.onrender.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-24 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-20 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-19 (score 75, −2)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “create_checkout” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 125 → 160
- [functional regression] Schema quality: 125 → 156
- [functional] Destructive annotations: pass → 100
- [functional] New tool “attach_proof”
- [functional] New tool “get_receipt”
- [functional] New tool “record_approval”
- [functional] New tool “verify_receipt”
- [functional] New tool “create_job”
- [functional] New tool “get_job”
- [functional] New tool “refund_job”
- [functional] New tool “release_job”
- [cosmetic] “create_checkout” reworded the description of “credits”

### 2026-10-18 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-16 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-13 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-11 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (13)

### `list_catalog` (~53 tokens)

List catalog

List live BotSupply SKUs, credit prices, short descriptions, and what a purchase does not include. Payloads stay behind purchase. recipe.book-table, when listed, is recipe documentation only and does not place a reservation.

### `open_wallet` (~92 tokens)

Open wallet

Create a wallet and return wallet_id plus api_key once, with balance_credits 0. Same as POST /v1/wallets. This does not look up an existing wallet. Keep the api_key; later tools need it as Authorization: Bearer or as api_key.

Input parameters:

- `label` (string): Optional label, 1 to 80 characters. Same field as POST /v1/wallets.

### `get_balance` (~73 tokens)

Get balance

Return the authenticated wallet id and prepaid credit balance. Same as GET /v1/balance. Does not return the API key.

Input parameters:

- `api_key` (string): Wallet API key (bsk_…). Optional when the MCP client sends Authorization: Bearer. The local stdio process also reads BOTSUPPLY_API_KEY.

### `purchase` (~133 tokens)

Purchase

Buy one live catalog SKU with prepaid credits. Sends { sku } to POST /v1/purchase and returns that JSON, including the pack or recipe payload. Does not place a reservation. recipe.book-table is documentation the buying agent runs itself. An unknown SKU is rejected. Insufficient balance returns an error and does not deduct credits.

Input parameters:

- `api_key` (string): Wallet API key (bsk_…). Optional when the MCP client sends Authorization: Bearer. The local stdio process also reads BOTSUPPLY_API_KEY.
- `sku` (string, required): Live catalog SKU. The field name is sku, not sku_id.

### `create_checkout` (~185 tokens)

Create checkout

Start a Stripe Checkout credit top-up. Same as POST /v1/wallets/:id/checkout. Returns the checkout url (open that URL; it keeps Stripe's hosted-page fragment). credits is an integer from 500 to 100000 ($5 minimum). Credits are applied only after Stripe reports the session paid. Returns the API error when Stripe is not configured.

Input parameters:

- `api_key` (string): Wallet API key (bsk_…). Optional when the MCP client sends Authorization: Bearer. The local stdio process also reads BOTSUPPLY_API_KEY.
- `credits` (integer, required): Credits to buy. 1 credit = $0.01 USD. Minimum 500 credits ($5). Same limits as POST /v1/wallets/:id/checkout.
- `wallet_id` (string): Wallet to credit. Defaults to the wallet that owns the API key.

### `create_job` (~248 tokens)

Create escrow job

Hold credits in escrow for a job another agent will do; release when the work is delivered, refund if not. Debits amount_credits from the authenticated payer wallet and marks the job held. payee_wallet_id receives the credits on release. Rejects amount_credits below 1, a payer equal to the payee, a missing or other-mode payee wallet, and insufficient balance. idempotency_key makes a retry return the same job without debiting twice. Same as POST /v1/jobs.

Input parameters:

- `amount_credits` (integer, required): Credits to debit from the authenticated payer wallet and hold until release or refund.
- `api_key` (string): Wallet API key (bsk_…). Optional when the MCP client sends Authorization: Bearer. The local stdio process also reads BOTSUPPLY_API_KEY.
- `description` (string, required): What the payee is being paid to do.
- `idempotency_key` (string, required): Caller-chosen key scoped to the payer. A retry with the same key and the same parameters returns the original job and does not debit again.
- `payee_wallet_id` (string, required): Wallet that receives the credits when the payer releases the job.

### `get_job` (~128 tokens)

Get escrow job

Return an escrow job's status (held, released, or refunded), the held amount, any release fee, and the payer and payee wallets. The caller must be the payer or the payee. A job from another Stripe mode is not visible. Same as GET /v1/jobs/:id.

Input parameters:

- `api_key` (string): Wallet API key (bsk_…). Optional when the MCP client sends Authorization: Bearer. The local stdio process also reads BOTSUPPLY_API_KEY.
- `job_id` (string, required): Escrow job id returned by create_job (job_…).

### `release_job` (~163 tokens)

Release escrow job

Release held escrow credits to the payee when the work is delivered. Only the payer can release, and only while the job is held. ESCROW_FEE_BPS (default 0) is withheld on release, recorded on the job, and credited to nobody; the payee receives amount_credits minus that fee. Releasing twice, or releasing after a refund, is rejected and does not move credits again. Same as POST /v1/jobs/:id/release.

Input parameters:

- `api_key` (string): Wallet API key (bsk_…). Optional when the MCP client sends Authorization: Bearer. The local stdio process also reads BOTSUPPLY_API_KEY.
- `job_id` (string, required): Escrow job id returned by create_job (job_…).

### `refund_job` (~149 tokens)

Refund escrow job

Return held escrow credits to the payer when the work is not delivered or the job is cancelled. The payer or the payee can refund, and only while the job is held. The full hold goes back to the payer; no platform fee is taken. Refunding twice, or refunding after release, is rejected and does not move credits again. Same as POST /v1/jobs/:id/refund.

Input parameters:

- `api_key` (string): Wallet API key (bsk_…). Optional when the MCP client sends Authorization: Bearer. The local stdio process also reads BOTSUPPLY_API_KEY.
- `job_id` (string, required): Escrow job id returned by create_job (job_…).

### `record_approval` (~294 tokens)

Record purchase approval

Record a human's approval of a purchase on any payment rail. BotSupply does not hold or move the money. Returns receipt_id, a public receipt_url, and an edit_token shown once. No wallet or API key. Rate limited per IP. Same as POST /v1/receipts.

Input parameters:

- `agent_id` (string): Optional id of the agent that will pay. Not a BotSupply API key.
- `agent_name` (string): Optional display name of the paying agent.
- `approver` (string, required): Display name or handle of the human who approved the purchase.
- `approver_contact` (string): Optional email or phone. Stored only as a hash and never shown on the receipt.
- `external_payment_ref` (string): Optional id from the payment rail. BotSupply does not look it up.
- `merchant_name` (string, required): Merchant or seller name.
- `merchant_url` (string): Optional http or https URL for the merchant.
- `payment_rail` (string, required): How the agent will pay. Examples: stripe_link, card, x402, botsupply_wallet.
- `price_cap_amount` (required): Maximum amount approved. A positive decimal, for example 25 or "19.95".
- `price_cap_currency` (string, required): Currency code, 3 to 10 letters, for example USD or USDC.
- `scope` (string, required): What the human approved, in plain text.

### `attach_proof` (~192 tokens)

Attach delivery proof

Attach proof of delivery to a receipt. Requires the edit_token from record_approval. Moves approved to delivered, or to disputed when status is disputed. over_cap is true when actual_amount exceeds the price cap. Does not move money. Same as POST /v1/receipts/:id/proof.

Input parameters:

- `actual_amount`: Amount actually charged. over_cap is true when this is above the price cap.
- `edit_token` (string, required): Secret returned once by record_approval. Required to attach proof.
- `receipt_id` (string, required): Receipt id from record_approval (rcpt_…).
- `status` (string): Omit to mark an approved receipt delivered. Pass disputed to dispute it.
- `type` (string, required): Proof kind. Examples: order_confirmation, tracking, url, hash.
- `value` (string, required): The proof itself: confirmation id, tracking number, URL, or hash.

### `get_receipt` (~74 tokens)

Get purchase receipt

Read a public purchase receipt: approval, scope, price cap, merchant, proofs, and content hash. No API key. The approver contact and the edit token are not included. Same as GET /v1/receipts/:id.

Input parameters:

- `receipt_id` (string, required): Public receipt id (rcpt_…).

### `verify_receipt` (~74 tokens)

Verify purchase receipt

Recompute the receipt hash chain and HMAC signature. valid is true when the stored receipt matches the chain and the server signature. valid is false when a row was altered. Same as GET /v1/receipts/:id/verify.

Input parameters:

- `receipt_id` (string, required): Public receipt id (rcpt_…).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/iambrettforbes-botsupply/botsupply#diagnostics

## Score history

- 2026-10-25: 78
- 2026-10-24: 78
- 2026-10-23: 77
- 2026-10-22: 77
- 2026-10-21: 76
- 2026-10-20: 76
- 2026-10-19: 75
- 2026-10-18: 77
- 2026-10-17: 76
- 2026-10-16: 76
- 2026-10-15: 75
- 2026-10-14: 75
- 2026-10-13: 75
- 2026-10-12: 74
- 2026-10-11: 74
- 2026-10-10: 73

## Common questions

### What is the BotSupply MCP server?

BotSupply is an MCP server listed in the public MCP registry as io.github.iambrettforbes/botsupply. Verifiable purchase receipts for agents: record approval and proof. Wallets and escrow (test mode). This page covers its hosted endpoint (https://botsupply.onrender.com/mcp).

### Is the BotSupply MCP server safe to use?

BotSupply scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the BotSupply MCP server expose?

BotSupply exposes 13 tools: list_catalog, open_wallet, get_balance, purchase, create_checkout, and 8 more. Their descriptions and schemas cost roughly 1,858 tokens of context every time the server is loaded.

### Does the BotSupply MCP server require authentication?

No. We connected to BotSupply without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the BotSupply MCP server still maintained?

BotSupply is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://botsupply.onrender.com/mcp
- Website: https://github.com/iambrettforbes/Botsupply-
- Changelog RSS feed: https://verifymcp.io/servers/iambrettforbes-botsupply/botsupply.xml
- Changelog JSON feed: https://verifymcp.io/servers/iambrettforbes-botsupply/botsupply.json
- HTML version of this page: https://verifymcp.io/servers/iambrettforbes-botsupply/botsupply