Skip to content

Settle Watch MCP server

io.github.benmcalillycreative/x402-trust-boardbenmcalillycreativestreamable-httpv1.0.1Scanned

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

2 tools: 1 do something that can't be undone and 1 change things.

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

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • 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 Settle Watch MCP server can do

The Settle Watch MCP server is published by the GitHub account benmcalillycreative. It has 2 tools. It can do things that cannot be undone, such as sending, paying or publishing (check_payment) and create or change data (1 tool: check_listing), but cannot delete data. None of its tools only reads.

2 tools bring in text other people can write (check_payment and check_listing); 2 tools can send data out of your system (check_payment and check_listing).

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 19, 2026, version 1.0.1.

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.

2 tools

Can't be undone 1Claude Code: ask
  • check_paymentBefore 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 overcha…Reads text others writeCan send data out1 finding

    Why it is in this group

    • The name "check_payment" says "payment": a word that usually means money moves, which cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Findings

    • Warn

      The server marks "check_payment" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":true}; The name "check_payment" says "payment": a word that usually means money moves, which cannot be taken back.

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

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
Changes things 1Claude Code: ask
  • check_listingFor sellers: check whether an x402 endpoint is listed in Coinbase's Bazaar and, if not, why.Reads text others writeCan send data outNo 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.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true

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.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
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 19, 2026, 17:20 UTC, unchanged since Nov 19, 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
2
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 2 tools that change things (1 irreversible, 1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.settlewatch.com/mcp: tools/list returned 2 tools to an anonymous client, including check_payment (irreversible), check_listing (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "check_payment" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":true}; The name "check_payment" says "payment": a word that usually means money moves, which cannot be taken back.

    What this check looks for

History

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

  1. Tools1 added.+1 addedView diff

Install

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

claude mcp add --transport http x402-trust-board https://api.settlewatch.com/mcp
claude mcp add --transport http x402-trust-board https://api.settlewatch.com/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": [],
    "ask": [
      "mcp__x402-trust-board__check_payment",
      "mcp__x402-trust-board__check_listing"
    ],
    "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 x402-trust-board. Review it before you use it.

Capability tags behind 2 rules
  • mcp__x402-trust-board__check_payment untrusted-input, outbound
  • mcp__x402-trust-board__check_listing untrusted-input, outbound

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.benmcalillycreative/x402-trust-board/verify?hash=6c64f3ebb5f4855e3fcb9487369db7c2fd19c021065277cb4e4aec1372db60cb" | jq -e '.changed == false'

Pinned hash 6c64f3ebb5f4, from Nov 19, 2026, 04: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.benmcalillycreative/x402-trust-board/changes.xml

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

Badge

Anlyon Radar badge for io.github.benmcalillycreative/x402-trust-board
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.benmcalillycreative/x402-trust-board.svg)](https://radar.anlyon.com/servers/io.github.benmcalillycreative/x402-trust-board)

Source: MCP Registry · repository. Synced Nov 19, 2026, 05:17 UTC.

Settle Watch MCP server: questions and answers

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

Is the Settle Watch MCP server safe?

No scan can promise that. What its definitions show: 2 tools, 2 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 Settle Watch MCP server delete data?

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

Can the Settle Watch MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: check_payment.

What tools does the Settle Watch MCP server have?

2 tools: 1 irreversible, 1 write. check_payment and check_listing.

Does the Settle Watch MCP server need sign-in or OAuth?

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

Does the Settle Watch MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): check_payment and check_listing.

Has the Settle Watch MCP server changed its tools?

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