Boundary Guard x402
REMOTE · X402-RESOURCE-SCANNER.VERCEL.APP · SCANNED SEP 20
MCP tools for x402 readiness, paid-path probes, launch packs, and trust receipts.
Available components
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- 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 Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1048 tokens (~174/item across 6 items; 6 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 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 6 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
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the Boundary Guard x402 MCP server?
Boundary Guard x402 is a hosted endpoint at https://x402-resource-scanner.vercel.app/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 · x402-resource-scanner.vercel.app
claude mcp add --transport http larrylemonbot-boundary-guard-x402 'https://x402-resource-scanner.vercel.app/mcp'
{
"mcpServers": {
"larrylemonbot-boundary-guard-x402": {
"url": "https://x402-resource-scanner.vercel.app/mcp"
}
}
} {
"servers": {
"larrylemonbot-boundary-guard-x402": {
"type": "http",
"url": "https://x402-resource-scanner.vercel.app/mcp"
}
}
} [mcp_servers.larrylemonbot-boundary-guard-x402] url = "https://x402-resource-scanner.vercel.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"larrylemonbot-boundary-guard-x402": {
"type": "remote",
"url": "https://x402-resource-scanner.vercel.app/mcp",
"enabled": true
}
}
} openclaw mcp add larrylemonbot-boundary-guard-x402 --url 'https://x402-resource-scanner.vercel.app/mcp' --transport streamable-http
mcp_servers:
larrylemonbot-boundary-guard-x402:
url: "https://x402-resource-scanner.vercel.app/mcp" {
"McpServers": {
"larrylemonbot-boundary-guard-x402": {
"Transport": "http",
"Url": "https://x402-resource-scanner.vercel.app/mcp"
}
}
} assistant mcp add larrylemonbot-boundary-guard-x402 -t streamable-http -u 'https://x402-resource-scanner.vercel.app/mcp'
{
"mcpServers": {
"larrylemonbot-boundary-guard-x402": {
"type": "http",
"url": "https://x402-resource-scanner.vercel.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 23 Aug 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.
- 11 Aug 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
- 31 Jul 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
- 30 Jul 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 Jul 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
- 26 Jul 26 0
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 20 Sept 2026 · Probed https://x402-resource-scanner.vercel.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.vercel.app | CN=WR1,O=Google Trust Services,C=US | 29 Aug 2026 | 27 Nov 2026 | RSA 2048 | SHA256-RSA | f7911168ffa7d0f4135e24792e7a52a8 |
| SANs: *.vercel.app | ||||||
| CN=WR1,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7fd9e2c2d2048a0474b627a26d0868a7 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of x402-resource-scanner.vercel.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| vercel.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="GateCheck by LarryBuildsAI"
Bearer realm="GateCheck by LarryBuildsAI"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://x402-resource-scanner.vercel.app/mcp | Verified | 200 | |
| http (plaintext) | http://x402-resource-scanner.vercel.app/mcp | HTTPS enforced | 308 | https://x402-resource-scanner.vercel.app/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 →
boundary_guard_check Boundary Guard Check ~120
Create a deterministic, read-only pre-action receipt from request, policy, and optional result evidence. Use before an agent posts, spends, lists, or writes so the decision can be audited; no external action is executed.
| Name | Type | Req | Description |
|---|---|---|---|
| nextStep | string | – | Optional guidance stored in the receipt. |
| policy | object | – | Decision object, e.g. allow/retry/review/block and reason. |
| request | object | yes | Action metadata the agent is about to perform. |
| result | object | – | Optional result or dry-run summary to hash into evidence. |
| Name | Type | Req | Description |
|---|---|---|---|
| claimBoundary | string | yes | – |
| createdAt | string | yes | – |
| decision | string | yes | – |
| evidenceHash | string | yes | – |
| marketplacePositioning | object | – | – |
| nextStep | string | – | – |
| receiptId | string | yes | – |
No examples provided.
check_agent_tool_readiness GateCheck Readiness ~239
GateCheck readiness: check whether an x402/agent-facing tool is ready for agent routing, marketplace listing, and paid-path monitoring, including public agent discovery surfaces (/llms.txt, /agents.txt, /.well-known/mcp.json, /mcp). Pass target plus optional tier, marketplace_url, expected_resources, and paid_path; deep/report tiers add unpaid 402 probing when paid_path is supplied. Tiers: quick $1, deep $5, report $10.
| Name | Type | Req | Description |
|---|---|---|---|
| expected | object | – | Optional expected x402 network/asset/price metadata for paid_path probes. |
| expected_resources | integer | – | Optional expected resource count. |
| marketplace_url | string | – | Optional marketplace/listing URL to compare against public metadata. |
| method | string | – | Safe unpaid probe method when paid_path is supplied. Defaults to GET. |
| paid_path | string | – | Optional specific paid endpoint to probe without payment for deep/report tiers. |
| target | string | yes | Target API/provider base URL to scan. |
| tier | string | – | Readiness depth. quick=$1, deep=$5, report=$10. Defaults to quick. |
| Name | Type | Req | Description |
|---|---|---|---|
| checks | object | yes | – |
| healthProbe | object|null | – | – |
| issues | array | yes | – |
| priceUsd | string | yes | – |
| product | string | yes | – |
| ready | boolean | yes | – |
| recommendedFixes | array | yes | – |
| report | object | – | – |
| scan | object | – | – |
| score | integer | yes | – |
| target | string | yes | – |
| tier | string | yes | – |
No examples provided.
generate_trust_receipt Generate Trust Receipt ~187
Generate a deterministic trust receipt from sanitized request/policy/result/payment summaries. Do not submit raw auth headers, cookies, API keys, private keys, payment signatures, payment response headers, customer prompts, customer documents, or payer-identifying evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| nextStep | string | – | Optional receipt next-step guidance. |
| payment | object | – | Optional sanitized payment summary or caller-provided hashes only; do not include raw payment signatures, raw payment response headers, private keys, API keys, cookies, payer-identifying evidence, or… |
| policy | object | – | Sanitized policy or decision summary to hash. |
| request | object | yes | Sanitized request/action summary to hash; omit raw prompts, documents, credentials, cookies, auth headers, signatures, and secrets. |
| result | object | – | Sanitized outcome/result summary to hash; omit customer data and secret-like values. |
| Name | Type | Req | Description |
|---|---|---|---|
| claimBoundary | string | yes | – |
| createdAt | string | yes | – |
| decision | string | yes | – |
| evidenceHash | string | yes | – |
| marketplacePositioning | object | – | – |
| nextStep | string | – | – |
| receiptId | string | yes | – |
No examples provided.
generate_x402_launch_pack x402 Launch Pack Generator ~275
Generate marketplace-safe launch assets for an x402/MCP seller: listing copy, buyer FAQ, checklist, approval packet, and claim boundaries. Pass target plus optional product_name, audience, primary_use_case, marketplace_url, and paid_path; service/premium tiers include readiness evidence. Tiers: single $9, service $29, premium $49.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | – | Primary buyer/audience for listing copy. |
| desired_marketplaces | array | – | Optional marketplace names to include in launch planning. |
| expected | object | – | Optional expected x402 network/asset/price metadata for paid_path probes. |
| expected_resources | integer | – | Optional expected resource count. |
| marketplace_url | string | – | Optional marketplace/listing URL to compare against public metadata. |
| method | string | – | Safe unpaid probe method when paid_path is supplied. Defaults to GET. |
| paid_path | string | – | Optional paid endpoint to validate via unpaid 402 challenge for service/premium packs. |
| primary_use_case | string | – | Primary buyer outcome/use case. |
| product_name | string | – | Buyer-facing product title. |
| target | string | yes | Target API/provider base URL to package for launch. |
| tier | string | – | Launch pack depth. single=$9, service=$29, premium=$49. Defaults to single. |
| Name | Type | Req | Description |
|---|---|---|---|
| approvalRequiredBeforeDistribution | boolean | yes | – |
| claimBoundary | string | – | – |
| launchPack | object | yes | – |
| priceUsd | string | yes | – |
| product | string | yes | – |
| productName | string | yes | – |
| readiness | object | – | – |
| readinessScore | integer | yes | – |
| readyForDistribution | boolean | – | – |
| report | object | – | – |
| target | string | yes | – |
| tier | string | yes | – |
No examples provided.
probe_x402_paid_path x402 Paid-Path Health Probe ~121
Probe a public x402 paid endpoint without signing or paying, then parse the HTTP 402 challenge. Pass target plus optional expected network/asset/price to verify payment metadata and receive a deterministic health receipt.
| Name | Type | Req | Description |
|---|---|---|---|
| expected | object | – | Optional expected x402 metadata such as network, asset, and priceUsd. |
| method | string | – | Safe unpaid probe method. Defaults to GET. |
| mode | string | – | Probe mode for v1. Defaults to unpaid_402. |
| target | string | yes | Specific paid endpoint URL to probe without payment. |
| Name | Type | Req | Description |
|---|---|---|---|
| checks | object | yes | – |
| healthy | boolean | yes | – |
| issues | array | yes | – |
| observed | object | yes | – |
| receipt | object | yes | – |
| recommendedFixes | array | yes | – |
| target | string | yes | – |
No examples provided.
scan_x402_resource x402 Resource Scan ~106
Read-only scan of a public API/provider URL for x402, OpenAPI, pricing, and agent-discovery metadata. Pass url, and optionally marketplace_url plus expected_resources, to get a readiness score, issues, and fixes; no private endpoints are called.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_resources | integer | – | Optional expected resource count. |
| marketplace_url | string | – | Optional marketplace/listing URL to compare against public metadata. |
| url | string | yes | Target API/provider base URL to scan. |
| Name | Type | Req | Description |
|---|---|---|---|
| issues | array | yes | – |
| marketplacePositioning | object | – | – |
| nextSteps | array | yes | – |
| prices | array | – | – |
| score | integer | yes | – |
| target | string | yes | – |
No examples provided.
What is the Boundary Guard x402 MCP server?
Boundary Guard x402 is an MCP server listed in the public MCP registry as io.github.LarryLemonBot/boundary-guard-x402. MCP tools for x402 readiness, paid-path probes, launch packs, and trust receipts. This page covers its hosted endpoint (https://x402-resource-scanner.vercel.app/mcp).
Is the Boundary Guard x402 MCP server safe to use?
Boundary Guard x402 scores 87 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 Boundary Guard x402 MCP server expose?
Boundary Guard x402 exposes 6 tools: boundary_guard_check, scan_x402_resource, probe_x402_paid_path, check_agent_tool_readiness, generate_x402_launch_pack, generate_trust_receipt. Their descriptions and schemas cost roughly 1,048 tokens of context every time the server is loaded.
Does the Boundary Guard x402 MCP server require authentication?
Yes. Boundary Guard x402 asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Boundary Guard x402 MCP server still maintained?
Boundary Guard x402 is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.