mcpbeat Sign in

Trustlayer MCP Server

not responding

Trustlayer is listed as active in the registry but did not answer our last check. It exposes 10 tools.

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

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 51 days of history · worst day 0%
51 days agonow
0.0%
Uptime 24h
0 of 91 checks
10
Tools
read from the server
8000 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 3

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 2 September 2026. No other catalogue keeps this.

2 Sep 3 tool descriptions were rewritten evidence_anchor, get_signed_fact, verify_signature

Trustlayer does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

run in your terminal
claude mcp add trustlayer --transport http https://tooloracle.io/trust/mcp/
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "trustlayer": {
      "url": "https://tooloracle.io/trust/mcp/"
    }
  }
}
~/.codex/config.toml
[mcp_servers.trustlayer]
url = "https://tooloracle.io/trust/mcp/"
.cursor/mcp.json
{
  "mcpServers": {
    "trustlayer": {
      "url": "https://tooloracle.io/trust/mcp/"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "trustlayer": {
      "url": "https://tooloracle.io/trust/mcp/"
    }
  }
}

Available tools 10

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

verify
verify_claim
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_signature
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.
agent
agent_reputation
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.
confidence
confidence_gate
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
evidence_anchor
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
freshness_guard
Check if data is current, stale, or expired. Prevents agent decisions based on outdated information. Configurable max age threshold.
hallucination
hallucination_check
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
provenance_trace
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.
signed
get_signed_fact
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
trust_status
Trust Layer infrastructure health, capabilities, and component status. Shows which verification services are online and what the Trust Layer can do.

Endpoints

URLTransportStateLatencyChecked
https://tooloracle.io/trust/mcp/ streamable-http answering 8000 ms 4 min ago

Alternatives to Trustlayer

same job, measured the same way
I
AgentGraph Trust
by agentgraph-co

Security scanning and trust verification for AI agent tools.

110 installs/wk local only
Trust Chain MCP
by csoai-org

Trust Chain MCP server. Tools: create trust anchor, verify chain, add attestation. Built by MEOK AI

177 installs/wk local only
Signet MCP Tools
by prismer-ai

MCP server exposing Signet cryptographic signing, verification, and content hash tools over stdio.

38 installs/wk local only
Data
by vdappdev2

MCP server for Verus on-chain data retrieval, decryption, signing, and verification

29 installs/wk local only
MCP Aml
by cryptoapis-io

MCP server for AML address verification and transaction screening via Crypto APIs

28 installs/wk local only
Deprecation MCP
by tsvillain

MCP server for cross-vendor API/SDK deprecation and breaking-change tracking

35 installs/wk local only
I
Depyler MCP
by noahgift

MCP server for Depyler: Python-to-Rust transpiler with analysis and verification tools

local only
Koda
by aabxtract

Verification and memory layer for coding-agent workflows.

39 installs/wk local only

Trustlayer — questions

Answers built from our own checks of this server.

What can Trustlayer do?
It exposes 10 tools, read directly from the server on our last check. Among them: agent_reputation, confidence_gate, evidence_anchor, freshness_guard, get_signed_fact, hallucination_check and 4 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Trustlayer working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 8000 ms. The bar chart above shows every period we have measured.
Is Trustlayer still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
The registry lists Trustlayer as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Trustlayer?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Trustlayer need an API key?
No. Trustlayer completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 10 of them are readable on this page. This is what we observed, not what the docs claim.