tru8-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRU8_API_KEY | Yes | API key (tru8_sk_...). Create at dashboard > Settings > Developer. | |
| TRU8_API_URL | No | API base URL. Default: https://api.trueight.com | https://api.trueight.com |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| tru8_checkA | Evidence research for a factual claim or article URL. Submit a claim as text or paste an article URL. URLs are auto-detected and trigger article mode: the pipeline extracts claims from the page and auto-selects up to 5 for evidence research. Tiers (in fallback order):
Charges based on tier actually executed, not tier requested. Set max_tier to control maximum spend per call. Output structure:
Args: claim: A factual claim ("The Earth's average temperature rose 1.1°C since 1880") or an article URL (https://example.com/article). URLs are auto-detected and the pipeline extracts claims from the page content. max_tier: Maximum tier to attempt — "lookup", "consensus", "quick" (default), or "full". max_age_hours: Skip cache hits older than this many hours. If set, lookup hits that are stale will be discarded and the pipeline re-runs at the next tier up to max_tier. compact: If True, strip full evidence arrays from response (smaller payload). |
| tru8_get_resultA | Retrieve a previously submitted check with pre-computed analytics. Returns the full result including a _computed block with tier/type distributions, corroboration groups, diagnostic values, timeline analysis, element state summaries, and per-claim dispositions. Use this over tru8_get_result_raw when you want structured analytics ready for summarisation or comparison without post-processing. Args: check_id: UUID returned by tru8_check. |
| tru8_get_result_rawA | Retrieve a previously submitted check without computed analytics. Returns claims, elements, evidence, and claim maps only. No _computed block. Smaller response payload. Use this when you will compute your own aggregations or only need specific fields from the raw data. Args: check_id: UUID returned by tru8_check. |
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
The three tools have distinct purposes: check submits a claim, get_result returns analytics, and get_result_raw returns raw data. The two retrieval tools are very similar but explicitly differentiated by descriptions, causing minimal ambiguity.
All tools follow the pattern tru8_<verb>_<modifier> with consistent snake_case. The verbs 'check' and 'get' are clear, and modifiers 'result' and 'result_raw' are descriptive and uniformly applied.
Three tools is well-suited for the narrow domain of fact-checking: one for submitting a claim and two for retrieving results in different formats. No unnecessary tools, and the count is sufficient for the core workflow.
The tool surface covers the primary workflow (submit and retrieve results with or without analytics). However, there is no tool to list or manage previous checks, which is a minor gap for users who need to track multiple checks.