MX Record

Verifiable groundingDomain Data5 credits/callMCP
MCP toolmxlookup

Ground agents in real-time MX records so email-routing and deliverability answers reflect live DNS truth, not stale lookups.

Ground security & research agents

Let an agent call MX Record to pull a domain's real records or health before it reasons about risk — verifiable signal instead of a confident guess.

Enrich a workflow with real records

Wire mxlookup into a compliance or research agent so each domain it evaluates is backed by live data it can cite.

Auditable lookups

Every record the agent uses carries MX Record as its origin, so findings are traceable.

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_••••" }
    }
  }
}
# “mxlookup” is now a tool your agent can call

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

  • domain
  • mx

MX Record, answered

How to ground an agent in it over MCP.

How do I give my agent MX Record?
Enable it on VerveContext and point your agent framework at the VerveContext MCP endpoint. MX Record then appears to the model as a tool named mxlookup, 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. MX Record is exposed as a standard tool, so nothing source-specific is required.
Can the agent cite MX Record?
Yes. MX Record is verifiable factual grounding — every value the agent pulls can carry MX Record as its source, so a person (or another system) can trace where the fact came from.
How many credits does a MX Record 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?
MX Record 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; MX Record is one of 300+ sources on the same key. Invoices and card statements show APIVERVE.

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

Scaling up?

Volume pricing, custom SLAs, and dedicated support for high-traffic teams.

Contact sales