_ registry / mcp + a2a http-sse · checked 23m ago

trustlayer

https://api.thetrustlayer.xyz

Registry code: 31c87779ac8581bc

api record

Provides on-chain analytics for AI agents, including network statistics, owner portfolios, reviewer profiles, and trust scores.

endpoint
https://api.thetrustlayer.xyz/mcp
door code
354f2ab3eb168aef
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
live
uptime
100%
latency
56ms

last good check

priced tools
0

of 6 tools

_ what it is for
topic
crypto & onchain onchain analytics
used for
  • get network statistics
  • get owner portfolio
  • get reviewer profile
  • get score history
  • get trust report
takes → gives
text, data → data, text
tools
6 reads
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 6 tools
6 never probed 0 of 6 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.

  • get_score_history reads unknown never probed

    Full score time-series for an agent: daily snapshots, 7d/30d trajectory, volatility over reputation lifetime.

    mcp-tool

    {
  "type": "object",
  "required": [
    "agentId"
  ],
  "properties": {
    "agentId": {
      "type": "string",
      "description": "Agent ID in chain:id format. Example: base:1378"
    }
  }
}
    arguments 12 lines
  • get_trust_report reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "agentId"
  ],
  "properties": {
    "agentId": {
      "type": "string",
      "description": "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"
    }
  }
}
    arguments 12 lines
  • get_reviewer_profile reads unknown never probed

    Quality score and review history for a wallet that has left ERC-8004 feedback. High-quality reviewers are rare — most score below 50.

    mcp-tool

    {
  "type": "object",
  "required": [
    "address"
  ],
  "properties": {
    "address": {
      "type": "string",
      "description": "Reviewer wallet address (0x...). Example: 0x1234...abcd"
    }
  }
}
    arguments 12 lines
  • get_owner_portfolio reads unknown never probed

    All agents owned by a wallet across all chains, with cross-chain group info and risk assessment.

    mcp-tool

    {
  "type": "object",
  "required": [
    "address"
  ],
  "properties": {
    "address": {
      "type": "string",
      "description": "Owner wallet address (EVM 0x... or Solana)"
    }
  }
}
    arguments 12 lines
  • get_network_stats reads unknown 22h ago

    Live network stats: total agents, chain breakdown, Sybil flags, reviewers scored, cross-chain groups.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_trust_score reads unknown never probed

    Basic trust score (0-100) for an AI agent with component breakdown.

    mcp-tool

    {
  "type": "object",
  "required": [
    "agentId"
  ],
  "properties": {
    "agentId": {
      "type": "string",
      "description": "Agent ID in chain:id format. Example: base:1378"
    }
  }
}
    arguments 12 lines
_ try it over mcp 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.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/31c87779ac8581bc/badge.svg)](https://brick.blue/agent/31c87779ac8581bc)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we knowoff the mcp door
card completeness
100%

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.