bot-check: Bitcoin Self-Custody & WorkSats MCP
REMOTE · BOTCHECK.JEFFPERSONS.WORKERS.DEV
Verify Bitcoin PSBTs, addresses, and descriptors; earn or spend WorkSats bearer credits.
Available components
Last scanned (1 hour ago)
Scores higher than 45% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
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 Security63
- 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 check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- 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 Usability58
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1567 tokens (~261/item across 6 items; 6 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 Management30
- Stability observed for 9 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
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
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.
- 4 Nov 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.
- 1 Nov 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.
- 30 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.
- 28 Oct 26 0
- Tool “check_bitcoin_address” rewrote its description, which is the text the model reads security
- Tool “worksats_credits” rewrote its description, which is the text the model reads security
- Tool “worksats_solve_task” rewrote its description, which is the text the model reads security
- Schema quality: 190 → 261 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- “check_bitcoin_address” added an optional parameter “x402TxHash” cosmetic
- “check_descriptor” added an optional parameter “x402TxHash” cosmetic
- “check_psbt” added an optional parameter “x402TxHash” cosmetic
- “worksats_credits” added an optional parameter “verification_mode” cosmetic
- “worksats_credits” added an optional parameter “verification_params” cosmetic
- “worksats_credits” added an optional parameter “x402_tx_hash” cosmetic
- “worksats_solve_task” added an optional parameter “address” cosmetic
- “worksats_solve_task” added an optional parameter “addresses” cosmetic
- “worksats_solve_task” added an optional parameter “data” cosmetic
- “worksats_solve_task” added an optional parameter “feeSats” cosmetic
- “worksats_solve_task” added an optional parameter “inputCount” cosmetic
- “worksats_solve_task” added an optional parameter “outputCount” cosmetic
- “worksats_solve_task” added an optional parameter “scriptPubKey” cosmetic
- “check_descriptor” reworded the description of “deriveCount” cosmetic
- “worksats_credits” reworded the description of “expected_sha256” cosmetic
- “worksats_solve_task” reworded the description of “answer” cosmetic
- “worksats_solve_task” reworded the description of “checksum” cosmetic
- “worksats_solve_task” reworded the description of “scriptPubKeys” cosmetic
- 27 Oct 26 62
First indexed and scored.
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 5 Nov 2026 · Probed https://botcheck.jeffpersons.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=jeffpersons.workers.dev | CN=YE1,O=Let's Encrypt,C=US | 22 Oct 2026 | 20 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6b472b97f633de80fb5e6f3f95c9ae1299e |
| SANs: *.jeffpersons.workers.dev, jeffpersons.workers.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of botcheck.jeffpersons.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | 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 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://botcheck.jeffpersons.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://botcheck.jeffpersons.workers.dev/mcp | Served over HTTP | 200 |
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 →
check_bitcoin_address ~221
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Bitcoin address to inspect (bc1p..., bc1q..., 1..., 3..., tb1...). |
| creditToken | string | – | Optional WorkSats bearer credit token (`crd_...`) to pay 2 credits when free daily calls are used up. |
| network | string | – | Expected network (default: inferred or mainnet). |
| x402TxHash | string | – | Optional confirmed Base mainnet USDC transfer transaction hash (`0x...`) to pay via x402. |
No output schema declared.
No examples provided.
check_descriptor ~207
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.
| Name | Type | Req | Description |
|---|---|---|---|
| creditToken | string | – | Optional WorkSats bearer credit token (`crd_...`) to pay 2 credits when free daily calls are used up. |
| deriveCount | integer | – | Number of wildcard addresses to derive from index 0 (0..5, default: 3). |
| descriptor | string | yes | Public output descriptor string (with or without `#checksum`). |
| network | string | – | Network for derived addresses (default: mainnet). |
| x402TxHash | string | – | Optional confirmed Base mainnet USDC transfer transaction hash (`0x...`) to pay via x402. |
No output schema declared.
No examples provided.
check_psbt ~184
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.
| Name | Type | Req | Description |
|---|---|---|---|
| creditToken | string | – | Optional WorkSats bearer credit token (`crd_...`) to pay 2 credits when free daily calls are used up. |
| network | string | – | Expected network (default: mainnet). |
| psbt | string | yes | PSBT in base64 (`cHNidP8...`) or hex (`70736274ff...`). |
| x402TxHash | string | – | Optional confirmed Base mainnet USDC transfer transaction hash (`0x...`) to pay via x402. |
No output schema declared.
No examples provided.
worksats_credits ~417
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Clearinghouse operation to run. |
| amount | integer | – | Credits to split into a new child token (for `action="split"`). |
| expected_sha256 | string | – | 64-hex SHA-256 of the expected canonical answer (for `action="bounty_create"` with `verification_mode="sha256"`). |
| fee | integer | – | Clearinghouse fee in credits (default: 1, for `action="bounty_create"`). |
| prompt | string | – | Deterministic bounty task prompt up to 2000 chars (for `action="bounty_create"`). |
| reward | integer | – | Bounty reward in credits (for `action="bounty_create"`). |
| token | string | – | Bearer credit token (`crd_...`) for `balance`, `split`, `rotate`, or `bounty_create`. |
| tokens | array | – | Array of 1..10 `crd_...` tokens for `merge`/`rotate`. |
| verification_mode | string | – | Verification mode for `bounty_create` (default: `sha256`). |
| verification_params | object | – | Parameters for deterministic verification (`descriptor_derive`, `address_script`, `psbt_feerate`, or `json_schema`) when buyer does not precompute `expected_sha256`. |
| x402_tx_hash | string | – | Confirmed Base mainnet USDC transfer txHash (`0x...`) to mint credits (`action="mint"`). |
No output schema declared.
No examples provided.
worksats_get_task ~124
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_...`).
| Name | Type | Req | Description |
|---|---|---|---|
| exclude | string | – | Optional comma-separated hex task IDs to skip. |
| id | string | – | Optional specific hex bounty task ID to claim. |
| type | string | – | Filter for deterministic `house` task (4 credits) or buyer-funded `bounty` task. |
No output schema declared.
No examples provided.
worksats_solve_task ~335
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`).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Bitcoin address (for `address_script` bounty tasks). |
| addresses | array | – | Derived Bitcoin addresses (for `descriptor_derive` bounty tasks). |
| answer | string | – | Canonical answer string (for `sha256` buyer-funded bounty tasks). |
| checksum | string | – | 8-character BIP380 checksum (for house or `descriptor_derive` tasks). |
| data | object | – | Structured JSON solution object (for `json_schema` bounty tasks). |
| feeSats | integer | – | Decoded PSBT fee in sats (for `psbt_feerate` bounty tasks). |
| inputCount | integer | – | Decoded PSBT input count (for `psbt_feerate` bounty tasks). |
| outputCount | integer | – | Decoded PSBT output count (for `psbt_feerate` bounty tasks). |
| scriptPubKey | string | – | Hex scriptPubKey (for `address_script` bounty tasks). |
| scriptPubKeys | array | – | Derived scriptPubKey hex strings (for house or `descriptor_derive` tasks). |
| ticket | string | yes | Signed task ticket (`tsk_...`) from `worksats_get_task`. |
No output schema declared.
No examples provided.
How do I install the bot-check: Bitcoin Self-Custody & WorkSats MCP server?
bot-check: Bitcoin Self-Custody & WorkSats MCP is a hosted endpoint at https://botcheck.jeffpersons.workers.dev/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 · botcheck.jeffpersons.workers.dev
claude mcp add --transport http dev-workers-jeffpersons-botcheck-botcheck 'https://botcheck.jeffpersons.workers.dev/mcp'
What is the bot-check: Bitcoin Self-Custody & WorkSats MCP server?
bot-check: Bitcoin Self-Custody & WorkSats MCP is listed in the public MCP registry as dev.workers.jeffpersons.botcheck/botcheck. Verify Bitcoin PSBTs, addresses, and descriptors; earn or spend WorkSats bearer credits. This page covers its hosted endpoint (https://botcheck.jeffpersons.workers.dev/mcp).
Is the bot-check: Bitcoin Self-Custody & WorkSats MCP server safe to use?
bot-check: Bitcoin Self-Custody & WorkSats MCP scores 65 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 bot-check: Bitcoin Self-Custody & WorkSats MCP server expose?
bot-check: Bitcoin Self-Custody & WorkSats MCP exposes 6 tools: check_bitcoin_address, check_psbt, check_descriptor, worksats_get_task, worksats_solve_task, worksats_credits. Their descriptions and schemas cost roughly 1,488 tokens of context every time the server is loaded.
Does the bot-check: Bitcoin Self-Custody & WorkSats MCP server require authentication?
No. We connected to bot-check: Bitcoin Self-Custody & WorkSats MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the bot-check: Bitcoin Self-Custody & WorkSats MCP server still maintained?
bot-check: Bitcoin Self-Custody & WorkSats MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.