_ registry / mcp http-sse · checked 5h ago

verifly-mcp-server

https://verifly.email

Registry code: 4ddf7890741dd1dd

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://verifly.email/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
341ms

last good check

priced tools
0

of 17 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 17 tools
1 open2 auth-required 14 never probed 3 of 17 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_started open 5h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • get_account auth-required 5h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • get_packages auth-required 5h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • check_domain_health unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "description": "Domain to check, e.g. example.com"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • get_credits unknown never probed

    Return the API key's remaining verification credits and recent usage (today / this month) and plan. Costs no credits.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • verify_email_demo unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "email"
  ],
  "properties": {
    "email": {
      "type": "string",
      "description": "The email address to verify, e.g. [email protected]"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • verify_email unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "email"
  ],
  "properties": {
    "email": {
      "type": "string",
      "description": "The email address to verify, e.g. [email protected]"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • verify_batch unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "emails"
  ],
  "properties": {
    "emails": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "minItems": 1,
      "description": "Array of email addresses to verify."
    },
    "exclude_role_accounts": {
      "type": "boolean",
      "description": "Flag/exclude role accounts (info@, sales@, ...). Default false."
    },
    "exclude_public_domains": {
      "type": "boolean",
      "description": "Flag/exclude public domains (gmail.com, ...). Default false."
    }
  },
  "additionalProperties": false
}
    arguments 26 lines
  • clean_email_list unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "emails"
  ],
  "properties": {
    "emails": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "minItems": 1,
      "description": "Email addresses to clean."
    },
    "remove_disposable": {
      "type": "boolean",
      "description": "Remove disposable/throwaway addresses. Default true."
    },
    "exclude_role_accounts": {
      "type": "boolean",
      "description": "Remove role accounts (info@, support@, ...). Default false."
    }
  },
  "additionalProperties": false
}
    arguments 26 lines
  • extract_emails unknown never probed

    Extract all email addresses found in a block of free-form text (notes, pasted documents, signatures). Optionally deduplicates and lowercases the results.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "text"
  ],
  "properties": {
    "text": {
      "type": "string",
      "description": "Free-form text to scan for email addresses."
    },
    "lowercase": {
      "type": "boolean",
      "description": "Lowercase all extracted addresses. Default true."
    },
    "deduplicate": {
      "type": "boolean",
      "description": "Remove duplicate addresses. Default true."
    }
  },
  "additionalProperties": false
}
    arguments 22 lines
  • submit_bulk unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "emails"
  ],
  "properties": {
    "emails": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "minItems": 1,
      "description": "Email addresses to verify in this job (deduped server-side)."
    },
    "webhook_url": {
      "type": "string",
      "description": "Optional public HTTPS URL to POST a job.completed notification to."
    }
  },
  "additionalProperties": false
}
    arguments 22 lines
  • get_job_status unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "job_id"
  ],
  "properties": {
    "job_id": {
      "type": "string",
      "description": "The job_id returned by submit_bulk."
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • get_job_results unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "job_id"
  ],
  "properties": {
    "job_id": {
      "type": "string",
      "description": "The job_id returned by submit_bulk."
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • list_jobs unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "limit": {
      "type": "integer",
      "description": "Max jobs to return (1-100, default 50)."
    },
    "offset": {
      "type": "integer",
      "description": "Pagination offset (default 0)."
    },
    "status": {
      "enum": [
        "pending",
        "processing",
        "completed",
        "failed"
      ],
      "type": "string",
      "description": "Only return jobs in this status."
    }
  },
  "additionalProperties": false
}
    arguments 25 lines
  • get_usage unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "limit": {
      "type": "integer",
      "description": "Max recent log entries to include (default 100, max 1000)."
    },
    "period": {
      "enum": [
        "day",
        "week",
        "month"
      ],
      "type": "string",
      "description": "Reporting period. Default 'month'."
    }
  },
  "additionalProperties": false
}
    arguments 20 lines
  • buy_credits unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "package_id"
  ],
  "properties": {
    "method": {
      "enum": [
        "stripe",
        "crypto"
      ],
      "type": "string",
      "description": "Payment method. 'stripe' = card link (needs a human), 'crypto' = wallet-payable invoice. Default 'stripe'."
    },
    "currency": {
      "enum": [
        "BTC",
        "ETH",
        "LTC",
        "USDT",
        "USDC"
      ],
      "type": "string",
      "description": "For method 'crypto': the coin to pay in; returns a raw wallet address an agent can pay autonomously."
    },
    "package_id": {
      "type": "string",
      "description": "The package id to buy (from get_packages)."
    }
  },
  "additionalProperties": false
}
    arguments 33 lines
  • register_account unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "email",
    "password"
  ],
  "properties": {
    "email": {
      "type": "string",
      "description": "Email for the new account (not a disposable domain)."
    },
    "password": {
      "type": "string",
      "minLength": 8,
      "description": "Password for the new account (minimum 8 characters)."
    }
  },
  "additionalProperties": false
}
    arguments 20 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/4ddf7890741dd1dd/badge.svg)](https://brick.blue/agent/4ddf7890741dd1dd)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.