Settle Watch

io.github.benmcalillycreativePublished by GitHub account benmcalillycreativev1.0.1Updated Nov 19, 2026

Check an x402 or MPP endpoint before your agent pays it: ok, caution or avoid, with reasons.

The publisher's own server: watch.diy – DIY Store Finder

VerifiedStreamable HTTPWeb executableFinanceDeveloper ToolsSecurity & Monitoring

Overview

Settle Watch's hosted MCP server (api.settlewatch.com); no sign-in required; Streamable HTTP; 2 tools.

No AI overview yet: these facts come from the registry entry and the server itself.

Endpoint
api.settlewatch.com
Last checked

Installation

In SourceWeft

  1. Open Settle Watch in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.benmcalillycreative%2Fx402-trust-board/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "settle-watch": {
      "type": "http",
      "url": "https://api.settlewatch.com/mcp"
    }
  }
}

README

Check-before-you-pay API

A Cloudflare Worker that answers one question for an agent about to pay an x402 or MPP endpoint: should I? It reads the board's latest checks (seller/<host>.json, published with the board) and charges $0.01 USDC on Base per answer (the PRICE setting in wrangler.toml), paid with x402 and settled through Coinbase's CDP facilitator. Bad input is refused before the paywall, and nothing is charged if the board can't be read.

GET /v1/check?url=<the URL you're about to pay>&payTo=<the address its 402 asks for, optional>
json
{  "verdict": "ok | caution | avoid | unknown",  "reasons": ["..."],  "endpoint": {"grade": "A", "score": 91, "uptime": 0.99, "p50_latency_ms": 210, "flags": []},  "seller": {"grade": "B", "payout": {"verified": true, "proofs": [...]}, "page": "..."},  "pay_to": {"proven_by_seller": "dns_signed", "matches_listing": true, "contradicts_seller_proof": false}}
  • avoid: a red flag (wallet switched, burn address, payout mismatch) or the address you're about to pay contradicts the payout proof the seller published.
  • caution: works, but has warnings, a C/D/F grade, or not enough history.
  • ok: graded A or B with matching terms.
  • unknown: the seller isn't in any catalog the board reads.

Free: GET / (description), GET /v1/health, and a remote MCP server at /mcp (tool check_payment, 100 checks a day per IP) for agents in Claude, Cursor and other MCP clients. The same data is free in bulk on the board (scores.json, payouts.json, seller/<host>.json); the API is for agents that want one answer, pay-per-call, without downloading anything.

Deploy (from a computer with Node 20+)

bash
cd workernpm cinpx wrangler login                        # oncenpx wrangler secret put PAY_TO            # your Base address that receives paymentsnpx wrangler secret put CDP_API_KEY_ID    # portal.cdp.coinbase.com > API keysnpx wrangler secret put CDP_API_KEY_SECRETnpx wrangler deploy

The first 1,000 settlements a month through the CDP facilitator are free; after that Coinbase charges $0.001 each, which is why the price is $0.01 rather than $0.001. After the first paid call settles, the facilitator lists the endpoint in the x402 Bazaar using the discovery metadata the Worker declares.

Test

bash
npm test        # verdict logicnpm run e2e     # wrangler dev + fake board + fake facilitator + a real x402 client with a throwaway key

Source: worker/README.md at commit d0688ed

Tools

2

check_payment

Check before paying an x402 / MPP endpoint

Before paying an agent-payable API (x402 or MPP), check whether it is safe: does it answer reliably, do its payment terms match its listing (no switched or burn wallets, no overcharges), and is the address it asks you to pay one the seller has proven is theirs. Returns verdict ok | caution | avoid | unknown with reasons. Pass the payTo address from the 402 response when you have it.

ParametersurlrequiredpayTo

check_listing

Why isn't my x402 endpoint in the Bazaar?

For sellers: check whether an x402 endpoint is listed in Coinbase's Bazaar and, if not, why. Runs Coinbase's public validator (the indexer's own checks), looks the payout address up in Coinbase's merchant list, and adds the Settle Watch's 30-day availability against Coinbase's 99% bar for featured listings. Returns findings with a fix for each.

Parametersurlrequiredmethod

Version history

1
  1. v1.0.1LatestNov 19, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Watch integrations