Tru8 Evidence Research
io.github.SamYatesSmith/tru8Version 1.0.6Source-traced evidence research for AI agents. We organise the evidence; you decide.
Status
Responds277 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 14:42 UTC
- Latency
- 277 ms
- Remotes responding
- 1 of 1
- Sign-in
- API key
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 21:12 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://api.trueight.com/mcp/Responds277 msNo sign-in
Claude Code
claude mcp add --transport http tru8 https://api.trueight.com/mcp/ --header 'X-API-Key: <YOUR_X_API_KEY>'Replace <YOUR_X_API_KEY> before running.
Claude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: tru8
Remote MCP server URL: https://api.trueight.com/mcp/
This server expects the header X-API-Key.Cursor
{
"mcpServers": {
"tru8": {
"url": "https://api.trueight.com/mcp/",
"headers": {
"X-API-Key": "<YOUR_X_API_KEY>"
}
}
}
}Replace <YOUR_X_API_KEY> before running.
VS Code
code --add-mcp '{"name":"tru8","type":"http","url":"https://api.trueight.com/mcp/","headers":{"X-API-Key":"<YOUR_X_API_KEY>"}}'Replace <YOUR_X_API_KEY> before running.
Streamable HTTP
pypi: tru8-mcp 1.0.6Package only
PyPI (uvx)
claude mcp add tru8 -e 'TRU8_API_KEY=<YOUR_TRU8_API_KEY>' -- uvx tru8-mcp==1.0.6Replace <YOUR_TRU8_API_KEY> before running.
Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
3 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
tru8_checkEvidence 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):
- lookup (~£0.02, instant) — cached prior analysis
- consensus (~£0.03, instant) — cross-user aggregate landscape (k≥3 checks)
- quick (~£0.07, ~15s) — web search + heuristic classification
- full (~£0.15, ~60-90s) — web + specialist APIs, LLM classification, coverage recovery
Charges based on tier actually executed, not tier requested.
Identical calls within ten minutes return the same check, so a
transport retry never runs — or charges — twice.
Set max_tier to control maximum spend per call.
Output structure:
- claims[].claimMap.elements[] — verifiable sub-claims with state
(supported/disputed/unresolved)
- claims[].claimMap.elements[].evidenceRefs[] — evidence mapped to elements
with relationship (supports/challenges/context) and reasoning
- claims[].evidence[] — sources classified by tier (primary/reporting/
commentary) and type (data/official/news/analysis/opinion/academic)
- claims[].claimMap.orientation — mechanical summary from element states
- _meta — execution metadata: executedTier, chargedPence, limitations
A run that has not finished after several minutes returns
{checkId, status, chargedPence, message} instead of the result: fetch it
later with tru8_get_result (free). A run that FAILS raises an error and is
not charged.
Per-argument guidance lives on the parameters themselves (see the
Annotated/Field declarations above), which is where a client can actually
read it — a docstring "Args:" block never reaches the tool's inputSchema.
| No | No | No | Yes |
tru8_get_resultRetrieve 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.
| No | Yes | Yes | No |
tru8_get_result_rawRetrieve 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.
| No | Yes | Yes | No |
Details
- Registry status
- Active
- Published
- Nov 2, 2026
- Updated
- Nov 2, 2026
- Categories (suggested)
- AI modelsSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared