---
ref: tool:anymailfinder/verify-email
name: Verify an email address
company: company:anymailfinder
workflows: []
access: [mcp, api]
tags: [capability:verify-emails, category:data-provider, has:api, has:mcp]
docs: https://anymailfinder.com/email-finder-api/docs/verify-email
updated: 2026-11-07
---

# Verify an email address

Checks whether an email address exists and can receive mail, catch-all domains included, and returns valid, invalid or risky with the domain's mail provider.

Note: Costs 0.2 credits whatever the result. Emails returned by the find calls are already verified and don't need this.

## Set up

Use the first option your agent supports.

### MCP (official, remote)

Add this server to your agent's MCP settings, then sign in when asked.

```json
{ "mcpServers": { "anymailfinder": { "url": "https://api.anymailfinder.com/mcp" } } }
```

Call the MCP tool `verify_email`.

Server URL: https://api.anymailfinder.com/mcp

### API (official)

- Base URL: https://api.anymailfinder.com/v5.1
- Endpoint: `POST /verify-email`
- Auth: send the header `Authorization: $ANYMAILFINDER_API_KEY`
- Get a key: https://app.anymailfinder.com/settings/api
- Docs: https://anymailfinder.com/email-finder-api/docs

Note: The key goes in Authorization as is, with no Bearer prefix. Searches can take up to 3 minutes; wait for the response instead of retrying. A 402 means the account is out of credits.

Before anything else, confirm access with the cheapest read-only call, like a list or a search. Never send or change anything to test access.

## Rules

- Ask the user before anything that sends messages, costs money, or changes data, and say how many records it touches. One approval covers a batch the user has seen.
- Never print API keys.