BG Verification
Truuth MCP connector
The Truuth connector lets Claude, ChatGPT, Cursor and the Elaichi Agent start identity verifications, send verification invites and read fraud, sanctions and document reports in Truuth, inside each person's own access, with every call logged.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
59 tools
How to connect
How to connect Truuth to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Truuth once
-
Open Connections, choose Add connection, and pick Truuth.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Truuth API key. One person generates a token in Truuth and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Truuth MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Truuth MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Truuth MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Truuth to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Truuth through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Compliance
Review the sanctions and PEP report
Ask for the sanctions and politically exposed person report on a customer's verification before approving the account, and get the findings summarized in plain language.
-
Onboarding
Send a verification invite to a new customer
Start a Truuth verification for a new applicant, send them the invite, and follow the events as they upload their document and complete the face check.
-
Risk
Run a fraud check on a submitted ID
Have the document classified, its authenticity checked and its text extracted, then search whether the photo appears elsewhere on the internet.
-
HR
Confirm a new hire is who they say
Create a verification for a candidate, then confirm the face match and liveness results came back clean before the offer goes out.
-
Operations
Catch up on a verification's status
Pull a single verification by its reference and list its events and reports to see exactly where it is stuck and what is still missing.
-
Support
Explain a stalled verification to a customer
Look up the customer's verification, check the document and face images that were received, and tell them clearly what to resubmit.
Try asking
- “Show Truuth verifications created this week by team.”
- “Summarize sanctions and PEP report hits from yesterday.”
- “Which Truuth verification invites are still awaiting completion?”
Compare
Elaichi vs Zapier MCP vs Composio for Truuth
All three can connect Truuth to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Truuth tools | Allow or restrict single Truuth tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Truuth call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
AI tools
Truuth tools for your AI agents
59 tools are ready to call through Elaichi's MCP endpoint the moment you connect Truuth, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Truuth gets you
6 screens from the product, each doing one job for your Truuth account.
The agent
Ask about verifications in plain language.
Starter prompts pull answers from live Truuth verifications, reports and invites.
- verifications
- invites
- reports
- documents
Ask Elaichi to work across your apps.
Show Truuth verifications created this week by team.
Summarize sanctions and PEP report hits from yesterday.
Which Truuth verification invites are still awaiting completion?
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Truuth.
One governed MCP endpoint over OAuth, no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
59 Truuth tools ready, zero custom code.
Browse verification, document, report and fraud check tools with their resources and methods.
- Create a Truuth verification
- Get single Truuth verification by ID
- Create a Truuth verification invite
- List all Truuth verification business report
ElaichiToolsToolboxes
Every team gets its own Truuth toolbox.
Toolboxes scope Truuth verifications, reports and document checks to the teams that need them.
- Onboarding
- Compliance
- Fraud
- Support
ElaichiToolboxesShared connections
Teammates use Truuth without seeing credentials.
See who connected each Truuth account and how many teams and members share it.
- Onboarding APAC
- Compliance
- Fraud Ops
- Support
ElaichiConnectionsAudit log
Answer who ran which Truuth verification.
Append-only log records when, who, what happened, type and resource touched.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule fires, a digest gets approved.
Six steps fetch Truuth verifications, group them, draft a digest, then post it back.
Truuth digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch verifications
Truuth
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Truuth
Queued
Collections and dashboards
Truuth verification health, computed on a schedule.
Four metrics, 14 days of verifications created and a breakdown by team, no model involved.
Truuth health
Refreshed 4 minutes ago · every 15 minutes · from the verifications collection
Verifications
1,284 ↓ 12%
Invites
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Verifications created
Last 14 days
By team
Share of activity
Onboarding APAC 34%
Compliance 27%
Fraud Ops 21%
Support 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Truuth to Claude?
Connect Truuth in Elaichi first: pick Truuth from the catalog and paste in the API key from your Truuth account, then Elaichi confirms the connection. Truuth connects with an API key, so there is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Sign in with your Elaichi account and Truuth is available in Claude.
Does Truuth work with ChatGPT and Cursor as well as Claude?
Yes. Once Truuth is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Truuth once and every client picks it up.
What can an AI agent actually do with my Truuth data?
An agent connected to Truuth can start a verification, send a verification invite, and read the reports that come back: fraud checks, sanctions and PEP screening, business reports, document images, face images and the event history. It can also classify a document, extract its text, check its authenticity, run a face match or liveness check, analyze an email address and search the internet for a photo. Truuth exposes many actions, so short concrete asks such as "show the fraud check report for this verification" work better than long instructions.
Does connecting Truuth give the AI access to every verification?
No. Access follows the person who signed in, so an agent working through Truuth sees only the verifications, reports and images that person's Truuth API key already reaches. Elaichi can narrow that further with restrictions on specific actions, and it can never widen it beyond what Truuth itself allows.
Can I stop an agent from deleting or changing things in Truuth?
Yes. Restrictions in Elaichi apply per action, so you can allow reading Truuth reports and verification events while blocking the creation of new verifications or the deletion of overlay files. A blocked action is never advertised to Claude, ChatGPT, Cursor or any other client, so no prompt can reach it.
What happens to a Truuth connection when someone leaves?
Offboarding the person in Elaichi ends their access to Truuth in every client at once. A shared Truuth connection keeps working for everyone else on the team. If you need to remove Truuth entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client.
Does the Truuth MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Truuth is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Truuth?
Yes. Both let Claude, ChatGPT or Cursor use Truuth. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Truuth call.
How is Elaichi different from Composio for Truuth?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Truuth: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Truuth in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.