Contact Verify (verify-x402)
NPM · CONTACT-VERIFY-MCP
Contact Verify (verify-x402). Basic $0.002, domain $0.02, sender $0.025.
Available components
Last scanned (14 hours ago)
Scores higher than 38% of npm servers
Category CRM and Sales
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 Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 112 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- 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 4 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
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.
- 21 Oct 26 +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.
- 19 Oct 26 +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.
- 18 Oct 26 0
- Stability: 0.00 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: pass → fail ▼ functional
- First check of Schema quality: unverified functional
- Package version: 1.0.0 → 1.1.0 functional
- 17 Oct 26 65
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 22 Oct 2026 · Analysed npm/contact-verify-mcp@1.1.0
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 →
Dependencies 112 packages
| Packages resolved | 112 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
lookup_phone Look up phone ~87
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.
| Name | Type | Req | Description |
|---|---|---|---|
| phone | string | yes | Phone number in E.164, for example +14155552671. Sent in the JSON body, not the URL. |
No output schema declared.
No examples provided.
preview_email Preview email ~98
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email address to preview. Sent in the JSON body, not the URL. |
No output schema declared.
No examples provided.
verify_domain Check domain ~153
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company_name | string | – | Optional legal name for the registration lookup. |
| compare_domain | string | – | Known domain to compare against. |
| domain | string | yes | Domain under test. |
| jurisdiction | string | – | Optional ISO 3166-1 alpha-2. |
| sender_email | string | – | Sender address. Sent in the JSON body, not the URL. |
No output schema declared.
No examples provided.
verify_email Verify email ~75
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email address to verify. Sent in the JSON body, not the URL. |
No output schema declared.
No examples provided.
verify_email_basic Basic email check ~85
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email address. Sent in the JSON body, not the URL. |
No output schema declared.
No examples provided.
verify_email_batch Verify email batch ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| emails | array | yes | 1 to 50 email addresses. Unique, well-formed addresses are billed at $0.01 each. |
No output schema declared.
No examples provided.
verify_sender Check sender ~115
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company_name | string | – | Optional legal name for the registration lookup. |
| compare_domain | string | – | Known domain to compare against. |
| string | yes | Email address. Sent in the JSON body, not the URL. | |
| jurisdiction | string | – | Optional ISO 3166-1 alpha-2. |
No output schema declared.
No examples provided.
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.
npm · contact-verify-mcp
claude mcp add dev-workers-okwithit9-verify-x402-contact-verify -- npx -y contact-verify-mcp
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.