# Verdix address risk (npm · verdix-mcp)

Check an EVM address on Base before sending funds: safe/caution/danger. Pays per call via x402.

- Trust score: 60/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-26

## Components

- npm · `verdix-mcp`: 60/100 (this document), [markdown](https://verifymcp.io/servers/com-verdixapi-verdix/verdix-mcp.md), [page](https://verifymcp.io/servers/com-verdixapi-verdix/verdix-mcp)

## Channel facts

- Registry: `npm`
- Package: `verdix-mcp`
- Version: `0.1.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-26.

- **Supply Chain Security**: 63/100
  - No malware found by supply-chain analysis.
  - Known CVEs could not be checked: the version this server declares is not published in its registry.
  - No install/post-install scripts declared.
  - Dependency health could not be checked: the version this server declares is not published in its registry.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add com-verdixapi-verdix -- npx -y verdix-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "com-verdixapi-verdix": {
      "command": "npx",
      "args": [
        "-y",
        "verdix-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-verdixapi-verdix": {
      "command": "npx",
      "args": [
        "-y",
        "verdix-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-verdixapi-verdix -- npx -y verdix-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-verdixapi-verdix": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "verdix-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-verdixapi-verdix --command npx --arg -y --arg verdix-mcp
```

### Hermes

```yaml
mcp_servers:
  com-verdixapi-verdix:
    command: "npx"
    args: ["-y", "verdix-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-verdixapi-verdix": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "verdix-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-verdixapi-verdix -t stdio -c npx -a -y verdix-mcp
```

### Other

```json
{
  "mcpServers": {
    "com-verdixapi-verdix": {
      "command": "npx",
      "args": [
        "-y",
        "verdix-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-26 (score 60)

First indexed and scored.

## MCP tools (2)

### `check_address_risk` (~262 tokens)

Check an address before sending it funds

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.

Input parameters:

- `address` (string, required): 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)

### `get_pricing` (~62 tokens)

Verdix prices per tier

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.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/com-verdixapi-verdix/verdix-mcp#diagnostics

## Score history

- 2026-09-26: 60

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/verdix-mcp
- Socket report: https://socket.dev/npm/package/verdix-mcp
- Repository: https://github.com/verdixapi/verdix-mcp
- Website: https://api.verdixapi.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-verdixapi-verdix/verdix-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-verdixapi-verdix/verdix-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-verdixapi-verdix/verdix-mcp