Verdix address risk
NPM · VERDIX-MCP · SCANNED SEP 26
Check an EVM address on Base before sending funds: safe/caution/danger. Pays per call via x402.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security63
- No malware found by supply-chain analysis.Pass
- Known CVEs could not be checked: the version this server declares is not published in its registry.Unverified
- No install/post-install scripts declared.Pass
- Dependency health could not be checked: the version this server declares is not published in its registry.Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 324 tokens (~162/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the Verdix address risk MCP server?
Verdix address risk runs locally as an npm package, launched with npx -y verdix-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · verdix-mcp
claude mcp add com-verdixapi-verdix -- npx -y verdix-mcp
{
"mcpServers": {
"com-verdixapi-verdix": {
"command": "npx",
"args": [
"-y",
"verdix-mcp"
]
}
}
} {
"servers": {
"com-verdixapi-verdix": {
"command": "npx",
"args": [
"-y",
"verdix-mcp"
]
}
}
} codex mcp add com-verdixapi-verdix -- npx -y verdix-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-verdixapi-verdix": {
"type": "local",
"command": [
"npx",
"-y",
"verdix-mcp"
],
"enabled": true
}
}
} openclaw mcp add com-verdixapi-verdix --command npx --arg -y --arg verdix-mcp
mcp_servers:
com-verdixapi-verdix:
command: "npx"
args: ["-y", "verdix-mcp"] {
"McpServers": {
"com-verdixapi-verdix": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"verdix-mcp"
]
}
}
} assistant mcp add com-verdixapi-verdix -t stdio -c npx -a -y verdix-mcp
{
"mcpServers": {
"com-verdixapi-verdix": {
"command": "npx",
"args": [
"-y",
"verdix-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Sept 26 60
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 26 Sept 2026 · Analysed npm/verdix-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_address_risk Check an address before sending it funds ~262
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The EVM address to check (the recipient, contract or counterparty) |
| tier | string | – | Analysis depth and price: quick ($0.02), standard ($0.10), deep ($0.50) |
No output schema declared.
No examples provided.
get_pricing Verdix prices per tier ~62
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the Verdix address risk MCP server?
Verdix address risk is an MCP server listed in the public MCP registry as com.verdixapi/verdix. Check an EVM address on Base before sending funds: safe/caution/danger. Pays per call via x402. This page covers its npm package (verdix-mcp).
Is the Verdix address risk MCP server safe to use?
Verdix address risk scores 60 out of 100 on VerifyMCP. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Verdix address risk MCP server expose?
Verdix address risk exposes 2 tools: check_address_risk, get_pricing. Their descriptions and schemas cost roughly 324 tokens of context every time the server is loaded.
Is the Verdix address risk MCP server still maintained?
Verdix address risk is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Verdix address risk MCP server under?
Verdix address risk declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.