VerityVerity
Book a Demo

One tool call between an answer and its sources.

Verity MCP puts a source-checking tool inside the assistants your team already runs. The assistant calls it mid-answer and comes back with what held up, what did not and the passage behind every citation.

Book a demo

What comes back from one call.

Who disagrees

  • Disputing sources counted, not buried
  • Support and dispute on every answer
  • The split arrives in the reply

Citations that open

  • Every citation resolves to its passage
  • Verifying a claim is one click
  • No second research project

Sources, not echoes

  • Copies and syndication count once
  • Same-owner repeats fold into one voice
  • Over a billion passages behind it

Your stack unchanged

  • Your model and your prompts stay
  • Works with any MCP client
  • One entry in tool settings

Safe to switch on

  • Nothing you send trains a model
  • Per-query audit trail
  • Answers respect existing permissions

The check runs where the work already happens.

Nobody switches tools or opens a second tab. When a question turns on evidence, the assistant calls Verity, and the reply carries the sources behind it plus the ones that argue the other way.

Which of our vendors are SOC 2 Type II certified?
searchgrounded
{ query: "SOC 2 Type II vendors",
  index: "both" }
Two active vendors hold current SOC 2 Type II certification: CloudScale[ 1 ] and Northwind Logistics[ 2 ].
  • [ 1 ] vendor-security-addendum.pdf p.4
  • [ 2 ] supplier-risk-register.pdf p.12
Illustrative composition. The live tool runs on your question.
  1. 1

    Search

    Your question runs against the full index.

  2. 2

    Collapse

    Duplicates and syndication fold into one source each.

  3. 3

    Count

    Every source lands as support, dispute or silence.

  4. 4

    Answer

    Built from what held up, with the passage behind every claim.

  5. 5

    Verify

    The finished answer is checked claim by claim before the assistant replies.

What happens when the assistant calls.

Five steps run between the tool call and the reply. No answer skips the check.

Set it up once.

Three steps and the tools appear in your assistant. Any client that speaks MCP over HTTP can call them.

  1. 1

    Create a key

    Sign in to the admin console at admin.veritylabs.io and create an API key for your organization.

  2. 2

    Add the server

    Add https://api.veritylabs.io/mcp as a remote MCP server in your client and send the key as Authorization: Bearer.

  3. 3

    Call the tools

    search returns numbered passages and a retrieval_id, verify checks text against that evidence and search_templates lists the Spaces and agents the key can use.

POST /mcp
tools/list
$ curl -X POST https://api.veritylabs.io/mcp \
  -H "Authorization: Bearer $VERITY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc": "2.0", "id": 1, "method": "tools/list"}'
A first call from the terminal. The same three tools answer any MCP client.

See the API reference →

The next answer your team acts on should arrive with its sources.

Book a demo