Verdix address risk

What Verdix address risk does

Verdix address risk checks an EVM address on Base before funds are sent. Its result uses three risk categories: safe, caution, or danger. The service is intended for workflows where an agent or application needs to assess a destination address before proceeding with a transfer.

The Verdix address risk MCP server is relevant to Base-based payment and treasury workflows that need an address check before sending funds. The available description does not specify whether the service supports chains other than Base, so its documented scope should be treated as Base only.

How it works

A client sends an EVM address for checking through the Verdix API. The service evaluates the address and returns one of the documented classifications: safe, caution, or danger. The available material does not describe the underlying signals, scoring rules, response schema, or whether additional address metadata is returned.

Each call is paid through x402. Applications using the Verdix address risk MCP server therefore need to account for payment on a per-call basis. The provided information does not define pricing, payment credentials, supported wallets, or how failed payments are reported.

Tools and capabilities

The documented capability is an address-risk check for Base:

• Check an EVM address before sending funds.
• Receive a safe, caution, or danger result.
• Pay for each call through x402.

No other tools, mutation operations, chain coverage, batch checks, or monitoring functions are described in the available material. Developers should not assume that the server can send funds or block transactions; the documented function is checking an address before a transfer.

Limitations and notes

The README is unavailable, so setup commands, MCP transport details, client compatibility, authentication requirements, environment variables, and request examples cannot be confirmed. The source supplied for this listing is the Verdix API address, but the available description does not explain how to configure an MCP client to use it.

The result labels indicate broad risk categories, not a documented guarantee that a transfer is safe. A calling application should decide how to handle each category. The available material does not define recommended actions for safe, caution, or danger results, nor does it state how current or comprehensive the checks are.

Before adopting the Verdix address risk MCP server, verify the installation method, x402 payment flow, supported MCP transport, response format, and Base address requirements from the service documentation.