Skip to content

bot-check: Bitcoin Self-Custody & WorkSats MCP server

dev.workers.jeffpersons.botcheck/botcheckbotcheck.jeffpersons.workers.devstreamable-httpv0.1.0Scanned

Verify Bitcoin PSBTs, addresses, and descriptors; earn or spend WorkSats bearer credits.

6 tools: 4 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 4 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

4 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

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 bot-check: Bitcoin Self-Custody & WorkSats MCP server can do

The bot-check: Bitcoin Self-Custody & WorkSats MCP server is published by botcheck.jeffpersons.workers.dev, a domain the MCP Registry verified. It has 6 tools. It can create or change data (4 tools: check_bitcoin_address, worksats_get_task, worksats_solve_task and worksats_credits), but cannot delete data. 2 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

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 0.1.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.

6 tools

Changes things 4Claude Code: ask
  • check_bitcoin_addressVerify a Bitcoin address (Bech32m P2TR, Bech32 P2WPKH/P2WSH, Base58 P2PKH/P2SH): network, type, witness version, scriptPubKey hex, and common pitfalls.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
    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`.

    Annotations the server declares

    • title: Check Bitcoin Address
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • worksats_creditsManage WorkSats bearer credits (`crd_...`): check `balance`, `split` credits to pay another bot, `rotate`/`merge` received tokens so the sender cannot double-spend, `mint` credits …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
    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`.

    Annotations the server declares

    • title: Manage WorkSats Bearer Credits
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • worksats_get_taskFetch an open buyer-funded bounty task or a deterministic house micro-task (`descriptor_checksum_and_derive`) from the WorkSats clearinghouse (`GET /v1/tasks/next`).1 finding

    Why it is in this group

    • The name "worksats_get_task" says "get": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    Findings

    • Warn

      The server marks "worksats_get_task" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "worksats_get_task" says "get": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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_...`).

    Annotations the server declares

    • title: Get WorkSats Micro-Task
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • worksats_solve_taskSubmit a solved WorkSats task ticket (`tsk_...`) to mint a signed bearer credit token (`crd_...`).No findings

    Why it is in this group

    • The description's first verb is "submit": a word for a change.
    Description, as the server wrote it
    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`).

    Annotations the server declares

    • title: Submit WorkSats Task Solution
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Only reads 2Show 2 read-only tools
  • check_descriptorValidate 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 a…No findings

    Why it is in this group

    • The description's first verb is "validate": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check Bitcoin Output Descriptor
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • check_psbtInspect 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, taproo…No findings

    Why it is in this group

    • The description's first verb is "inspect": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check Bitcoin PSBT
    • 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 untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
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.

Tools listed without sign-in

Looked at Nov 18, 2026, 16:23 UTC, unchanged since Oct 27, 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
4
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
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://botcheck.jeffpersons.workers.dev/mcp: tools/list returned 6 tools to an anonymous client, including check_bitcoin_address (write), worksats_get_task (write), worksats_solve_task (write), worksats_credits (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "worksats_get_task" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "worksats_get_task" says "get": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools5 changed.~5 changedView diff

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http botcheck https://botcheck.jeffpersons.workers.dev/mcp
claude mcp add --transport http botcheck https://botcheck.jeffpersons.workers.dev/mcp

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__botcheck__check_psbt",
      "mcp__botcheck__check_descriptor"
    ],
    "ask": [
      "mcp__botcheck__check_bitcoin_address",
      "mcp__botcheck__worksats_get_task",
      "mcp__botcheck__worksats_solve_task",
      "mcp__botcheck__worksats_credits"
    ],
    "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 botcheck. Review it before you use it.

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/dev.workers.jeffpersons.botcheck/botcheck/verify?hash=a4df6c1db4957c522f3ac9e95410d88cdbbc27d0be6e252ac04cb7c507405723" | jq -e '.changed == false'

Pinned hash a4df6c1db495, from Nov 9, 2026, 13:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/dev.workers.jeffpersons.botcheck/botcheck/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for dev.workers.jeffpersons.botcheck/botcheck
[![Anlyon Radar](https://radar.anlyon.com/badge/dev.workers.jeffpersons.botcheck/botcheck.svg)](https://radar.anlyon.com/servers/dev.workers.jeffpersons.botcheck/botcheck)

Source: MCP Registry. Synced Oct 27, 2026, 00:17 UTC.

bot-check: Bitcoin Self-Custody & WorkSats MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the bot-check: Bitcoin Self-Custody & WorkSats MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 4 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the bot-check: Bitcoin Self-Custody & WorkSats MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the bot-check: Bitcoin Self-Custody & WorkSats MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the bot-check: Bitcoin Self-Custody & WorkSats MCP server have?

6 tools: 4 write, 2 read. check_bitcoin_address, worksats_get_task, worksats_solve_task, worksats_credits, check_psbt and check_descriptor.

Does the bot-check: Bitcoin Self-Custody & WorkSats MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the bot-check: Bitcoin Self-Custody & WorkSats MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the bot-check: Bitcoin Self-Custody & WorkSats MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 9, 2026. Every change is on this page and in its Atom feed.