Skip to content

x402 Pay — USDC API Payment Helper MCP server

com.scriptmasterlabs/x402-payscriptmasterlabs.comstreamable-httpv1.0.3Scanned

Pay for APIs with USDC. Read-only x402 payment discovery, verification, evidence, and status.

5 tools: 2 do something that can't be undone and 3 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here do something that can't be undone. 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 x402 Pay — USDC API Payment Helper MCP server can do

The x402 Pay — USDC API Payment Helper MCP server is published by scriptmasterlabs.com, a domain the MCP Registry verified. It has 5 tools. It can do things that cannot be undone, such as sending, paying or publishing (payment_info and check_payment), but cannot delete data. 3 tools only read.

1 tool reads private data (list_paid_apis); 5 tools bring in text other people can write (payment_info, list_paid_apis, check_payment and 2 more); 2 tools can send data out of your system (check_payment and x402_inspect_challenge). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 5 findings (tool-shadowing, annotation-conflict and credentials-mention). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 18, 2026, version 1.0.3.

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.

5 tools

Can't be undone 2Claude Code: ask
  • check_paymentInspect a public HTTPS URL for a fresh x402 v2 HTTP 402 challenge using an unsigned GET with a 10-second network timeout and no redirect following.Reads text others writeCan send data out2 findings

    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

    • Info

      The input schema at properties.url.description mentions "credentials".

      Matched text

      inputSchema.properties.url.description: "...ned GET. No payment headers; redirects, credentials and private network targets are rejecte..."

      What this check looks for
    • 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,"destructiveHint":false,"idempotentHint":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
    Inspect a public HTTPS URL for a fresh x402 v2 HTTP 402 challenge using an unsigned GET with a 10-second network timeout and no redirect following. Returns validated payTo, asset, network, atomic amount, resource and maxTimeoutSeconds; incomplete or non-x402 responses return challenge=null and a reason. Does not sign, settle or verify receipts. Fresh requirements override documented receiver hints; inspect canonical_receiver_match before choosing to pay.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
  • payment_infoRead the documented SML x402 v2 Base/USDC configuration and receiver before selecting a paid route.Reads text others write2 findings

    Why it is in this group

    • The name "payment_info" 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.

    Findings

    • Warn

      The description contains "override these hints; this tool", wording about other tools or servers.

      Matched text

      description: "...nly policy. Fresh resource requirements override these hints; this tool does not sign, spend or prove settlemen..."

      What this check looks for
    • Warn

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

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "payment_info" 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
    Read the documented SML x402 v2 Base/USDC configuration and receiver before selecting a paid route. Returns configuration and a read-only policy. Fresh resource requirements override these hints; this tool does not sign, spend or prove settlement.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
Only reads 3Show 3 read-only tools
  • check_statusRead the current SqueezeOS backend status and payment-readiness evidence.Reads text others writeNo findings

    Why it is in this group

    • The name "check_status" says "status": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Read the current SqueezeOS backend status and payment-readiness evidence. Returns both upstream envelopes and autonomous_spend=false. Use to diagnose readiness before purchase; HTTP availability or readiness flags alone do not establish settled or accepted delivery.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
  • list_paid_apisList paid API operations declared by the live SqueezeOS OpenAPI document, bounded by limit.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "list_paid_apis" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "document": it reads documents.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    List paid API operations declared by the live SqueezeOS OpenAPI document, bounded by limit. Returns method, path, job and advertised price. Use for route selection, then inspect that resource's fresh 402 challenge; listed prices do not authorize payment.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
  • x402_inspect_challengeInspect a fresh x402 v2 challenge without sending payment.Reads text others writeCan send data out1 finding

    Why it is in this group

    • The name "x402_inspect_challenge" says "inspect": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Findings

    • Info

      The input schema at properties.url.description mentions "credentials".

      Matched text

      inputSchema.properties.url.description: "...ned GET. No payment headers; redirects, credentials and private network targets are rejecte..."

      What this check looks for
    Description, as the server wrote it
    Inspect a fresh x402 v2 challenge without sending payment. Compatible alias of check_payment with the same schema, 10-second unsigned probe and result. Use before a paid resource call; do not use as a signer, receipt verifier or settlement proof. Non-402 and incomplete challenges remain null rather than receiving invented defaults.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: 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.

