dev.workers.sebastiaan-ba3.payverify/tools
REMOTE · PAYVERIFY.SEBASTIAAN-BA3.WORKERS.DEV
Verify a Base USDC transaction or x402 settlement landed. Free, no account needed.
Available components
Last scanned (21 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 22 Oct 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 Security46
- 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 check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 373 tokens (~373/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: excellent → good functional
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 258 → 409 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Schema quality: good → excellent functional
- 15 Oct 26 57
First indexed and scored.
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 22 Oct 2026 · Probed https://payverify.sebastiaan-ba3.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sebastiaan-ba3.workers.dev | CN=YE1,O=Let's Encrypt,C=US | 18 Sept 2026 | 17 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 61f8a0e14c80aee897d02cfc8b1b838082b |
| SANs: *.sebastiaan-ba3.workers.dev, sebastiaan-ba3.workers.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of payverify.sebastiaan-ba3.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://payverify.sebastiaan-ba3.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://payverify.sebastiaan-ba3.workers.dev/mcp | Served over HTTP | 200 |
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 →
verify_base_usdc_tx ~155
Verify a Base (Ethereum L2) transaction and report every USDC Transfer event in it: sender, recipient, amount, block number, on-chain success, and confirmation age. Free, no account, reads Base's public JSON-RPC live. Example you can call right now, no setup: {"tx": "0xad887d8844d9d8b093b8040c1950e66b7cf3c9f3c98644bed7fb911c6a2e8079"} -- a real, already-settled USDC transfer, always returns found:true.
| Name | Type | Req | Description |
|---|---|---|---|
| tx | string | yes | 0x-prefixed 64-hex-character Base transaction hash. |
No output schema declared.
No examples provided.
How do I install the dev.workers.sebastiaan-ba3.payverify/tools MCP server?
dev.workers.sebastiaan-ba3.payverify/tools is a hosted endpoint at https://payverify.sebastiaan-ba3.workers.dev/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 · payverify.sebastiaan-ba3.workers.dev
claude mcp add --transport http dev-workers-sebastiaan-ba3-payverify-tools 'https://payverify.sebastiaan-ba3.workers.dev/mcp'
What is the dev.workers.sebastiaan-ba3.payverify/tools MCP server?
dev.workers.sebastiaan-ba3.payverify/tools is an MCP server listed in the public MCP registry as dev.workers.sebastiaan-ba3.payverify/tools. Verify a Base USDC transaction or x402 settlement landed. Free, no account needed. This page covers its hosted endpoint (https://payverify.sebastiaan-ba3.workers.dev/mcp).
Is the dev.workers.sebastiaan-ba3.payverify/tools MCP server safe to use?
dev.workers.sebastiaan-ba3.payverify/tools scores 60 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 dev.workers.sebastiaan-ba3.payverify/tools MCP server expose?
dev.workers.sebastiaan-ba3.payverify/tools exposes 1 tool: verify_base_usdc_tx. Their descriptions and schemas cost roughly 155 tokens of context every time the server is loaded.
Does the dev.workers.sebastiaan-ba3.payverify/tools MCP server require authentication?
No. We connected to dev.workers.sebastiaan-ba3.payverify/tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the dev.workers.sebastiaan-ba3.payverify/tools MCP server still maintained?
dev.workers.sebastiaan-ba3.payverify/tools is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.