# Contact Verify (verify-x402) (npm · contact-verify-mcp)

Contact Verify (verify-x402). Basic $0.002, domain $0.02, sender $0.025.

- Trust score: 67/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-22

## Components

- npm · `contact-verify-mcp`: 67/100 (this document), [markdown](https://verifymcp.io/servers/dev-workers-okwithit9-verify-x402-contact-verify/contact-verify-mcp.md), [page](https://verifymcp.io/servers/dev-workers-okwithit9-verify-x402-contact-verify/contact-verify-mcp)

## Channel facts

- Registry: `npm`
- Package: `contact-verify-mcp`
- Version: `1.1.0`
- 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-10-22.

- **Supply Chain Security**: 99/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 112 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 852 tokens (~121/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 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.

## Install

### How do I install the Contact Verify (verify-x402) MCP server?

Contact Verify (verify-x402) runs locally as an npm package, launched with npx -y contact-verify-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 dev-workers-okwithit9-verify-x402-contact-verify -- npx -y contact-verify-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "dev-workers-okwithit9-verify-x402-contact-verify": {
      "command": "npx",
      "args": [
        "-y",
        "contact-verify-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-workers-okwithit9-verify-x402-contact-verify": {
      "command": "npx",
      "args": [
        "-y",
        "contact-verify-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add dev-workers-okwithit9-verify-x402-contact-verify -- npx -y contact-verify-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-workers-okwithit9-verify-x402-contact-verify": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "contact-verify-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-workers-okwithit9-verify-x402-contact-verify --command npx --arg -y --arg contact-verify-mcp
```

### Hermes

```yaml
mcp_servers:
  dev-workers-okwithit9-verify-x402-contact-verify:
    command: "npx"
    args: ["-y", "contact-verify-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "dev-workers-okwithit9-verify-x402-contact-verify": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "contact-verify-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-workers-okwithit9-verify-x402-contact-verify -t stdio -c npx -a -y contact-verify-mcp
```

### Other

```json
{
  "mcpServers": {
    "dev-workers-okwithit9-verify-x402-contact-verify": {
      "command": "npx",
      "args": [
        "-y",
        "contact-verify-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-10-21 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-19 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-18 (score 65, 0)

- [security regression] Stability: 0.00 → unverified
- [security regression] Tool safety: pass → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Schema quality: pass → fail
- [functional] First check of Schema quality: unverified
- [functional] Package version: 1.0.0 → 1.1.0

### 2026-10-17 (score 65)

First indexed and scored.

## MCP tools (7)

### `verify_email` (~75 tokens)

Verify email

Contact Verify (verify-x402) full mailbox check. Deliverability, catch-all, disposable, and role-account signals. Costs $0.01 USDC on Base mainnet, paid automatically from the EVM_PRIVATE_KEY wallet.

Input parameters:

- `email` (string, required): Email address to verify. Sent in the JSON body, not the URL.

### `verify_email_basic` (~85 tokens)

Basic email check

Contact Verify (verify-x402) basic check. Costs $0.002 USDC on Base mainnet for format plus mail server (syntax, MX, disposable, free-email, and role account). It does not check the mailbox. Paid automatically from the EVM_PRIVATE_KEY wallet.

Input parameters:

- `email` (string, required): Email address. Sent in the JSON body, not the URL.

### `verify_email_batch` (~101 tokens)

Verify email batch

Verify up to 50 email addresses in one call. Costs $0.01 USDC per unique, well-formed address on Base mainnet, paid automatically from the EVM_PRIVATE_KEY wallet. Invalid syntax is not billed. A failed check for one address comes back as unknown and does not fail the batch.

Input parameters:

- `emails` (array, required): 1 to 50 email addresses. Unique, well-formed addresses are billed at $0.01 each.

### `preview_email` (~98 tokens)

Preview email

Contact Verify (verify-x402) preview is free ($0.00). Checks syntax, MX, disposable-domain status, and role-account status. It does not check the mailbox and does not spend from the wallet. Basic is $0.002. The full mailbox check is $0.01. The address is sent in a JSON body.

Input parameters:

- `email` (string, required): Email address to preview. Sent in the JSON body, not the URL.

### `verify_domain` (~153 tokens)

Check domain

Contact Verify (verify-x402) domain check. Domain age, lookalike detection, MX, website, business-registry match, and SPF/DMARC. Costs $0.02 USDC on Base mainnet, paid automatically from the EVM_PRIVATE_KEY wallet. A sender address is posted as JSON and is not put in the URL.

Input parameters:

- `company_name` (string): Optional legal name for the registration lookup.
- `compare_domain` (string): Known domain to compare against.
- `domain` (string, required): Domain under test.
- `jurisdiction` (string): Optional ISO 3166-1 alpha-2.
- `sender_email` (string): Sender address. Sent in the JSON body, not the URL.

### `verify_sender` (~115 tokens)

Check sender

Contact Verify (verify-x402) sender check. Email deliverability plus the domain check in one call. Costs $0.025 USDC on Base mainnet, paid automatically from the EVM_PRIVATE_KEY wallet.

Input parameters:

- `company_name` (string): Optional legal name for the registration lookup.
- `compare_domain` (string): Known domain to compare against.
- `email` (string, required): Email address. Sent in the JSON body, not the URL.
- `jurisdiction` (string): Optional ISO 3166-1 alpha-2.

### `lookup_phone` (~87 tokens)

Look up phone

Look up the carrier line type of one E.164 phone number (mobile, landline, VoIP, or toll-free). Costs $0.02 USDC on Base mainnet, paid automatically from the EVM_PRIVATE_KEY wallet.

Input parameters:

- `phone` (string, required): Phone number in E.164, for example +14155552671. Sent in the JSON body, not the URL.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/dev-workers-okwithit9-verify-x402-contact-verify/contact-verify-mcp#diagnostics

## Score history

- 2026-10-22: 67
- 2026-10-21: 67
- 2026-10-20: 66
- 2026-10-19: 66
- 2026-10-18: 65
- 2026-10-17: 65

## Common questions

### What is the Contact Verify (verify-x402) MCP server?

Contact Verify (verify-x402) is an MCP server listed in the public MCP registry as dev.workers.okwithit9.verify-x402/contact-verify. Contact Verify (verify-x402). Basic $0.002, domain $0.02, sender $0.025. This page covers its npm package (contact-verify-mcp).

### Is the Contact Verify (verify-x402) MCP server safe to use?

Contact Verify (verify-x402) scores 67 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 October 2026. 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 Contact Verify (verify-x402) MCP server expose?

Contact Verify (verify-x402) exposes 7 tools: verify_email, verify_email_basic, verify_email_batch, preview_email, verify_domain, and 2 more. Their descriptions and schemas cost roughly 714 tokens of context every time the server is loaded.

### Is the Contact Verify (verify-x402) MCP server still maintained?

Contact Verify (verify-x402) is still listed as active in the MCP registry. We last reached this channel on 22 October 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 Contact Verify (verify-x402) MCP server under?

Contact Verify (verify-x402) 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/contact-verify-mcp
- Socket report: https://socket.dev/npm/package/contact-verify-mcp
- Website: https://verify-x402.okwithit9.workers.dev/mcp
- Changelog RSS feed: https://verifymcp.io/servers/dev-workers-okwithit9-verify-x402-contact-verify/contact-verify-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-workers-okwithit9-verify-x402-contact-verify/contact-verify-mcp.json
- HTML version of this page: https://verifymcp.io/servers/dev-workers-okwithit9-verify-x402-contact-verify/contact-verify-mcp