ScorpTech x402 API

Slaac Address

slaac_address

Read-onlyIdempotent

IPv6 address a host builds for itself from a /64 prefix and a MAC (SLAAC, RFC 4862). The interface id is the modified EUI-64. The prefix must be exactly 64 bits and the low 64 bits of the prefix must be zero. Also returns the link-local address and the solicited-node multicast address. Text is RFC 5952. No zone index and no IPv4 tail. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/slaac-address

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": {
      "prefix": "<prefix>",
      "mac": "<mac>"
    },
    "name": "slaac_address"
  }
}

Input Schema

Name	Required	Description	Default
`mac`	Yes
`prefix`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

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 behavioral details: prefix constraints, modified EUI-64 construction, additional returned addresses, RFC 5952 formatting, no zone index or IPv4 tail, x402 pricing, and the equivalent HTTPS endpoint. This is unusually rich context for an agent deciding whether and how to call 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.

Conciseness5/5

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

The description is front-loaded with the core operation and then adds only relevant constraints, output notes, formatting, and payment/access information. Despite covering several points, the sentences are dense and none are filler.

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

Completeness4/5

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

With no output schema, the description usefully names the additional return values and formatting rules, and annotations already cover safety. It could be slightly more complete by specifying accepted MAC formats and error behavior, but it is sufficient for correct invocation in most cases.

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 description coverage is 0%, so the description carries the parameter burden; it explains that prefix must be exactly 64 bits with zero low 64 bits, and that MAC is used to build the modified EUI-64 interface ID. It does not specify the accepted MAC textual format, which is the main remaining gap.

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 precise resource and operation: deriving an IPv6 SLAAC address from a /64 prefix and MAC, with RFC 4862 and modified EUI-64 context. It also distinguishes the output from related sibling operations by noting that link-local and solicited-node multicast addresses are returned as well.

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?

The SLAAC/RFC 4862 context and prefix constraints imply when this tool is appropriate, but the description does not explicitly name alternatives such as eui64 or solicited_node or explain when to prefer this tool over them. Usage is inferable but not explicitly routed.

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?