TrustLayer
REMOTE · API.THETRUSTLAYER.XYZ
Agent reputation scoring: trust scores, Sybil detection, cross-chain identity for 133K+ agents
Available components
Last scanned (3 hours ago)
Scores higher than 16% of remote servers
Unreachable for 2 days in a row. Last reached 3 Nov 2026.
Category Crypto and Web3
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 4 Nov 26 0
- Endpoint reachability: not serving MCP → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- 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
- 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
- 11 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
- 7 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 6 Aug 26 0
- HSTS header: unverified → fail ▼ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: pass functional
- First check of Schema quality: unverified functional
- First check of Tool coverage: 100 functional
- 31 Jul 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
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 5 Nov 2026 · Probed https://api.thetrustlayer.xyz/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.thetrustlayer.xyz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| thetrustlayer.xyz. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.thetrustlayer.xyz/mcp | Unreachable | ||
| http (plaintext) | http://api.thetrustlayer.xyz/mcp | HTTPS enforced |
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 →
get_network_stats ~30
Live network stats: total agents, chain breakdown, Sybil flags, reviewers scored, cross-chain groups.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_owner_portfolio ~49
All agents owned by a wallet across all chains, with cross-chain group info and risk assessment.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Owner wallet address (EVM 0x... or Solana) |
No output schema declared.
No examples provided.
get_reviewer_profile ~62
Quality score and review history for a wallet that has left ERC-8004 feedback. High-quality reviewers are rare — most score below 50.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Reviewer wallet address (0x...). Example: 0x1234...abcd |
No output schema declared.
No examples provided.
get_score_history ~54
Full score time-series for an agent: daily snapshots, 7d/30d trajectory, volatility over reputation lifetime.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | Agent ID in chain:id format. Example: base:1378 |
No output schema declared.
No examples provided.
get_trust_report ~117
Full trust forensics for an AI agent: Sybil risk, reviewer quality, cross-chain identity, anomaly flags, risk level, and recommended max exposure. Covers every ERC-8004 registry chain plus Solana.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | Agent ID in chain:id format. Chains: base, ethereum, bsc, celo, gnosis, optimism, arbitrum, avalanche, polygon, monad, mantle, scroll, linea, metis, taiko, solana-mainnet. Example: base:1378 |
No output schema declared.
No examples provided.
get_trust_score ~47
Basic trust score (0-100) for an AI agent with component breakdown.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | Agent ID in chain:id format. Example: base:1378 |
No output schema declared.
No examples provided.
How do I install the TrustLayer MCP server?
TrustLayer is a hosted endpoint at https://api.thetrustlayer.xyz/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.thetrustlayer.xyz
claude mcp add --transport http goatgaucho-trustlayer 'https://api.thetrustlayer.xyz/mcp'
What is the TrustLayer MCP server?
TrustLayer is an MCP server listed in the public MCP registry as io.github.goatgaucho/trustlayer. Agent reputation scoring: trust scores, Sybil detection, cross-chain identity for 133K+ agents. This page covers its hosted endpoint (https://api.thetrustlayer.xyz/mcp).
Is the TrustLayer MCP server safe to use?
TrustLayer scores 33 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 TrustLayer MCP server expose?
TrustLayer exposes 6 tools: get_trust_report, get_trust_score, get_reviewer_profile, get_owner_portfolio, get_score_history, get_network_stats. Their descriptions and schemas cost roughly 359 tokens of context every time the server is loaded.
Does the TrustLayer MCP server require authentication?
Its publisher declares no required credentials for TrustLayer. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the TrustLayer MCP server still maintained?
TrustLayer is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 3 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.