eleata-verify-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EVERIFY_API_KEY | Yes | Your eleata API key, sent as Authorization: Bearer header. | |
| EVERIFY_API_BASE | No | Required if EVERIFY_RAPIDAPI=1. The RapidAPI host URL. | |
| EVERIFY_RAPIDAPI | No | Set to '1' to use the RapidAPI marketplace channel. The key is sent as X-RapidAPI-Key instead of Authorization: Bearer. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| verify_claimA | 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 |
| check_groundednessA | 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 |
| verify_strictA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
verify_claim and verify_strict are nearly identical except for an abstention threshold, making it unclear which to choose. check_groundedness overlaps in purpose (checking support in context/evidence). Agents will struggle to differentiate without additional heuristics.
Two tools use 'verify_' (one with noun 'claim', one with adjective 'strict'), and one uses 'check_groundedness'. The verbs 'check' and 'verify' are synonymous but break pattern consistency. The mix of noun and adjective styles is acceptable but not uniform.
With 3 tools, the count is slightly low but appropriate for a narrowly scoped verification server. Each tool serves a distinct mode (normal, strict, groundedness), so no tool feels superfluous.
Covers the core verification operations but lacks any tool for evidence retrieval, source management, or batch verification. The strict version adds nuance but also indicates incomplete coverage of confidence levels. Agents may need to work around missing functionality.