x402 Pay — USDC API Payment Helper
REMOTE · SQUEEZEOS-API.ONRENDER.COM
Pay for APIs with USDC. Read-only x402 payment discovery, verification, evidence, and status.
Available components
Last scanned (6 hours ago)
Scores higher than 95% of remote servers
Reachable. Last reached 7 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 Security80
- 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 455 tokens (~91/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 26 0
- Stability: pass → 0.97 functional
- 29 Oct 26 0
- The server now declares the “prompts” capability functional
- The server now declares the “resources” capability functional
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- 14 Oct 26 +4
- Tool “check_payment” rewrote its description, which is the text the model reads security
- Tool “check_status” rewrote its description, which is the text the model reads security
- Tool “list_paid_apis” rewrote its description, which is the text the model reads security
- Tool “payment_info” rewrote its description, which is the text the model reads security
- Schema quality: 35 → 91 ▼ functional
- Tool coverage: 0% → 100% ▲ functional
- Tool “check_payment” now declares an output schema ▲ functional
- Tool “check_status” now declares an output schema ▲ functional
- Tool “list_paid_apis” now declares an output schema ▲ functional
- Tool “payment_info” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- Schema quality: good → excellent functional
- Server version: 1.0.1 → 1.0.2 functional
- New tool “x402_inspect_challenge” functional
- “check_payment” reworded the description of “url” cosmetic
- “list_paid_apis” reworded the description of “limit” cosmetic
- 9 Oct 26 +1
- Stability: 0.97 → pass security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 7 Nov 2026 · Probed https://squeezeos-api.onrender.com/mcp/x402-pay
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=onrender.com | CN=WE1,O=Google Trust Services,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 6eb1e3fe7d0631ea1337bfa4a321c137 |
| SANs: onrender.com, *.onrender.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of squeezeos-api.onrender.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| onrender.com. | No DS | 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 |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data: |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://squeezeos-api.onrender.com/mcp/x402-pay | Verified | 200 | |
| http (plaintext) | http://squeezeos-api.onrender.com/mcp/x402-pay | HTTPS enforced | 301 | https://squeezeos-api.onrender.com/mcp/x402-pay |
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_payment Check Payment ~127
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Full public HTTPS URL to inspect with an unsigned GET. No payment headers; redirects, credentials and private network targets are rejected. |
| Name | Type | Req | Description |
|---|---|---|---|
| canonical_receiver_match | boolean | – | Comparison with documented SML receiver; a mismatch never rewrites upstream requirements. |
| challenge | – | yes | Fresh validated requirements, or null. No synthetic defaults are inserted. |
| http_status | integer | yes | Observed HTTP status; zero means no HTTP response was received. |
| is_x402 | boolean | yes | True only for HTTP 402 with complete validated x402 v2 requirements. |
| missing_fields | array | – | – |
| payment_sent | – | yes | – |
| raw_headers | object | – | Allowlisted response headers only; never cookies or authentication headers. |
| reason | string | – | – |
No examples provided.
check_status Check Status ~53
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| autonomous_spend | – | yes | – |
| core | object | yes | – |
| hosting | string | yes | – |
| ok | boolean | yes | – |
| payment_readiness | object | yes | – |
No examples provided.
list_paid_apis List Paid Apis ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of declared paid operations to return; not an exhaustive catalog count. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| ok | boolean | yes | – |
| operations | array | yes | – |
| source | string | yes | – |
No examples provided.
payment_info Payment Info ~56
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | – |
| asset_contract | string | yes | – |
| network | string | yes | – |
| pay_to | string | yes | – |
| policy | object | yes | – |
| product | string | yes | – |
| protocol | string | yes | – |
No examples provided.
x402_inspect_challenge X402 Inspect Challenge ~107
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Full public HTTPS URL to inspect with an unsigned GET. No payment headers; redirects, credentials and private network targets are rejected. |
| Name | Type | Req | Description |
|---|---|---|---|
| canonical_receiver_match | boolean | – | Comparison with documented SML receiver; a mismatch never rewrites upstream requirements. |
| challenge | – | yes | Fresh validated requirements, or null. No synthetic defaults are inserted. |
| http_status | integer | yes | Observed HTTP status; zero means no HTTP response was received. |
| is_x402 | boolean | yes | True only for HTTP 402 with complete validated x402 v2 requirements. |
| missing_fields | array | – | – |
| payment_sent | – | yes | – |
| raw_headers | object | – | Allowlisted response headers only; never cookies or authentication headers. |
| reason | string | – | – |
No examples provided.
How do I install the x402 Pay — USDC API Payment Helper MCP server?
x402 Pay — USDC API Payment Helper is a hosted endpoint at https://squeezeos-api.onrender.com/mcp/x402-pay, 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 · squeezeos-api.onrender.com
claude mcp add --transport http com-scriptmasterlabs-x402-pay 'https://squeezeos-api.onrender.com/mcp/x402-pay'
What is the x402 Pay — USDC API Payment Helper MCP server?
x402 Pay — USDC API Payment Helper is an MCP server listed in the public MCP registry as com.scriptmasterlabs/x402-pay. Pay for APIs with USDC. Read-only x402 payment discovery, verification, evidence, and status. This page covers its hosted endpoint (https://squeezeos-api.onrender.com/mcp/x402-pay).
Is the x402 Pay — USDC API Payment Helper MCP server safe to use?
x402 Pay — USDC API Payment Helper scores 88 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 x402 Pay — USDC API Payment Helper MCP server expose?
x402 Pay — USDC API Payment Helper exposes 5 tools: payment_info, list_paid_apis, check_payment, x402_inspect_challenge, check_status. Their descriptions and schemas cost roughly 425 tokens of context every time the server is loaded.
Does the x402 Pay — USDC API Payment Helper MCP server require authentication?
No. We connected to x402 Pay — USDC API Payment Helper without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the x402 Pay — USDC API Payment Helper MCP server still maintained?
x402 Pay — USDC API Payment Helper is still listed as active in the MCP registry. We last reached this channel on 7 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the x402 Pay — USDC API Payment Helper MCP server?
VerifyMCP ran 13 checks on x402 Pay — USDC API Payment Helper, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.