BotSupply
REMOTE · BOTSUPPLY.ONRENDER.COM
Verifiable purchase receipts for agents: record approval and proof. Wallets and escrow (test mode).
Available components
Last scanned (3 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 25 Oct 2026.
Category Finance and Payments
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Oct 26 +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.
- 22 Oct 26 +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.
- 20 Oct 26 +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.
- 19 Oct 26 −2
- 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 security
- Schema quality: 125 → 160 ▼ functional
- 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” functional
- “create_checkout” reworded the description of “credits” cosmetic
- 18 Oct 26 +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.
- 16 Oct 26 +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.
- 13 Oct 26 +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.
- 11 Oct 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Oct 2026 · Probed https://botsupply.onrender.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=onrender.com | CN=WE1,O=Google Trust Services,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 6eb1e3fe7d0631ea1337bfa4a321c137 |
| SANs: onrender.com, *.onrender.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of botsupply.onrender.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| onrender.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://botsupply.onrender.com/mcp | Verified | 200 | |
| http (plaintext) | http://botsupply.onrender.com/mcp | HTTPS enforced | 301 | https://botsupply.onrender.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
attach_proof Attach delivery proof ~192
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.
| Name | Type | Req | Description |
|---|---|---|---|
| actual_amount | – | – | Amount actually charged. over_cap is true when this is above the price cap. |
| edit_token | string | yes | Secret returned once by record_approval. Required to attach proof. |
| receipt_id | string | yes | Receipt id from record_approval (rcpt_…). |
| status | string | – | Omit to mark an approved receipt delivered. Pass disputed to dispute it. |
| type | string | yes | Proof kind. Examples: order_confirmation, tracking, url, hash. |
| value | string | yes | The proof itself: confirmation id, tracking number, URL, or hash. |
No output schema declared.
No examples provided.
create_checkout Create checkout ~185
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
create_job Create escrow job ~248
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_credits | integer | yes | 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 | yes | What the payee is being paid to do. |
| idempotency_key | string | yes | 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 | yes | Wallet that receives the credits when the payer releases the job. |
No output schema declared.
No examples provided.
get_balance Get balance ~73
Return the authenticated wallet id and prepaid credit balance. Same as GET /v1/balance. Does not return the API key.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Wallet API key (bsk_…). Optional when the MCP client sends Authorization: Bearer. The local stdio process also reads BOTSUPPLY_API_KEY. |
No output schema declared.
No examples provided.
get_job Get escrow job ~128
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Escrow job id returned by create_job (job_…). |
No output schema declared.
No examples provided.
get_receipt Get purchase receipt ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| receipt_id | string | yes | Public receipt id (rcpt_…). |
No output schema declared.
No examples provided.
list_catalog List catalog ~53
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
open_wallet Open wallet ~92
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.
| Name | Type | Req | Description |
|---|---|---|---|
| label | string | – | Optional label, 1 to 80 characters. Same field as POST /v1/wallets. |
No output schema declared.
No examples provided.
purchase Purchase ~133
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Live catalog SKU. The field name is sku, not sku_id. |
No output schema declared.
No examples provided.
record_approval Record purchase approval ~294
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | Merchant or seller name. |
| merchant_url | string | – | Optional http or https URL for the merchant. |
| payment_rail | string | yes | How the agent will pay. Examples: stripe_link, card, x402, botsupply_wallet. |
| price_cap_amount | – | yes | Maximum amount approved. A positive decimal, for example 25 or "19.95". |
| price_cap_currency | string | yes | Currency code, 3 to 10 letters, for example USD or USDC. |
| scope | string | yes | What the human approved, in plain text. |
No output schema declared.
No examples provided.
refund_job Refund escrow job ~149
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Escrow job id returned by create_job (job_…). |
No output schema declared.
No examples provided.
release_job Release escrow job ~163
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Escrow job id returned by create_job (job_…). |
No output schema declared.
No examples provided.
verify_receipt Verify purchase receipt ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| receipt_id | string | yes | Public receipt id (rcpt_…). |
No output schema declared.
No examples provided.
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.
remote · botsupply.onrender.com
claude mcp add --transport http iambrettforbes-botsupply 'https://botsupply.onrender.com/mcp'
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.