Integration

Xverify integration

Xverify validates contact data one record at a time. An agent can verify an email address (deliverability, catch-all, risky or disposable domain, role account, typo correction), a U.S. or Canadian phone number (valid or not, line type, time zone, location), and a U.S. or Canadian postal address (deliverability, standardized fields, Zip+4, delivery flags), or all three in one call. Each query is counted against the account's paid query limit, and every call needs the domain registered in the Xverify settings. Authentication is the Xverify API key, sent as the api_key query parameter.

Connect Xverify How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Xverify.Built from the 4 Xverify tools below, on the connection you add once.

What you can do with Xverify

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Aio, 1 operation

verify_contactVerify contactGETVerifies an email address, a phone number and a postal address in one call; send any of them. Each one sent gets its own section (email, phone, address) in the answer.

Av, 1 operation

verify_addressVerify addressGETVerifies and standardizes one U.S. or Canadian postal address: deliverability status, reason, corrected fields, Zip+4 and delivery flags. Give zip, or city and state.

Ev, 1 operation

verify_emailVerify emailGETVerifies one email address: status (valid, invalid, accept_all, risky, unknown), reason, domain type, role account flag and a suggested correction for a typo.

Pv, 1 operation

verify_phoneVerify phoneGETVerifies one U.S. or Canadian phone number: status (valid or invalid), reason, line type (Landline, Cell, VOIP), use type, time zone and location.

Use Xverify from Claude Code, Cursor or Codex

Connect Xverify in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Xverify operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Xverify

Create your workspace
Sign up free. Nothing to install.
Connect Xverify once
Add your Xverify connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.