ZBS Index What actually exists in applied AI, with the source next to it

mcp server

Verifly

Email verification for AI agents — verify, clean & validate emails; self-onboard + crypto pay

Description as published by the maintainer. Source

  • version 1.0.0
  • active

active — Most recent push to the repository was 2026-07-17.

What this server can do

17 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.

buy_credits(method, currency, package_id)
Start 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. Required: package_id.
check_domain_health(domain)
Check 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. Required: domain.
clean_email_list(emails, remove_disposable, exclude_role_accounts)
Clean 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. Required: emails.
extract_emails(text, lowercase, deduplicate)
Extract all email addresses found in a block of free-form text (notes, pasted documents, signatures). Optionally deduplicates and lowercases the results. Required: text.
get_account
Return 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.
get_credits
Return the API key's remaining verification credits and recent usage (today / this month) and plan. Costs no credits.
get_job_results(job_id)
Fetch 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. Required: job_id.
get_job_status(job_id)
Fetch 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. Required: job_id.
get_packages
List 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.
get_started
Call 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.
get_usage(limit, period)
Return 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.
list_jobs(limit, offset, status)
List 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.
register_account(email, password)
Programmatically 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. Required: email, password.
submit_bulk(emails, webhook_url)
Submit 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. Required: emails.
verify_batch(emails, exclude_role_accounts, exclude_public_domains)
Synchronously 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. Required: emails.
verify_email(email)
Verify 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. Required: email.
verify_email_demo(email)
Verify 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. Required: email.

Last successful function declaration observed on . Source: https://verifly.email/mcp. We list what the server declared; we do not call any of these functions.

Endpoint status observed on . Source: https://verifly.email/mcp.

Signals

These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.

Signal Value What it measures Window Observed Source
GitHub stars 0 Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. cumulative, all time GitHub
Last commit 2026-07-17 Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. point in time GitHub
Open issues 0 Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. as of fetch GitHub
Latest published version 1.0.0 Latest version string the maintainer published to the registry. as of fetch Model Context Protocol
Registry record last updated 2026-06-27 When the registry record was last updated by its maintainer. point in time Model Context Protocol
First listed in the MCP Registry 2026-06-27 Date this server was first published to the official MCP Registry. Not a usage or quality measure. point in time Model Context Protocol
repository status active The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. as of fetch GitHub
mcp tools declared 17 tools Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. as of probe verifly.email
mcp endpoint status ok The server listed 17 functions when asked. as of probe verifly.email

Where to get it

Related, by what their authors tagged them

  • LayerCall — last commit 2026-08-04, shares email-validation
    Score an IP, email, phone, domain or device for fraud in one call, with the signals behind it.
  • Courier — last commit 2026-06-13, shares email-verification
    Continuity protocol for autonomous AI agents. Agent messaging with SMTP bridge and LN payments.
  • io.github.Davison-Francis/deliveriq-mcp — last commit 2026-05-02, shares email-verification
    Email deliverability for AI agents. 12 tools: verify, DNSBL, DMARC, spam-trap, finder.

These share tags the maintainers applied themselves, such as email-validation, email-verification. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.

This is not a recommendation and not a test result. It is a map of what the authors said their work is about.

Also from james-sib

  • com.sibfly/ground-motion — last commit 2026-07-02
    Measured ground motion per US address (NASA InSAR). Self-register, $0.40/report, misses free.

How the author describes it

Topics the maintainer set on GitHub: ai-agent, email-validation, email-verification, llm-tools, mcp, model-context-protocol, verifly.

This record as data

Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.

GET /api/v1/entries/mcp_server.json

Sources

  1. james-sib/verifly-mcp-server on GitHub — GitHub, observed , trust tier 3.
  2. Official MCP Registry — Model Context Protocol, observed , trust tier 1.
  3. Tools declared by the MCP server at https://verifly.email/mcp — verifly.email, observed , trust tier 1.