eleata Claim Verifier runs on your own machine — the client starts it, so there is no endpoint to ping. 41 installs a week from npm. Last commit 30 Jun 2026.
Grounding/hallucination guard: verify a claim against evidence (Supported/Refuted/NEE).
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 2 October 2026. No other catalogue keeps this.
We read the source, 5 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
пакет eleata-verify-mcp ссылается на hernaninverso/eleata-verify-mcp
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add eleata-verify-mcp -e 'EVERIFY_API_KEY=<EVERIFY_API_KEY>' -- npx -y eleata-verify-mcp
{
"mcpServers": {
"eleata-verify-mcp": {
"command": "npx",
"args": [
"-y",
"eleata-verify-mcp"
],
"env": {
"EVERIFY_API_KEY": "<EVERIFY_API_KEY>"
}
}
}
}
[mcp_servers.eleata-verify-mcp]
command = "npx"
args = ["-y", "eleata-verify-mcp"]
env = { EVERIFY_API_KEY = "<EVERIFY_API_KEY>" }
{
"mcpServers": {
"eleata-verify-mcp": {
"command": "npx",
"args": [
"-y",
"eleata-verify-mcp"
],
"env": {
"EVERIFY_API_KEY": "<EVERIFY_API_KEY>"
}
}
}
}
{
"servers": {
"eleata-verify-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"eleata-verify-mcp"
],
"env": {
"EVERIFY_API_KEY": "<EVERIFY_API_KEY>"
}
}
}
}
Put your own value in place of
<EVERIFY_API_KEY> (API key for the eleata Claim Verifier (paid Bearer or RapidAPI key)).
The author’s registry entry marks it as required.
Execution-grounded verification for AI coding agents on Windows: evidence, not agent claims.
Verify academic citations against real databases. Catches hallucinated references, exports BibTeX.
Verify legal case citations against real court records; flag fake/hallucinated cites.
Hallucination validator and factual grounding checker for LLM outputs.
Verify deliverables before shipping: acceptance criteria checked against evidence; signed record.
Force evidence-gated, tiered claim reporting (FACT/INFERENCE/SPECULATION). No-LLM.
Verify AI agent claims vs reality: inline grounding-check + swallowed-exception + transcript review.
Evidence-gated verification, selection, and measurement MCP for coding agents.
Answers built from our own checks of this server.