10 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 private-data tool breaks every one.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write5
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.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__x402-pay__list_paid_apis"
    ]
  }
}

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 20, 2026, 19:22 UTC, unchanged since Oct 22, 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 (2 irreversible). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://squeezeos-api.onrender.com/mcp/x402-pay: tools/list returned 5 tools to an anonymous client, including payment_info (irreversible), check_payment (irreversible)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

3 warn2 info
  • The description contains "override these hints; this tool", wording about other tools or servers.

    Matched text

    description: "...nly policy. Fresh resource requirements override these hints; this tool does not sign, spend or prove settlemen..."

    What this check looks for
  • The server marks "payment_info" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

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

    What this check looks for
  • 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,"destructiveHint":false,"idempotentHint":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
  • The input schema at properties.url.description mentions "credentials".

    Matched text

    inputSchema.properties.url.description: "...ned GET. No payment headers; redirects, credentials and private network targets are rejecte..."

    What this check looks for
  • The input schema at properties.url.description mentions "credentials".

    Matched text

    inputSchema.properties.url.description: "...ned GET. No payment headers; redirects, credentials and private network targets are rejecte..."

    What this check looks for

History

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

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

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

claude mcp add --transport http x402-pay https://squeezeos-api.onrender.com/mcp/x402-pay
claude mcp add --transport http x402-pay https://squeezeos-api.onrender.com/mcp/x402-pay

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__x402-pay__list_paid_apis",
      "mcp__x402-pay__check_status"
    ],
    "ask": [
      "mcp__x402-pay__payment_info",
      "mcp__x402-pay__check_payment",
      "mcp__x402-pay__x402_inspect_challenge"
    ],
    "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-pay. Review it before you use it.

Capability tags behind 5 rules
  • mcp__x402-pay__payment_info untrusted-input
  • mcp__x402-pay__list_paid_apis private-data, untrusted-input
  • mcp__x402-pay__check_payment untrusted-input, outbound
  • mcp__x402-pay__x402_inspect_challenge untrusted-input, outbound
  • mcp__x402-pay__check_status untrusted-input

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/com.scriptmasterlabs/x402-pay/verify?hash=63847a691d2d74a9ea197292b89071aa841753eff2cee8befdd724d4540b0bb3" | jq -e '.changed == false'

Pinned hash 63847a691d2d, from Nov 18, 2026, 21:17 UTC.

Watch

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

https://radar.anlyon.com/servers/com.scriptmasterlabs/x402-pay/changes.xml

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

Badge

Anlyon Radar badge for com.scriptmasterlabs/x402-pay
[![Anlyon Radar](https://radar.anlyon.com/badge/com.scriptmasterlabs/x402-pay.svg)](https://radar.anlyon.com/servers/com.scriptmasterlabs/x402-pay)

Source: MCP Registry · repository. Synced Nov 5, 2026, 02:17 UTC.

x402 Pay — USDC API Payment Helper MCP server: questions and answers

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

Is the x402 Pay — USDC API Payment Helper MCP server safe?

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

Can the x402 Pay — USDC API Payment Helper MCP server delete data?

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

Can the x402 Pay — USDC API Payment Helper MCP server do things that cannot be undone?

Yes. 2 tools can send, pay, publish or merge: payment_info and check_payment.

What tools does the x402 Pay — USDC API Payment Helper MCP server have?

5 tools: 2 irreversible, 3 read. payment_info, check_payment, list_paid_apis, x402_inspect_challenge and check_status.

Does the x402 Pay — USDC API Payment Helper MCP server need sign-in or OAuth?

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

Does the x402 Pay — USDC API Payment Helper 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 x402_inspect_challenge.

Has the x402 Pay — USDC API Payment Helper MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.