ScorpTech x402 API

Reverse Dns

reverse_dns

Read-onlyIdempotent

Reverse DNS (PTR) for up to 20 IPv4 / IPv6 addresses with forward-confirmed reverse DNS (FCrDNS: does the PTR hostname resolve back to the same IP?), PTR name, TTL and NXDOMAIN / SERVFAIL status, over DNS-over-HTTPS. Useful for mail-server checks, log enrichment and bot verification (e.g. is this really Googlebot). Price: $0.002 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/reverse-dns

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": {
      "ips": "<ips>"
    },
    "name": "reverse_dns"
  }
}

Input Schema

Name	Required	Description	Default
`ips`	Yes	IPv4 / IPv6 addresses
`forward`	No	Forward-confirm each PTR hostname

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, and the description adds genuinely useful context beyond them: DNS-over-HTTPS transport, the returned fields (PTR name, TTL, NXDOMAIN/SERVFAIL), and a per-call price with an x402/Solana payment requirement. Rate limits and failure-billing edge cases are unstated, so not a 5.

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?

A single dense block with the core capability front-loaded and no filler sentences; every clause (scope, FCrDNS, return fields, price, HTTPS endpoint) carries information. Slightly crowded, with the endpoint URL and pricing competing for attention with the primary behavior.

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?

No output schema exists, and the description compensates by naming the returned values (PTR name, TTL, NXDOMAIN/SERVFAIL) and explaining FCrDNS. With only two parameters fully documented and the payment model disclosed, an agent has everything needed to call it correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description earns a bump by spelling out what the 'forward' flag actually does ('does the PTR hostname resolve back to the same IP?') and confirming the 20-address cap, adding meaning beyond the terse schema text 'Forward-confirm each PTR hostname'.

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?

States the exact operation (reverse DNS / PTR lookup), the input unit (up to 20 IPv4/IPv6 addresses), and the enrichment applied (FCrDNS). This clearly separates it from siblings like dns_dump, dns_propagation, dnssec_check, and ip_intel without opening any schema.

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?

Gives concrete use cases: mail-server checks, log enrichment, and bot verification (explicitly the Googlebot example). It does not name a sibling alternative or state when NOT to use it (e.g. versus ip_intel or dns_dump), which keeps it below a 5.

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

All ScorpTech x402 API tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?