ai.verifox/email-verifier
REMOTE · MCP.VERIFOX.AI · 2 COMPONENTS
Verify email deliverability & find business emails (single or bulk) via the Verifox API.
Available components
Last scanned (15 hours ago)
Scores higher than 74% of remote servers
Reachable. Last reached 21 Nov 2026.
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 554 tokens (~92/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Nov 26 0
- Stability: pass → 0.97 functional
- 31 Oct 26 0
- Tool “verify_email” rewrote its description, which is the text the model reads security
- Server version: 1.2.0 → 1.2.2 functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 Nov 2026 · Probed https://mcp.verifox.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=verifox.ai | CN=YE2,O=Let's Encrypt,C=US | 18 Nov 2026 | 16 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 6979f33d89394615453b27cbd091335b2bb |
| SANs: *.verifox.ai, verifox.ai | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.verifox.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814 | 8 | Verified |
| verifox.ai. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.verifox.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.verifox.ai/mcp | HTTPS enforced | 308 | https://mcp.verifox.ai/mcp |
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 ~93
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 check, including a repeat answered from the 24-hour result cache.
| 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.
How do I install the ai.verifox/email-verifier MCP server?
ai.verifox/email-verifier is a hosted endpoint at https://mcp.verifox.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.verifox.ai
claude mcp add --transport http ai-verifox-email-verifier 'https://mcp.verifox.ai/mcp'
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 hosted endpoint (https://mcp.verifox.ai/mcp).
Is the ai.verifox/email-verifier MCP server safe to use?
ai.verifox/email-verifier scores 79 out of 100 on VerifyMCP. 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 554 tokens of context every time the server is loaded.
Does the ai.verifox/email-verifier MCP server require authentication?
No. We connected to ai.verifox/email-verifier without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
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 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the ai.verifox/email-verifier MCP server?
VerifyMCP ran 12 checks on ai.verifox/email-verifier, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about ai.verifox/email-verifier: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.