Skip to main content
Glama
verifystack-x402-mcp

verifystack-x402-mcp

Official

verifystack_domain_intel

Assess a domain or URL for phishing risk and trust signals using DNS records (SPF/DMARC/MX), RDAP registration age, and HTTPS security headers.

Instructions

Paid x402 API ($0.004 USDC on Base): Domain anti-phishing & trust profiler via Cloudflare DoH (A/MX/SPF/DMARC), RDAP registration age, and HTTPS security headers.

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": {
      "domainOrUrl": "<domainOrUrl>"
    },
    "name": "verifystack_domain_intel"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainOrUrlYesPublic domain or URL to inspect (e.g. https://app.uniswap.org)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the most consequential behavior: this is a paid call costing $0.004 USDC on Base via x402, which an agent must know before invoking. It also names the upstream providers used (Cloudflare DoH, RDAP), but omits rate limits, failure/refund behavior when payment or lookup fails, and whether a charge occurs on error.

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?

One dense sentence that front-loads the cost and payment rail before the capability, so the highest-friction fact is seen first. The parenthetical record-type list is compact and earns its place, though the sentence is packed enough to be slightly hard to scan.

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

Completeness3/5

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

For a one-parameter read tool this covers the cost model and the data sources consulted, which is the main thing an agent needs to decide to call it. Because no output schema exists, the description should say what shape of result comes back (a trust score, raw DNS records, or flags) and it does not.

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% and the single parameter already documents that a public domain or URL is accepted, including an example. The description adds no format constraints or normalization rules (e.g., whether a bare domain vs. a full path matters), so the schema does all the work.

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?

States a specific verb and resource: a 'Domain anti-phishing & trust profiler' and names the concrete data sources (Cloudflare DoH A/MX/SPF/DMARC, RDAP registration age, HTTPS headers). An agent can tell this inspects domains rather than tokens, URLs, or wallets as its siblings do, though it never explicitly contrasts with verifystack_clean_url or verifystack_token_safety.

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

Usage Guidelines3/5

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

Usage is implied by the described outputs (phishing risk, registration age, header security), so an agent can infer this is for pre-interaction domain trust checks. There is no explicit when-to-use/when-not guidance and no named alternative for overlapping checks such as URL cleaning, leaving the routing decision to inference.

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