Verifly
email.verifly/veriflyVersion 1.0.0Email verification for AI agents — verify, clean & validate emails; self-onboard + crypto pay
Status
Responds371 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 14:29 UTC
- Latency
- 371 ms
- Remotes responding
- 1 of 1
- Sign-in
- API key
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 22:14 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://verifly.email/mcpResponds371 msNo sign-in
Claude Code
claude mcp add --transport http verifly https://verifly.email/mcp --header 'Authorization: Bearer <YOUR_TOKEN>'Replace <YOUR_TOKEN> before running.
Claude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: verifly
Remote MCP server URL: https://verifly.email/mcp
This server expects the header Authorization.Cursor
{
"mcpServers": {
"verifly": {
"url": "https://verifly.email/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}Replace <YOUR_TOKEN> before running.
VS Code
code --add-mcp '{"name":"verifly","type":"http","url":"https://verifly.email/mcp","headers":{"Authorization":"Bearer <YOUR_TOKEN>"}}'Replace <YOUR_TOKEN> before running.
Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
17 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
buy_creditsStart a purchase of a credit package and return a way to pay. This does NOT complete a payment by itself — it returns a payment link / address:
• method 'stripe' → returns a checkout_url. Paying by card requires a HUMAN to open that link and enter card details; an agent cannot finish a card payment on its own.
• method 'crypto' → returns a Plisio invoice with a checkout_url AND, when you pass a `currency` (BTC, ETH, LTC, USDT, USDC), a RAW wallet `address` + `amount`. An autonomous agent CAN pay this from a crypto wallet with no browser/human, then credits are added automatically once the payment confirms. Prefer crypto for fully autonomous top-ups. Get a package id from get_packages first. | No | No | Not declared | Yes |
check_domain_healthCheck the DNS and deliverability health of an email domain: MX records, SPF, DMARC, and an overall health score. Useful for diagnosing why a domain bounces or for validating a sending domain. | No | Yes | Not declared | Yes |
clean_email_listClean a list of email addresses before an import or campaign: dedupes, removes invalid syntax, and (optionally) strips disposable and role accounts. Returns the cleaned list plus a summary of what was removed. | No | Yes | Not declared | No |
extract_emailsExtract all email addresses found in a block of free-form text (notes, pasted documents, signatures). Optionally deduplicates and lowercases the results. | No | Yes | Not declared | No |
get_accountReturn the account profile for the current API key: email, name, company, timezone, remaining credits, total credits used, number of API keys, and plan. Costs no credits. | No | Yes | Not declared | No |
get_creditsReturn the API key's remaining verification credits and recent usage (today / this month) and plan. Costs no credits. | No | Yes | Not declared | No |
get_job_resultsFetch the full per-address results of a completed bulk verification job by job_id (each email's verdict, recommendation, and reason) plus the valid/invalid/risky summary and credits used. The job must be 'completed' — check get_job_status first. | No | Yes | Not declared | No |
get_job_statusFetch the current status and progress of a bulk verification job by its job_id (status, percent progress, processed count, and a valid/invalid/risky summary). Poll this after submit_bulk until status is 'completed', then call get_job_results. | No | Yes | Not declared | No |
get_packagesList the credit packages available for purchase (id, name, credit amount, price in USD, and price per 1k credits). Use the returned package id with buy_credits. | No | Yes | Not declared | No |
get_startedCall this FIRST if you have no Verifly API key. Returns how Verifly works and how to get access with no human: pay-as-you-go email verification API, 100 free credits on self-registration, no monthly fee. No API key required to call this tool. | No | Yes | Not declared | No |
get_usageReturn detailed usage statistics for the account over a period (day, week, or month): total credits used, emails processed, request counts broken down by endpoint and source, a daily breakdown, and recent activity. | No | Yes | Not declared | No |
list_jobsList the account's bulk verification jobs, most recent first, with their status, progress, and summary. Optionally filter by status and paginate. Use this to find past jobs and their job_ids. | No | Yes | Not declared | No |
register_accountProgrammatically create a brand-new Verifly account — this is how an agent self-onboards with no human in the loop. Requires only an email and a password (min 8 chars; disposable email domains are rejected). The new account starts with free credits. The response includes the new account id/email and a freshly generated `api_key.key` that is shown ONCE — capture and store it immediately, it cannot be retrieved again. Subsequent tool calls can then use that key as the bearer token. | No | No | Not declared | No |
submit_bulkSubmit a list of email addresses as an asynchronous bulk verification job — the right tool for large lists. Returns immediately with a job_id, status, and the check_status_url / results_url to poll. Small lists may complete inline (status 'completed'); larger ones return status 'pending' — poll get_job_status until it is 'completed', then call get_job_results. Optionally register a webhook_url (public HTTPS) to be notified when the job finishes. | No | No | Not declared | Yes |
verify_batchSynchronously verify a list of email addresses (best for up to a few hundred). Returns a per-address verdict for each email. For very large lists use the bulk async endpoint instead. | No | Yes | Not declared | Yes |
verify_emailVerify one email address in real time. Returns a deliverability verdict (valid / invalid / risky / unknown), the reason, detailed flags (disposable, role account, catch-all, MX, SMTP), a send/reject recommendation, and credit usage. | No | Yes | Not declared | Yes |
verify_email_demoVerify one email address with NO account or API key, so you can evaluate Verifly before registering. Rate-limited per IP (a few checks). Returns the same deliverability verdict and flags as the full API. For real volume, call register_account for a key + 100 free credits, then use verify_email. | No | Yes | Not declared | Yes |
Details
- Registry status
- Active
- Published
- Jun 27, 2026
- Updated
- Jun 27, 2026
- Categories (suggested)
- SecurityFinance and paymentsSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared