Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Tru8 Evidence Research

PYPI · TRU8-MCP · 2 COMPONENTS · SCANNED OCT 2

Source-traced evidence research for AI agents. We organise the evidence; you decide.

+3 this week 78 Trust /100
Trust breakdown (7 categories)

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 → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 0 of 28 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability65
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 707 tokens (~235/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
  • Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Tru8 Evidence Research MCP server?

Tru8 Evidence Research runs locally as a PyPI package, launched with uvx tru8-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · tru8-mcp

# add to Claude Code
claude mcp add samyatessmith-tru8 -- uvx tru8-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "samyatessmith-tru8": {
      "command": "uvx",
      "args": [
        "tru8-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "samyatessmith-tru8": {
      "command": "uvx",
      "args": [
        "tru8-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add samyatessmith-tru8 -- uvx tru8-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "samyatessmith-tru8": {
      "type": "local",
      "command": [
        "uvx",
        "tru8-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add samyatessmith-tru8 --command uvx --arg tru8-mcp
# ~/.hermes/config.yaml
mcp_servers:
  samyatessmith-tru8:
    command: "uvx"
    args: ["tru8-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "samyatessmith-tru8": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "tru8-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add samyatessmith-tru8 -t stdio -c uvx -a tru8-mcp
// mcp.json
{
  "mcpServers": {
    "samyatessmith-tru8": {
      "command": "uvx",
      "args": [
        "tru8-mcp"
      ]
    }
  }
}
Changelog

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 Oct 26 −2
    • Stability: pass → 0.80 functional
  • 1 Oct 26 0
    • Stability: 0.97 → pass security
  • 30 Sept 26 +16
    • Malware scan: unverified → pass ▲ security
  • 29 Sept 26 −15
    • Provenance: unverified → fail ▼ security
    • Malware scan: pass → unverified ▼ security
  • 28 Sept 26 +15
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Sept 26 −12
    • Malware scan: pass → unverified ▼ security
    • License: fail → pass ▲ functional
    • Licence: MIT License → MIT functional
  • 25 Sept 26 +12
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

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 2 Oct 2026 · Analysed pypi/tru8-mcp@1.0.3

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 28 packages
Packages resolved 28
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~653 tokens

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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
tru8_check ~466

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): - 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. 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 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).

NameTypeReqDescription
claimstringyes–
compactboolean––
max_age_hours–––
max_tierstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

tru8_get_result ~103

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.

NameTypeReqDescription
check_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

tru8_get_result_raw ~84

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.

NameTypeReqDescription
check_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

Common questions

What is the Tru8 Evidence Research MCP server?

Tru8 Evidence Research is an MCP server listed in the public MCP registry as io.github.SamYatesSmith/tru8. Source-traced evidence research for AI agents. We organise the evidence; you decide. This page covers its PyPI package (tru8-mcp).

Is the Tru8 Evidence Research MCP server safe to use?

Tru8 Evidence Research scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 2 October 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Tru8 Evidence Research MCP server expose?

Tru8 Evidence Research exposes 3 tools: tru8_check, tru8_get_result, tru8_get_result_raw. Their descriptions and schemas cost roughly 653 tokens of context every time the server is loaded.

Is the Tru8 Evidence Research MCP server still maintained?

Tru8 Evidence Research is still listed as active in the MCP registry. We last reached this channel on 2 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Tru8 Evidence Research MCP server under?

Tru8 Evidence Research declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.