Email Verification

What it grounds

Ground agents in verifiable email validity — format, MX and mailbox checks — so contact decisions rest on real deliverability, not assumptions.

Ways to ground with it

Check before you act

Let an agent call Email Verification to confirm an input is real and safe before it writes a record, sends a message, or completes a task — grounding the decision in a verifiable check.

Guardrail an automated workflow

Wire emailvalidator into an agent pipeline so risky inputs are flagged and traced, not passed through on the model's hunch.

Auditable validation

Each verdict the agent relies on carries Email Verification as its source, so a reviewer can see exactly what was checked.

Connect over MCP

Point your agent framework at the VerveContext endpoint. Every enabled source — this one included — becomes a tool the model can call. No per-source plumbing.

context.json

{
  "mcpServers": {
    "vervecontext": {
      "url": "https://api.vervecontext.com/v1/mcp",
      "headers": { "x-api-key": "vc_live_••••" }
    }
  }
}

# “emailvalidator” is now a tool your agent can call

Facts your agent can cite

Each call returns structured fields your agent can read — and trace back to this source.

creationDate
domain
email
username
canConnect
hasTypo
isValid
isMxValid

Email Verification, answered

How to ground an agent in it over MCP.

How do I give my agent Email Verification?

Enable it on VerveContext and point your agent framework at the VerveContext MCP endpoint. Email Verification then appears to the model as a tool named emailvalidator, which it calls when a task needs it — no per-source plumbing.

Which agents and frameworks can use it?

Any MCP client — Claude, Cursor, LangChain, and custom agents all speak the Model Context Protocol. Email Verification is exposed as a standard tool, so nothing source-specific is required.

Can the agent cite Email Verification?

Yes. Email Verification is verifiable factual grounding — every value the agent pulls can carry Email Verification as its source, so a person (or another system) can trace where the fact came from.

How many credits does a Email Verification call cost?

Each call costs 5 credits. Scoped keys let you grant an agent only the sources it should reach, and usage logs show exactly what was pulled to ground each answer.

How current is the data?

Email Verification is served live from APIVerve's production data engine and pulled at the moment the agent calls it, so answers reflect the world now rather than the model's training cutoff.

Where does the data come from, and what shows on my bill?

VerveContext runs on APIVerve, our production data engine; Email Verification is one of 300+ sources on the same key. Invoices and card statements show APIVERVE.

Ground alongside

Browse all sources

Check before you act

Guardrail an automated workflow

Auditable validation

Email Verification, answered

Ground your agents in Email Verification. Connect over MCP, enable the source, and every answer carries its receipts.

Scaling up?