# Verifly

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

- name: email.verifly/verifly
- version: 1.0.0
- connection class: R1 (autonomous)
- trust: 89/100
- quality: 80/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/email.verifly%2Fverifly
- tools: https://api.protogrid.dev/v1/servers/email.verifly%2Fverifly/tools

**An agent can connect on its own if it already holds `VERIFLY_TOKEN`.** Remote endpoint behind a static API key or header. The registry never sees the value; the agent fills the placeholder.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "verifly": {
      "type": "http",
      "url": "https://verifly.email/mcp",
      "headers": {
        "Authorization": "Bearer ${VERIFLY_TOKEN}"
      }
    }
  }
}
```

Placeholders to fill: `${VERIFLY_TOKEN}`.

## Trust

- hygiene: 100
- liveness: 100
- freshness: 65
- provenance: 85
- drivers: +repository +dns-namespace +website +reachable +uptime-100% ~updated-115d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 80/100 (good)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 86 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 17 of 17 tools declare readOnlyHint or destructiveHint
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: get_started (idempotentHint); verify_email (idempotentHint); verify_email_demo (idempotentHint); …
- pass `tools.token_cost`: about 2,870 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 75 (weight 15)

- warn `stability.changes`: 17 tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 17, about 2,870 tokens to load them all
- tool set hash: 728184c4a715a2e0bd67e9b6c97fb594
- tools last changed: 2026-10-01T06:27:06.437Z
- badge: [![protogrid quality](https://protogrid.dev/badge/email.verifly/verifly.svg)](https://protogrid.dev/servers/email.verifly/verifly)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-01 `register_account` changed (annotations)
- 2026-10-01 `buy_credits` changed (annotations)
- 2026-10-01 `get_packages` changed (annotations)
- 2026-10-01 `get_account` changed (annotations)
- 2026-10-01 `get_usage` changed (annotations)
- 2026-10-01 `list_jobs` changed (annotations)
- 2026-10-01 `get_job_results` changed (annotations)
- 2026-10-01 `get_job_status` changed (annotations)
- 2026-10-01 `submit_bulk` changed (annotations)
- 2026-10-01 `get_credits` changed (annotations)

Full history: https://api.protogrid.dev/v1/servers/email.verifly%2Fverifly/changes

## Remotes

- https://verifly.email/mcp (streamable-http, auth api_key ${VERIFLY_TOKEN}, reachable true, uptime30d 1)

## Packages

_none_

## Tools (17)

- `buy_credits`: 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.
- `check_domain_health`: 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.
- `clean_email_list`: 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.
- `extract_emails`: Extract all email addresses found in a block of free-form text (notes, pasted documents, signatures). Optionally deduplicates and lowercases the results.
- `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`: 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.
- `get_job_status`: 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.
- `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`: 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`: 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`: 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.
- `submit_bulk`: 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.
- `verify_batch`: 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.
- `verify_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.
- `verify_email_demo`: 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.