Grounding/hallucination guard: verify a claim against evidence (Supported/Refuted/NEE).
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".
| 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. |
{
"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).
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.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y eleata-verify-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-hernaninverso-eleata-verify-mcp": {
"command": "npx",
"args": [
"-y",
"eleata-verify-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referenceeleata Claim Verifier works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.