ai.verifox/email-verifier
NPM · VERIFOX-MCP · 2 COMPONENTS · SCANNED SEP 21
Verify email deliverability & find business emails (single or bulk) via the Verifox API.
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 Security98
- 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 96 dependencies flagged as unhealthy. View diagnostics → Partial
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 60 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 544 tokens (~90/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
How do I install the ai.verifox/email-verifier MCP server?
ai.verifox/email-verifier runs locally as an npm package, launched with npx -y verifox-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 · verifox-mcp
claude mcp add ai-verifox-email-verifier -- npx -y verifox-mcp
{
"mcpServers": {
"ai-verifox-email-verifier": {
"command": "npx",
"args": [
"-y",
"verifox-mcp"
]
}
}
} {
"servers": {
"ai-verifox-email-verifier": {
"command": "npx",
"args": [
"-y",
"verifox-mcp"
]
}
}
} codex mcp add ai-verifox-email-verifier -- npx -y verifox-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-verifox-email-verifier": {
"type": "local",
"command": [
"npx",
"-y",
"verifox-mcp"
],
"enabled": true
}
}
} openclaw mcp add ai-verifox-email-verifier --command npx --arg -y --arg verifox-mcp
mcp_servers:
ai-verifox-email-verifier:
command: "npx"
args: ["-y", "verifox-mcp"] {
"McpServers": {
"ai-verifox-email-verifier": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"verifox-mcp"
]
}
}
} assistant mcp add ai-verifox-email-verifier -t stdio -c npx -a -y verifox-mcp
{
"mcpServers": {
"ai-verifox-email-verifier": {
"command": "npx",
"args": [
"-y",
"verifox-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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.80 functional
- 8 Sept 26 +1
- Stability: 0.97 → pass security
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 21 Sept 2026 · Analysed npm/verifox-mcp@1.2.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 →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| 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 →
find_email ~106
Find ONE person's business email from their name and company domain. Generates ~50 permutations and SMTP-verifies each, waits for the result, and returns the best match (or not_found). Charges 10 Fox Credits per find.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Company domain, e.g. stripe.com |
| first_name | string | yes | Person's first name |
| last_name | string | yes | Person's last name |
| middle_name | string | – | Optional middle name for more permutations |
No output schema declared.
No examples provided.
find_emails ~101
Bulk-find business emails for a LIST of contacts (name + company domain each). Submits the list, waits for completion, and returns the found email per contact. Up to 1000 contacts. Charges 10 Fox Credits per contact. Large lists that don't finish quickly return a jobId to poll with get_job.
| Name | Type | Req | Description |
|---|---|---|---|
| contacts | array | yes | Contacts to find emails for |
| wait | boolean | – | Wait for results in this call (default true) |
No output schema declared.
No examples provided.
get_credits ~60
Get the current Fox Credit balance for the Verifox account tied to the API key. Free — no credits charged. Use it to check remaining balance before a big verify/find run (verify = 1 credit/email, find = 10 credits/contact).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_job ~87
Check an async job started by verify_emails, find_email, or find_emails. Returns results if finished, otherwise the current status. Use the type shown in the submitting tool's response.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | Job ID from verify_emails / find_email / find_emails |
| type | string | yes | Job type: verify_bulk, find_single, or find_bulk |
No output schema declared.
No examples provided.
verify_email ~83
Verify whether ONE email address is deliverable. Checks syntax, MX, SMTP, catch-all, disposable, free-provider and role detection, and returns a 0-100 quality score. Charges 1 Fox Credit per uncached email.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email address to verify | |
| proxy | boolean | – | Use a SOCKS5 proxy for the SMTP check |
No output schema declared.
No examples provided.
verify_emails ~107
Bulk-verify a LIST of email addresses. Submits the whole list, waits for completion, and returns one result per email (same fields as verify_email). Best for cleaning lead lists. Charges 1 Fox Credit per email. Large lists that don't finish quickly return a jobId to poll with get_job.
| Name | Type | Req | Description |
|---|---|---|---|
| emails | array | yes | Email addresses to verify |
| wait | boolean | – | Wait for results in this call (default true). Set false to just get a jobId. |
No output schema declared.
No examples provided.
What is the ai.verifox/email-verifier MCP server?
ai.verifox/email-verifier is an MCP server listed in the public MCP registry as ai.verifox/email-verifier. Verify email deliverability & find business emails (single or bulk) via the Verifox API. This page covers its npm package (verifox-mcp).
Is the ai.verifox/email-verifier MCP server safe to use?
ai.verifox/email-verifier scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 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 ai.verifox/email-verifier MCP server expose?
ai.verifox/email-verifier exposes 6 tools: verify_email, verify_emails, find_email, find_emails, get_credits, get_job. Their descriptions and schemas cost roughly 544 tokens of context every time the server is loaded.
Is the ai.verifox/email-verifier MCP server still maintained?
ai.verifox/email-verifier is still listed as active in the MCP registry. We last reached this channel on 21 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 ai.verifox/email-verifier MCP server under?
ai.verifox/email-verifier declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.