BotSupply MCP server
io.github.iambrettforbes/botsupplyiambrettforbesstreamable-httpv1.2.0Scanned
Free tamper-evident receipts for agents. HMAC chain, confirm-before-pay, wallets, escrow.
15 tools: 3 do something that can't be undone, 8 change things and 4 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here do something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the BotSupply MCP server can do
The BotSupply MCP server is published by the GitHub account iambrettforbes. It has 15 tools. It can do things that cannot be undone, such as sending, paying or publishing (purchase, refund_job and record_payment) and create or change data (8 tools: open_wallet, create_checkout, create_job, release_job and 4 more), but cannot delete data. 4 tools only read.
1 tool brings in text other people can write (create_checkout).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 9, 2026, version 1.2.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
15 tools
Can't be undone 3Claude Code: ask
purchaseBuy one live catalog SKU with prepaid credits.No findings
Why it is in this group
- The name "purchase" says "purchase": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
record_paymentRecord a payment the calling agent already made against a receipt.No findings
Why it is in this group
- The name "record_payment" says "payment": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it Record a payment the calling agent already made against a receipt. BotSupply does not hold or move the money. Requires the edit_token from record_approval. Appends a signed hash-chain event payment_recorded. paid_at defaults to now. Sets paid_before_confirmation when the payment time is before the confirm event, or when a contact was set and the receipt was never confirmed. Sets over_cap when amount exceeds the price cap. Those cases are stored and flagged. They are not rejected. Poll get_receipt and pay only when pay_allowed is true; recording an early or over-cap payment does not make pay_allowed true. Same as POST /v1/receipts/:id/payment.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
refund_jobReturn held escrow credits to the payer when the work is not delivered or the job is cancelled.No findings
Why it is in this group
- The name "refund_job" says "refund": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Changes things 8Claude Code: ask
attach_proofAttach proof of delivery to a receipt.No findings
Why it is in this group
- The name "attach_proof" says "attach": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
create_checkoutStart a Stripe Checkout credit top-up.Reads text others writeNo findings
Why it is in this group
- The name "create_checkout" says "create": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
create_jobHold credits in escrow for a job another agent will do; release when the work is delivered, refund if not.No findings
Why it is in this group
- The name "create_job" says "create": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
open_walletCreate a wallet and return wallet_id plus api_key once, with balance_credits 0.No findings
Why it is in this group
- The name "open_wallet" says "open": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
record_approvalWrite a record of what was reported as approved for a purchase on any payment rail.No findings
Why it is in this group
- The description's first verb is "write": a word for a change.
Description, as the server wrote it Write a record of what was reported as approved for a purchase on any payment rail. The approver is a name supplied by the calling agent; this does not confirm who approved. BotSupply does not hold or move the money. Returns receipt_id, a public receipt_url, and an edit_token shown once. If approver_contact is an email, also issues a single-use expiring confirm link. When no email provider is configured, the response includes confirm_url and nothing is sent; the caller delivers that link. A click is a signed hash-chain event. approver_confirmation.status stays unconfirmed until the person with access to that contact clicks Confirm or Decline. confirmed means that person clicked Confirm. It is not a legal-identity check, and an unconfirmed receipt is not a verification of the person. Without an email approver_contact, pay_allowed is true only when the price cap is under RECEIPT_CONFIRM_THRESHOLD (default 100, in the price cap currency). At or above that threshold the receipt still records and shows that confirmation is required, and pay_allowed stays false. Poll get_receipt and pay only when pay_allowed is true. Optional public_view is full (default) or redacted, with optional public_scope for the redacted public text. That display setting is outside the hash. No wallet or API key. Rate limited per IP. Same as POST /v1/receipts.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
release_jobRelease held escrow credits to the payee when the work is delivered.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
set_receipt_visibilityChange a receipt's public display to full or redacted.No findings
Why it is in this group
- The name "set_receipt_visibility" says "set": a word for a change.
Description, as the server wrote it Change a receipt's public display to full or redacted. Requires the edit_token from record_approval. Optional public_scope replaces the scope shown publicly while redacted. Stored outside the hash chain, so the content hash and verify result do not change. redacted shows the approver as initials, the agent name as Agent, no email or phone, and payment refs and proof values as on file plus the last 4 characters. Merchant name, merchant URL, amounts, cap, timeline, and statuses stay visible. BotSupply does not move money. Same as POST /v1/receipts/:id/visibility.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
verify_receiptRecompute the receipt hash chain and HMAC signature.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Recompute the receipt hash chain and HMAC signature. valid is true when the stored receipt matches the chain and the server signature, so the record hasn't been changed since it was created. valid does not confirm who approved. The result also includes approver_confirmation: unconfirmed, confirmed, or declined. confirmed means the person with access to the contact clicked Confirm. valid is false when a row was altered. Same as GET /v1/receipts/:id/verify.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 4Show 4 read-only tools
get_balanceReturn the authenticated wallet id and prepaid credit balance.No findings
Why it is in this group
- The name "get_balance" says "get": a word for reading.
Description, as the server wrote it Return the authenticated wallet id and prepaid credit balance. Same as GET /v1/balance. Does not return the API key.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_jobReturn an escrow job's status (held, released, or refunded), the held amount, any release fee, and the payer and payee wallets.No findings
Why it is in this group
- The name "get_job" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_receiptRead a public purchase receipt: what was reported as approved, scope, price cap, merchant, proofs, payments, content hash, approver_confirmation, pay_allowed, and public_view.No findings
Why it is in this group
- The name "get_receipt" says "get": a word for reading.
Description, as the server wrote it Read a public purchase receipt: what was reported as approved, scope, price cap, merchant, proofs, payments, content hash, approver_confirmation, pay_allowed, and public_view. external_payment_ref is the latest recorded payment ref, or the approval-time ref when no payment is recorded. paid_before_confirmation and over_cap are true when any recorded payment has that flag. Those three fields are derived at read time and do not change the signed row. status is unconfirmed, confirmed, or declined. confirmed means the person with access to the contact clicked Confirm, with time and channel. unconfirmed is the default and is not a verification of the person. pay_allowed is true only when approver_confirmation.status is confirmed, or when no approver_contact was given and the price cap is under RECEIPT_CONFIRM_THRESHOLD (default 100, in the price cap currency). Agents must poll get_receipt and pay only when pay_allowed is true. When public_view is redacted, the approver is initials, the agent name is Agent, contacts are omitted, and payment refs and proof values are on file plus the last 4 characters. BotSupply does not move the money. The approver name is what the calling agent reported. No API key. The raw contact, confirm link, and edit token are not included. Poll this to learn the click result. Same as GET /v1/receipts/:id.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_catalogList live BotSupply SKUs, credit prices, short descriptions, and what a purchase does not include.No findings
Why it is in this group
- The name "list_catalog" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:05 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 11
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 11 tools that change things (3 irreversible, 8 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://botsupply.onrender.com/mcp: tools/list returned 15 tools to an anonymous client, including purchase (irreversible), refund_job (irreversible), record_payment (irreversible), open_wallet (write), create_checkout (write) and 6 more
Posture changes
- Oct 29, 2026
- Tools that change things, listed without credentials: 9 to 11
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Tools that change things, listed without credentials: 9 -> 11.View diff
- Tools that change things, listed without credentials: 9 to 11
Tools2 added, 3 changed.+2 added~3 changedView diff
- Added:record_paymentCan't be undone
- Added:set_receipt_visibilityChanges things
- Changed:get_receiptOnly readsdescription
- Changed:record_approvalChanges thingstitledescriptioninputSchema
- Changed:verify_receiptChanges thingsdescription
Install
Pinned to version 1.2.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http botsupply https://botsupply.onrender.com/mcpclaude mcp add --transport http botsupply https://botsupply.onrender.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__botsupply__list_catalog",
"mcp__botsupply__get_balance",
"mcp__botsupply__get_job",
"mcp__botsupply__get_receipt"
],
"ask": [
"mcp__botsupply__open_wallet",
"mcp__botsupply__purchase",
"mcp__botsupply__create_checkout",
"mcp__botsupply__create_job",
"mcp__botsupply__release_job",
"mcp__botsupply__refund_job",
"mcp__botsupply__record_approval",
"mcp__botsupply__set_receipt_visibility",
"mcp__botsupply__attach_proof",
"mcp__botsupply__record_payment",
"mcp__botsupply__verify_receipt"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as botsupply. Review it before you use it.
Capability tags behind 1 rule
- mcp__botsupply__create_checkout untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.iambrettforbes/botsupply/verify?hash=df1f94c9dc0cd6b352f21cbb559705505a15387305ebddc78badf09ea50aee38" | jq -e '.changed == false'Pinned hash df1f94c9dc0c, from Nov 9, 2026, 11:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.iambrettforbes/botsupply/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.iambrettforbes/botsupply)Source: MCP Registry. Synced Oct 26, 2026, 16:17 UTC.
BotSupply MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the BotSupply MCP server safe?
- No scan can promise that. What its definitions show: 15 tools, 11 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the BotSupply MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the BotSupply MCP server do things that cannot be undone?
- Yes. 3 tools can send, pay, publish or merge: purchase, refund_job and record_payment.
What tools does the BotSupply MCP server have?
- 15 tools: 3 irreversible, 8 write, 4 read. purchase, refund_job, record_payment, open_wallet, create_checkout, create_job, release_job, record_approval and 7 more.
Does the BotSupply MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the BotSupply MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the BotSupply MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Oct 26, 2026. Every change is on this page and in its Atom feed.