eleata Claim Verifier
Grounding/hallucination guard: verify a claim against evidence (Supported/Refuted/NEE).
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
eleata-verify-mcpclaude mcp add eleata-claim-verifier -e 'EVERIFY_API_KEY=<your everify_api_key>' -- npx -y eleata-verify-mcp@0.1.1
{
"mcpServers": {
"eleata-claim-verifier": {
"command": "npx",
"args": [
"-y",
"eleata-verify-mcp@0.1.1"
],
"env": {
"EVERIFY_API_KEY": "<your everify_api_key>"
}
}
}
}
Environment variables
EVERIFY_API_KEYrequired secret API key for the eleata Claim Verifier (paid Bearer or RapidAPI key)
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
eleata Claim Verifier — MCP server
A grounding / hallucination guardrail for AI agents. Give it a claim and supporting
evidence; it returns whether the evidence Supports / Refutes / gives Not Enough Evidence
for the claim (natural-language inference), with a confidence and an abstained flag for
low-confidence cases. Wraps the hosted eleata Claim Verifier.
Use it as a fact-check / RAG hallucination guard: before an agent trusts or repeats a statement, check it against its source. Treat
abstained=true(or any verdict other than Supported) as "do not rely".
Tools
| Tool | What it does |
|---|---|
verify_claim(claim, evidence) | Is the claim supported by the evidence? Verdict + confidence + abstained. |
check_groundedness(answer, context) | RAG guard: is the model's answer grounded in the retrieved context? |
verify_strict(claim, evidence) | Same, with a higher abstention threshold — for compliance/legal where a wrong "Supported" is costly. |
Setup
{
"mcpServers": {
"eleata-verify": {
"command": "npx",
"args": ["-y", "eleata-verify-mcp"],
"env": { "EVERIFY_API_KEY": "your_key" }
}
}
}
Get a key at https://eleata.io/checkout?p=verifypro (paid channel, sent as Authorization: Bearer).
For the RapidAPI marketplace channel, set EVERIFY_RAPIDAPI=1 and EVERIFY_API_BASE to the RapidAPI host
(the key is then sent as X-RapidAPI-Key).
Notes
Confidence is uncalibrated on the public channels (not a probability) — rely on the verdict and the
abstained flag, not the raw number. The engine is a multilingual NLI model (mDeBERTa-v3-mnli-xnli).
verify sends your claim + evidence to the hosted API; see https://eleata.io/privacy/.
MIT licensed.
Frequently asked questions
What is eleata Claim Verifier?
Grounding/hallucination guard: verify a claim against evidence (Supported/Refuted/NEE).
How do I install eleata Claim Verifier?
It runs on your machine. In Claude Code: claude mcp add eleata-claim-verifier -e 'EVERIFY_API_KEY=<your everify_api_key>' -- npx -y eleata-verify-mcp@0.1.1. For other clients, paste the JSON configuration from this page into their MCP settings.
Does eleata Claim Verifier need an API key?
Yes. It expects EVERIFY_API_KEY, which you set in its configuration.
Is eleata Claim Verifier open source?
Its code is public on GitHub, but the repository does not declare a standard license.
Who maintains eleata Claim Verifier?
It is published by hernaninverso. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.