Sanctions Screening

Verifiable groundingFinance1 credit/callMCP
MCP toolsanctionscreening

Ground compliance agents in the authoritative OFAC SDN list so sanctions answers cite the current published list instead of a model's recollection.

Stop stale-number hallucinations

An agent asked about prices or rates will happily invent a figure. Enable Sanctions Screening and it calls the sanctionscreening tool to check the live number before it answers — so the reply rests on real data, not the model's memory.

Ground a research or trading assistant

Give a market assistant a source it can actually cite: every figure it reports carries Sanctions Screening as its origin, so a human can trace where the number came from.

Fresh at answer time

Because the model pulls sanctions screening at the moment it responds, the answer reflects the market now — not whatever was true when the model was trained.

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

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

  • query
  • matched
  • matchCount
  • verdict
  • topScore
  • results
  • list

Sanctions Screening, answered

How to ground an agent in it over MCP.

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

Ground your agents in Sanctions Screening. 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