Integrating identity verification into MCP workflows

Identity verification is most valuable when it fits into a larger human or agent workflow. MCP lets assistants call the Finder or Probe without forcing users to reimplement transport, schema handling, or result semantics each time.

Why MCP matters here

The MCP surface mirrors the same two precision operations as the REST API. Keeping the surface narrow makes agent behavior easier to reason about and easier to price later.

When an agent calls identity_find, it gets back a structured result with state, outcome, and address. When it calls identity_probe, it gets the same shape. That consistency means the agent does not need to handle different response formats depending on which workflow ran.

If you want the Finder side of that flow in more detail, read How to find anyone's work email using the Finder API.

For teams building email verification into automated systems, this is a practical advantage. The agent can route deliverable results into a CRM, suppress undeliverable results, and preserve identity-provider or MX-host context when it is returned — all without custom integration logic.

The MCP tools

Relentless Identity exposes these MCP tools:

• identity_find — accepts a full name and company domain, returns the most likely work email identity. This is the email finder workflow for cases where the address is not yet known.
• identity_probe — accepts an exact email address, returns a deliverability verdict. This is the email verification workflow for cases where the mailbox is already known.
• Account usage helpers — inspect remaining capacity and usage history.
• Job scheduling — run finder or probe operations as background jobs with callback retrieval.

The tool surface is intentionally minimal. Each tool does one thing well. The agent decides which tool to call based on what it knows about the contact.

How teams use it

Sales ops enriching lead research

A common pattern is to let an agent gather context from a company website or CRM record, call identity_find to resolve a likely work identity, then call identity_probe only when the workflow requires direct verification on a specific address. See How to find anyone's work email using the Finder API for the full Finder workflow.

This two-step pattern — find, then verify — gives sales teams a verified email address without relying on guessed patterns or stale enrichment tables.

Security teams attaching identity checks to investigation playbooks

When a security team needs to verify whether an email address belongs to a real person at a target organization, the MCP integration lets them run that check directly inside their investigation workflow. The agent can call identity_probe on a suspicious address and get back an identity-level verdict.

Onboarding agents confirming professional domains

When a SaaS platform's onboarding agent needs to verify that a new user's work email corresponds to a real identity, it can call identity_find during signup. The result confirms whether the address maps to a valid work identity, reducing fraudulent account creation.

Data pipelines cleaning CRM identities

When a data pipeline needs to verify or enrich a batch of contacts, the MCP integration provides programmatic access to the same email finder and verification workflows. The agent can call identity_find for unknown addresses and identity_probe for known ones, then store the verified results.

Setting up MCP

The MCP integration works with Claude, Codex, OpenCode, and other MCP-compatible environments. See the MCP reference for installation instructions and configuration guidance.

For a broader context on how email verification fits into modern agent workflows, read Why SMTP verification is dead for precision outreach. If you want to try a single address first, use the free email verifier.