eleata Claim Verifier
NPM · ELEATA-VERIFY-MCP · SCANNED AUG 3
Grounding/hallucination guard: verify a claim against evidence (Supported/Refuted/NEE).
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security86
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 33 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 310 tokens (~103/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · eleata-verify-mcp
claude mcp add hernaninverso-eleata-verify-mcp -- npx -y eleata-verify-mcp
codex mcp add hernaninverso-eleata-verify-mcp -- npx -y eleata-verify-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"hernaninverso-eleata-verify-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"eleata-verify-mcp"
],
"enabled": true
}
}
} openclaw mcp add hernaninverso-eleata-verify-mcp --command npx --arg -y --arg eleata-verify-mcp
mcp_servers:
hernaninverso-eleata-verify-mcp:
command: "npx"
args: ["-y", "eleata-verify-mcp"] {
"mcpServers": {
"hernaninverso-eleata-verify-mcp": {
"command": "npx",
"args": [
"-y",
"eleata-verify-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Aug 26 +48
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Security disclosure: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: unverified → excellent ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.23 ▲ functional
- First check of Schema quality: unverified functional
- Licence: MIT functional
- 31 Jul 26 −7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 46
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 94 packages
94 packages in the resolved dependency tree · 94 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
check_groundedness ~107
Hallucination guard for RAG / agent answers. Pass the model's generated answer and the retrieved context; returns whether the answer is grounded in the context. Treat any verdict other than 'Supported', or `abstained=true`, as 'ungrounded / likely hallucination' and have the agent retract or re-retrieve.
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | The model-generated answer to check for grounding. |
| context | string | yes | The retrieved context the answer should be grounded in. |
No output schema declared.
No examples provided.
verify_claim ~121
Fact-check a claim against a piece of evidence using natural-language inference. Returns a grounded verdict — Supported, Refuted, or Not Enough Evidence — with a confidence (0..1) and an `abstained` flag. Use it to check whether a statement is actually backed by a source before trusting or repeating it. If `abstained` is true, treat the result as 'cannot verify — do not rely'.
| Name | Type | Req | Description |
|---|---|---|---|
| claim | string | yes | The statement to check. |
| evidence | string | yes | The source text the claim should be supported by. |
No output schema declared.
No examples provided.
verify_strict ~82
Same as verify_claim but with a raised abstention threshold — abstains more readily. Use when a wrong 'Supported' is costly (compliance, legal, medical-adjacent) and the agent must not over-assert.
| Name | Type | Req | Description |
|---|---|---|---|
| claim | string | yes | The statement to check. |
| evidence | string | yes | The source text the claim should be supported by. |
No output schema declared.
No examples provided.