_ registry / mcp http-sse · checked 2h ago

tru8

https://api.trueight.com

Registry code: 7aaa3610d66a503b

api record

Structured evidence research. Submit a factual claim or article URL. Evidence is organised by source tier (primary/reporting/commentary) and type (data/official/news/analysis/opinion/academic), with element decomposition and relationship mapping (supports/challenges/context).

endpoint
https://api.trueight.com/mcp/
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is tru8 live?
Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is tru8 free to use?
Yes — the hub reached it with no key and no payment.
What tools does tru8 have?
3 tools: tru8_get_result, tru8_get_result_raw, tru8_check.
Is tru8 safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98.9%

90 days 99.3%· all time 99.3%

latency
319ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 435 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • research evidence for a factual claim
  • fact-check an article url
  • retrieve a previous evidence check
takes → gives
text, web pages → data
tools
2 reads1 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 3 tools
3 never probed 0 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • tru8_get_result reads unknown 16h ago

    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.

    mcp-tool

    {
      "type": "object",
      "title": "tru8_get_resultArguments",
      "required": [
        "check_id"
      ],
      "properties": {
        "check_id": {
          "type": "string",
          "title": "Check Id",
          "description": "The 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."
        }
      }
    }
    arguments 14 lines
  • tru8_get_result_raw reads unknown 16h ago

    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.

    mcp-tool

    {
      "type": "object",
      "title": "tru8_get_result_rawArguments",
      "required": [
        "check_id"
      ],
      "properties": {
        "check_id": {
          "type": "string",
          "title": "Check Id",
          "description": "The check UUID returned by tru8_check. Same retrieval as tru8_get_result, without the computed analytics block."
        }
      }
    }
    arguments 14 lines
  • tru8_check changes data unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "title": "tru8_checkArguments",
      "required": [
        "claim"
      ],
      "properties": {
        "claim": {
          "type": "string",
          "title": "Claim",
          "description": "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."
        },
        "compact": {
          "type": "boolean",
          "title": "Compact",
          "default": false,
          "description": "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_tier": {
          "type": "string",
          "title": "Max Tier",
          "default": "full",
          "description": "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 ~£0.15 only for claims never researched before. Set \"quick\" to cap spend at ~£0.07, accepting web-search-only sourcing and heuristic classification (see _meta.limitations)."
        },
        "max_age_hours": {
          "anyOf": [
            {
              "type": "integer"
            },
            {
              "type": "null"
            }
          ],
          "title": "Max Age Hours",
          "default": null,
          "description": "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."
        }
      }
    }
    arguments 39 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 7aaa3610d66a503b.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/7aaa3610d66a503b/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/7aaa3610d66a503b/badge.svg)](https://brick.blue/agent/7aaa3610d66a503b?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.