app.netlify.micropay-test-suite/micropay-test-suite
REMOTE · MICROPAY-TEST-SUITE.NETLIFY.APP
Verify your agent's x402 payment flow for free on Base Sepolia testnet before real money moves.
Available components
Last scanned (11 hours ago)
Scores higher than 87% of remote servers
Reachable. Last reached 5 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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability86
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 112 tokens (~112/item across 1 items; 1 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 27 Oct 26 +1
- Stability: 0.97 → pass security
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 −5
- Stability: pass → 0.67 functional
- 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
- 27 Sept 26 0
- HTTPS: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ 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 5 Nov 2026 · Probed https://micropay-test-suite.netlify.app/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.netlify.app,O=Netlify\, Inc,L=San Francisco,ST=California,C=US | CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1,O=DigiCert Inc,C=US | 16 Feb 2026 | 19 Mar 2027 | ECDSA 256 | SHA256-RSA | cd5d0afb0611b5bd9d692535c0ca7c4 |
| SANs: *.netlify.app, netlify.app | ||||||
| CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 30 Mar 2021 | 29 Mar 2031 | RSA 2048 | SHA256-RSA | cf5bd062b5602f47ab8502c23ccf066 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of micropay-test-suite.netlify.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| netlify.app. | absent | 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; preload |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://micropay-test-suite.netlify.app/api/mcp | Verified | 200 | |
| http (plaintext) | http://micropay-test-suite.netlify.app/api/mcp | HTTPS enforced | 301 | https://micropay-test-suite.netlify.app/api/mcp |
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_flow Check x402 payment flow ~112
Verifies an agent's x402 payment flow against a free Base Sepolia testnet endpoint. Call with no arguments first to get back the payment-required challenge (price, network, payTo). Sign it with your x402 client, then call again passing paymentSignature as the encoded PAYMENT-SIGNATURE header value to get back a verified/failed receipt.
| Name | Type | Req | Description |
|---|---|---|---|
| paymentSignature | string | – | Encoded PAYMENT-SIGNATURE header from a signed x402 payment payload. Omit to receive the payment-required challenge instead. |
No output schema declared.
No examples provided.
How do I install the app.netlify.micropay-test-suite/micropay-test-suite MCP server?
app.netlify.micropay-test-suite/micropay-test-suite is a hosted endpoint at https://micropay-test-suite.netlify.app/api/mcp, 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 · micropay-test-suite.netlify.app
claude mcp add --transport http app-netlify-micropay-test-suite-micropay-test-su 'https://micropay-test-suite.netlify.app/api/mcp'
What is the app.netlify.micropay-test-suite/micropay-test-suite MCP server?
app.netlify.micropay-test-suite/micropay-test-suite is an MCP server listed in the public MCP registry as app.netlify.micropay-test-suite/micropay-test-suite. Verify your agent's x402 payment flow for free on Base Sepolia testnet before real money moves. This page covers its hosted endpoint (https://micropay-test-suite.netlify.app/api/mcp).
Is the app.netlify.micropay-test-suite/micropay-test-suite MCP server safe to use?
app.netlify.micropay-test-suite/micropay-test-suite scores 83 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 app.netlify.micropay-test-suite/micropay-test-suite MCP server expose?
app.netlify.micropay-test-suite/micropay-test-suite exposes 1 tool: check_payment_flow. Their descriptions and schemas cost roughly 112 tokens of context every time the server is loaded.
Does the app.netlify.micropay-test-suite/micropay-test-suite MCP server require authentication?
No. We connected to app.netlify.micropay-test-suite/micropay-test-suite without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the app.netlify.micropay-test-suite/micropay-test-suite MCP server still maintained?
app.netlify.micropay-test-suite/micropay-test-suite is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.