Skip to content

trustlayer MCP server

io.tooloracle/trustlayertooloracle.iostreamable-httpv1.0.0Scanned

FeedOracle Trust Layer - 10-tool cross-server trust: signing, anchoring, verification.

10 tools: 7 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 7 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

7 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the trustlayer MCP server can do

The trustlayer MCP server is published by tooloracle.io, a domain the MCP Registry verified. It has 10 tools. It can create or change data (7 tools: verify_claim, provenance_trace, freshness_guard, hallucination_check and 3 more), but cannot delete data. 3 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 21, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

10 tools

Changes things 7Claude Code: ask
  • confidence_gateDecision gate for agents: should I proceed, exercise caution, abstain, or escalate?No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Decision gate for agents: should I proceed, exercise caution, abstain, or escalate? Evaluates multi-factor confidence for a specific action type (cite, trade, report, recommend) against a threshold.
  • evidence_anchorWITHDRAWN (2026-08-09).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    WITHDRAWN (2026-08-09). This tool does not submit any blockchain transaction and creates no on-chain anchor or proof; it returns a non-success withdrawal notice.
  • freshness_guardCheck if data is current, stale, or expired.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Check if data is current, stale, or expired. Prevents agent decisions based on outdated information. Configurable max age threshold.
  • hallucination_checkCompare an agent's statement against ground truth evidence.No findings

    Why it is in this group

    • The description's first verb is "compare": a word for reading.
    • The input takes a statement or command to run (input.statement), which can change anything it can reach.
    Description, as the server wrote it
    Compare an agent's statement against ground truth evidence. Detects factual mismatches and dangerous hallucination patterns (absolute language, suspect claims). Returns evidence checks and red flags.
  • provenance_traceFull data provenance chain — traces every data point from external source (CoinGecko, ESMA, on-chain) through FeedOracle processing to final delivery.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Full data provenance chain — traces every data point from external source (CoinGecko, ESMA, on-chain) through FeedOracle processing to final delivery. Each step individually hashed. Supports EU AI Act Art. 13 transparency requirements.
  • verify_claimVerify an agent's claim against FeedOracle signed evidence.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Verify an agent's claim against FeedOracle signed evidence. Checks if a statement (e.g. 'USDC market cap is $32B') matches live, cryptographically signed data. Returns verified/partially_verified/unverified with confidence score and recommended action.
  • verify_signatureWITHDRAWN (2026-08-09).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    WITHDRAWN (2026-08-09). This tool performs no cryptographic signature verification and returns a non-success withdrawal notice. A hash comparison is not signature verification.
Only reads 3Show 3 read-only tools
  • agent_reputationGet trust score and reputation for an AI agent from FeedOracle KYA (Know Your Agent) system.No findings

    Why it is in this group

    • The description's first verb is "get": a word for reading.
    Description, as the server wrote it
    Get trust score and reputation for an AI agent from FeedOracle KYA (Know Your Agent) system. Returns trust level (UNVERIFIED → CERTIFIED), score (0-100), and registration details.
  • get_signed_factWITHDRAWN (2026-08-09).No findings

    Why it is in this group

    • The name "get_signed_fact" says "get": a word for reading.
    Description, as the server wrote it
    WITHDRAWN (2026-08-09). This tool does not produce or verify a cryptographic signature and returns a non-success withdrawal notice. Do not rely on it for signed evidence.
  • trust_statusTrust Layer infrastructure health, capabilities, and component status.No findings

    Why it is in this group

    • The name "trust_status" says "status": a word for reading.
    Description, as the server wrote it
    Trust Layer infrastructure health, capabilities, and component status. Shows which verification services are online and what the Trust Layer can do.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:32 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
7
Protocol version
2025-03-26
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://tooloracle.io/.well-known/oauth-protected-resource/trust/mcp
Authorization servers
https://feedoracle.io
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 7 tools that change things (7 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://tooloracle.io/trust/mcp/: tools/list returned 10 tools to an anonymous client, including verify_claim (write), provenance_trace (write), freshness_guard (write), hallucination_check (write), verify_signature (write) and 2 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http trustlayer https://tooloracle.io/trust/mcp/
claude mcp add --transport http trustlayer https://tooloracle.io/trust/mcp/

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__trustlayer__get_signed_fact",
      "mcp__trustlayer__agent_reputation",
      "mcp__trustlayer__trust_status"
    ],
    "ask": [
      "mcp__trustlayer__verify_claim",
      "mcp__trustlayer__provenance_trace",
      "mcp__trustlayer__freshness_guard",
      "mcp__trustlayer__hallucination_check",
      "mcp__trustlayer__verify_signature",
      "mcp__trustlayer__confidence_gate",
      "mcp__trustlayer__evidence_anchor"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as trustlayer. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.tooloracle/trustlayer/verify?hash=b1765154964a5959301bf0f40f9be1dbeac5fb41384c4f95ad5d0862b6afadcf" | jq -e '.changed == false'

Pinned hash b1765154964a, from Nov 21, 2026, 18:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.tooloracle/trustlayer/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.tooloracle/trustlayer
[![Anlyon Radar](https://radar.anlyon.com/badge/io.tooloracle/trustlayer.svg)](https://radar.anlyon.com/servers/io.tooloracle/trustlayer)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:52 UTC.

trustlayer MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the trustlayer MCP server safe?

No scan can promise that. What its definitions show: 10 tools, 7 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the trustlayer MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the trustlayer MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the trustlayer MCP server have?

10 tools: 7 write, 3 read. verify_claim, provenance_trace, freshness_guard, hallucination_check, verify_signature, confidence_gate, evidence_anchor, get_signed_fact and 2 more.

Does the trustlayer MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the trustlayer MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the trustlayer MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.