Skip to main content
Glama

YRUZ x402 Endpoint Check (0.005 USDC)

x402_endpoint_check
Read-onlyIdempotent

Validate any x402 endpoint the way buyer agents see it: calls it unpaid, decodes the 402 challenge (v2 PAYMENT-REQUIRED header and v1 JSON body), checks every offer (scheme, network, asset, amount, payTo format, timeout, fee payer, EIP-712 domain), CORS exposure and the origin's discovery files (/.well-known/x402, openapi.json, llms.txt). Returns networks, prices in USD and every problem with its fix. Price: 0.005 USDC per call, paid with x402 (USDC on Base or Solana, no account, no API key); invalid input is refused before payment and a failed run is never charged. Without a payment the tool returns the x402 PaymentRequired. How to call it: get_example {"tool":"x402_endpoint_check"}. Same tool over HTTP: https://yruz.one/api/x402-check?url=https%3A%2F%2Fyruz.one%2Fapi%2Faudit

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "x402_endpoint_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesendpoint URL (required)
methodNoGET (default) or POST

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / url / examples
      Added value: +[
      +  "https://yruz.one/api/audit"
      +]
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations, the description discloses important behavior: price is 0.005 USDC per call, payment uses x402 on Base or Solana with no account or API key, invalid input is refused before payment, failed runs are never charged, and unpaid calls return PaymentRequired. These details materially affect whether and how an agent invokes the tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose and then layers on checks, pricing, payment behavior, and call guidance. It is dense and mostly earns its length, though it repeats pricing information already in the title and packs many clauses into one long paragraph.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex paid remote-check tool with no output schema, the description covers what is checked, what is returned at a high level (networks, USD prices, every problem with its fix), payment requirements, failure modes, and how to get an example call. This is enough for an agent to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both parameters are already documented in the input schema. The description mentions the target URL and provides an HTTP example, but it does not add meaningful semantics for the method parameter beyond what the schema already says (GET default or POST).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Validate any x402 endpoint the way buyer agents see it.' It then enumerates the exact checks performed, including the 402 challenge, offers, CORS, and discovery files, which distinguishes it from generic sibling tools like site_audit, uptime_check, or url_safety_check.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear usage context by explaining that the tool calls the endpoint unpaid and returns the x402 PaymentRequired without payment, and it points agents to get_example for call syntax. However, it does not explicitly state when to prefer this over generic siblings such as site_audit or url_safety_check, nor does it name exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.