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

REMOTE · API.TRUEIGHT.COM · 2 COMPONENTS · SCANNED OCT 2

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

0 this week 81 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 898 tokens (~299/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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
  • 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
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the Tru8 Evidence Research MCP server?

Tru8 Evidence Research is a hosted endpoint at https://api.trueight.com/mcp/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.trueight.com

# add to Claude Code
claude mcp add --transport http samyatessmith-tru8 'https://api.trueight.com/mcp/'
// .cursor/mcp.json
{
  "mcpServers": {
    "samyatessmith-tru8": {
      "url": "https://api.trueight.com/mcp/"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "samyatessmith-tru8": {
      "type": "http",
      "url": "https://api.trueight.com/mcp/"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.samyatessmith-tru8]
url = "https://api.trueight.com/mcp/"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "samyatessmith-tru8": {
      "type": "remote",
      "url": "https://api.trueight.com/mcp/",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add samyatessmith-tru8 --url 'https://api.trueight.com/mcp/' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  samyatessmith-tru8:
    url: "https://api.trueight.com/mcp/"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "samyatessmith-tru8": {
      "Transport": "http",
      "Url": "https://api.trueight.com/mcp/"
    }
  }
}
# add to Vellum
assistant mcp add samyatessmith-tru8 -t streamable-http -u 'https://api.trueight.com/mcp/'
// mcp.json
{
  "mcpServers": {
    "samyatessmith-tru8": {
      "type": "http",
      "url": "https://api.trueight.com/mcp/"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 9 Sept 26 0
    • Stability: 0.97 → pass security
  • 8 Sept 26 +1

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

  • 5 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.

  • 3 Sept 26 79
    • Tool “tru8_check” rewrote its description, which is the text the model reads security
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 14 Aug 26 0
    • Server version: 1.0.4 → 1.0.5 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 · Probed https://api.trueight.com/mcp/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=trueight.com CN=WE1,O=Google Trust Services,C=US 5 Aug 2026 3 Nov 2026 ECDSA 256 ECDSA-SHA256 9db3a7f105c021c20e58853d72c9ba62
SANs: trueight.com, *.trueight.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.trueight.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
trueight.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.trueight.com/mcp/ Verified 200
http (plaintext) http://api.trueight.com/mcp/ HTTPS enforced 301 https://api.trueight.com/mcp/
MCP tools · 3 exposed · ~844 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 ~614

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

NameTypeReqDescription
claimstringyesA 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 conten…
compactboolean–If true, strip the full evidence arrays and computed analytics from the response, leaving claims and claim maps. Smaller payload for agents that only need orientation.
max_age_hours––Skip cache hits older than this many hours. Stale lookup hits are discarded and the pipeline re-runs at the next tier up to max_tier. 0 means never serve a cached result.
max_tierstring–Maximum tier to attempt — "lookup", "consensus", "quick" or "full" (default). A CEILING, not a floor: cached and consensus hits still return instantly at their own lower price, so the default costs ~…
NameTypeReqDescription
resultstringyes–

No examples provided.

tru8_get_result ~133

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.

NameTypeReqDescription
check_idstringyesThe check UUID returned by tru8_check. Retrieval is free and limited to your own checks; a check still running returns its status rather than a result, so this is also the poll call.
NameTypeReqDescription
resultstringyes–

No examples provided.

tru8_get_result_raw ~97

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.

NameTypeReqDescription
check_idstringyesThe check UUID returned by tru8_check. Same retrieval as tru8_get_result, without the computed analytics block.
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 hosted endpoint (https://api.trueight.com/mcp/).

Is the Tru8 Evidence Research MCP server safe to use?

Tru8 Evidence Research scores 81 out of 100 on VerifyMCP. 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 844 tokens of context every time the server is loaded.

Does the Tru8 Evidence Research MCP server require authentication?

No. We connected to Tru8 Evidence Research without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

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.