Skip to main content
Glama

YRUZ URL Safety Check (0.005 USDC)

url_safety_check
Read-onlyIdempotent

Should an agent open, sign or pay this link? Follows every redirect and checks the final site: domain age (RDAP), TLS certificate age and validity, look-alike and punycode domains, brand impersonation (PayPal, Coinbase, MetaMask, Phantom ...), risky TLDs, URL shorteners, raw-IP hosts, downloads, password and seed-phrase forms and wallet-drainer patterns. Returns a 0-100 risk score, a verdict (safe, caution, dangerous) and every signal explained. Heuristic, no blocklist. 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":"url_safety_check"}. Same tool over HTTP: https://yruz.one/api/safety?url=https%3A%2F%2Fgithub.com%2Flogin

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": "url_safety_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYeslink to check (required), e.g. https://example.com/login

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / url / examples
      Added value: +[
      +  "https://github.com/login"
      +]
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Discloses behavior far beyond the annotations: heuristic with no blocklist, follows every redirect, returns a 0-100 score plus verdict and per-signal explanations, costs 0.005 USDC via x402 with no account, invalid input refused before payment, failed runs never charged, and an unpaid call returns x402 PaymentRequired. That is exactly the kind of write-adjacent/paid-operation context annotations (readOnlyHint, idempotentHint) cannot convey.

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?

Front-loaded with the decision question and a dense, comma-separated signal list; payment terms and error semantics follow in the right order. Slightly over-packed – the trailing literal HTTP endpoint URL is incidental detail that most agents don't need.

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 one-parameter paid tool with no output schema, the description covers outcome shape (score, verdict, explained signals), failure modes, pricing/payment flow, and a discovery path via get_example. Nothing an agent needs in order to call it or to interpret the cost is missing.

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?

Single required `url` parameter with 100% schema description coverage including an example, so the schema carries the semantics. The description adds no format guidance (schemes, encoded URLs, bare domains) beyond what the schema already shows, so this lands at the baseline.

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

Purpose4/5

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

Opens with a concrete decision frame ("Should an agent open, sign or pay this link?") and then enumerates exactly what is inspected: redirects, RDAP domain age, TLS, punycode/look-alikes, brand impersonation, wallet-drainer patterns. The scope is specific enough that it materially differs from link_preview or domain_intel, but the description never names those siblings to draw the boundary explicitly.

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?

The use context is unambiguous – vet a link before opening, signing, or paying – and it points to get_example for invocation help plus an HTTP equivalent endpoint. It stops short of stating when NOT to use it or which sibling to pick instead (e.g. domain_intel for a bare domain with no link).

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.