crypto_address_validate
Offline validator and chain detector for up to 50 crypto addresses: EVM (EIP-55 checksum, returns the checksummed form), Bitcoin (P2PKH, P2SH, SegWit v0 bech32, Taproot bech32m, testnet), Solana (32-byte base58, wallet vs program-derived/off-curve), Tron, XRP, Litecoin, Dogecoin, Dash and Cosmos-...
This record as markdown: /tools/com-it-scorptech-x402/crypto-address-validate.md
What crypto_address_validate does on ScorpTech x402 API
AI agents call crypto_address_validate to retrieve information from ScorpTech x402 API without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
chain | string | — | Expected chain; addresses valid only for another chain are reported invalid with the detected chain |
addresses | array | Yes | Addresses to check, comma list or JSON array, max 50 |
Parameters from the server's own tool schema.
Why crypto_address_validate is rated Low
Even though crypto_address_validate only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs crypto_address_validate safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScorpTech x402 API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crypto_address_validate, this is the rule to start with:
crypto_address_validate is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ScorpTech x402 API, apply this rule, and every crypto_address_validate call is checked against it from then on.
Questions about crypto_address_validate
Offline validator and chain detector for up to 50 crypto addresses: EVM (EIP-55 checksum, returns the checksummed form), Bitcoin (P2PKH, P2SH, SegWit v0 bech32, Taproot bech32m, testnet), Solana (32-byte base58, wallet vs program-derived/off-curve), Tron, XRP, Litecoin, Dogecoin, Dash and Cosmos-SDK bech32 chains. Catches typos via checksums before an agent sends funds. No network calls. Price: $0.002 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/crypto-address-validate. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.
crypto_address_validate accepts 2 parameters: chain, addresses. Required: addresses. The full parameter table on this page comes from the server's own tool schema.
Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for crypto_address_validate: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches ScorpTech x402 API. Nothing to install.
crypto_address_validate is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the crypto_address_validate rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for crypto_address_validate. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
crypto_address_validate is provided by the ScorpTech x402 API MCP server (https://scorptech.it.com/api/x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScorpTech x402 API, and thousands of servers like it.
This server
Across the catalogue