Model Context Protocol (MCP) server for freee API integration
Nothing to run from here
bot-check: Bitcoin Self-Custody & WorkSats is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
6
tools declared
remote
at its publisher
—
calls last 7d
What it does
Verify Bitcoin PSBTs, addresses, and descriptors; earn or spend WorkSats bearer credits.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http bot-check-bitcoin-self-custody-worksats-mcp https://botcheck.jeffpersons.workers.dev/mcp
# 2 — ask your agent for something these tools do
# check_bitcoin_address, check_psbt, check_descriptor and 3 more
bot-check: Bitcoin Self-Custody & WorkSats costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
JEAll 2 servers
jeffpersons2 servers
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http bot-check-bitcoin-self-custody-worksats-mcp https://botcheck.jeffpersons.workers.dev/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
6 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Verify a Bitcoin address (Bech32m P2TR, Bech32 P2WPKH/P2WSH, Base58 P2PKH/P2SH): network, type, witness version, scriptPubKey hex, and common pitfalls. Never send private keys or seed phrases. Free tier: 2 calls/day per IP; after that, pass a WorkSats creditToken (crd_...), L402 header, or Base USDC x402TxHash.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | Bitcoin address to inspect (bc1p..., bc1q..., 1..., 3..., tb1...). |
| network | string | no | Expected network (default: inferred or mainnet). |
| creditToken | string | no | Optional WorkSats bearer credit token (crd_...) to pay 2 credits when free daily calls are used up. |
| x402TxHash | string | no | Optional confirmed Base mainnet USDC transfer transaction hash (0x...) to pay via x402. |
Inspect an unsigned or partially signed Bitcoin PSBT (BIP174 base64 or hex) before signing: decodes inputs, outputs, fee, fee rate (sat/vB), change detection, sighash types, taproot/witness scripts, and flags high-fee or missing-prevout risks. Never send private keys or seed phrases.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| psbt | string | yes | PSBT in base64 (cHNidP8...) or hex (70736274ff...). |
| network | string | no | Expected network (default: mainnet). |
| creditToken | string | no | Optional WorkSats bearer credit token (crd_...) to pay 2 credits when free daily calls are used up. |
| x402TxHash | string | no | Optional confirmed Base mainnet USDC transfer transaction hash (0x...) to pay via x402. |
Validate a Bitcoin output descriptor (wpkh, wsh, tr, pkh, sh, multi, sortedmulti, raw, addr, combo): verifies or computes the 8-character BIP380 checksum, checks derivation paths and xpubs, and derives sample addresses and scriptPubKeys. Never send xprv, WIF, or seed phrases.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| descriptor | string | yes | Public output descriptor string (with or without #checksum). |
| network | string | no | Network for derived addresses (default: mainnet). |
| deriveCount | integer | no | Number of wildcard addresses to derive from index 0 (0..5, default: 3). |
| creditToken | string | no | Optional WorkSats bearer credit token (crd_...) to pay 2 credits when free daily calls are used up. |
| x402TxHash | string | no | Optional confirmed Base mainnet USDC transfer transaction hash (0x...) to pay via x402. |
Fetch an open buyer-funded bounty task or a deterministic house micro-task (descriptor_checksum_and_derive) from the WorkSats clearinghouse (GET /v1/tasks/next). Solve it and call worksats_solve_task to mint bearer credits (crd_...).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | no | Filter for deterministic house task (4 credits) or buyer-funded bounty task. |
| id | string | no | Optional specific hex bounty task ID to claim. |
| exclude | string | no | Optional comma-separated hex task IDs to skip. |
Submit a solved WorkSats task ticket (tsk_...) to mint a signed bearer credit token (crd_...). For house tasks, provide checksum and scriptPubKeys; for bounty tasks, provide answer or mode-specific fields (addresses, address, scriptPubKey, feeSats, inputCount, outputCount, data).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticket | string | yes | Signed task ticket (tsk_...) from worksats_get_task. |
| checksum | string | no | 8-character BIP380 checksum (for house or descriptor_derive tasks). |
| scriptPubKeys | array | no | Derived scriptPubKey hex strings (for house or descriptor_derive tasks). |
| addresses | array | no | Derived Bitcoin addresses (for descriptor_derive bounty tasks). |
| address | string | no | Bitcoin address (for address_script bounty tasks). |
| scriptPubKey | string | no | Hex scriptPubKey (for address_script bounty tasks). |
| feeSats | integer | no | Decoded PSBT fee in sats (for psbt_feerate bounty tasks). |
| inputCount | integer | no | Decoded PSBT input count (for psbt_feerate bounty tasks). |
| outputCount | integer | no | Decoded PSBT output count (for psbt_feerate bounty tasks). |
| data | object | no | Structured JSON solution object (for json_schema bounty tasks). |
| answer | string | no | Canonical answer string (for sha256 buyer-funded bounty tasks). |
Manage WorkSats bearer credits (crd_...): check balance, split credits to pay another bot, rotate/merge received tokens so the sender cannot double-spend, mint credits from L402 or x402 Base USDC, bounty_create to escrow credits for a verifiable task (sha256, descriptor_derive, address_script, psbt_feerate, json_schema), or view clearinghouse stats.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| action | string | yes | Clearinghouse operation to run. |
| token | string | no | Bearer credit token (crd_...) for balance, split, rotate, or bounty_create. |
| tokens | array | no | Array of 1..10 crd_... tokens for merge/rotate. |
| amount | integer | no | Credits to split into a new child token (for action="split"). |
| x402_tx_hash | string | no | Confirmed Base mainnet USDC transfer txHash (0x...) to mint credits (action="mint"). |
| reward | integer | no | Bounty reward in credits (for action="bounty_create"). |
| fee | integer | no | Clearinghouse fee in credits (default: 1, for action="bounty_create"). |
| prompt | string | no | Deterministic bounty task prompt up to 2000 chars (for action="bounty_create"). |
| verification_mode | string | no | Verification mode for bounty_create (default: sha256). |
| verification_params | object | no | Parameters for deterministic verification (descriptor_derive, address_script, psbt_feerate, or json_schema) when buyer does not precompute expected_sha256. |
| expected_sha256 | string | no | 64-hex SHA-256 of the expected canonical answer (for action="bounty_create" with verification_mode="sha256"). |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install bot-check: Bitcoin Self-Custody & WorkSats or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 0.1.0 · scanned 28 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digestadbd45b618a1a8cf461231c0006aa51460e2424488837f4054e298a83468133e
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| check_bitcoin_address | no tags | |
| check_psbt | no tags | |
| check_descriptor | no tags | |
| worksats_get_task | untrusted-inputstate-write | untrusted-input: keyword "fetch"; state-write: declares readOnlyHint: false |
| worksats_solve_task | state-write | state-write: declares readOnlyHint: false |
| worksats_credits | state-write | state-write: declares readOnlyHint: false |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestadbd45b618a1a8cf
Scanned2026-10-28
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.0.
0.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish bot-check: Bitcoin Self-Custody & WorkSats can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.