verdix
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VERDIX_API_URL | No | Only for testing against another deployment. | https://api.verdixapi.com |
| EVM_PRIVATE_KEY | No | Alternative to VERDIX_PRIVATE_KEY, also accepted. | |
| VERDIX_PRIVATE_KEY | No | Your Base wallet's private key (hex). Required to use check_address_risk. | |
| VERDIX_MAX_PRICE_USD | No | Most one call may cost, in USD. | 0.10 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_address_riskA | Screen an EVM address on Base before sending it money or interacting with it. Returns Verdix's verdict JSON unchanged: verdict (safe | caution | danger), risk_score (0-100), reasons, checked, tier, price_usd, as_of. 'danger' means sanctioned, a known scam/exploit/phishing address, an address-poisoning lookalike, a burn address or similar - do not send funds. 'caution' means not enough evidence to call it safe (new, unverified, or a data source was unavailable) - confirm with the user first. PAID: each call costs USDC on Base via x402, paid from the wallet configured in this server (VERDIX_PRIVATE_KEY), never more than VERDIX_MAX_PRICE_USD. Tiers: quick ($0.02), standard ($0.10, default), deep ($0.50); call get_pricing for current prices. A 503 answer (data unavailable) is not charged. |
| get_pricingA | Free. Current Verdix price per tier (USDC on Base, via x402), the payment recipient, your configured max price per call, and whether a wallet is configured (with its public address, so it can be funded). Nothing is signed or paid. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools serve completely distinct purposes: one performs the core risk screening action, the other provides pricing information. There is no overlap or ambiguity in their functions.
Both tool names follow the consistent verb_noun pattern with lowercase and underscores (check_address_risk, get_pricing). The naming is clear and predictable.
With only 2 tools, the surface is on the thin side, but it matches the narrow scope of the server, which focuses on address risk screening and its associated pricing. The count is borderline but not unreasonable.
The server covers the core operation of checking address risk and provides a necessary auxiliary tool for pricing. While there are no tools for bulk checks or history, the primary use case is fully addressed, leaving only minor gaps.