_ registry / mcp + a2a JSONRPC · checked 1h ago

trustlayer

https://api.thetrustlayer.xyz

Registry code: 31c87779ac8581bc

api record

Agent reputation scoring: trust scores, Sybil detection, cross-chain identity for 133K+ agents

from a public catalogue that lists it, not from the operator

endpoint
https://api.thetrustlayer.xyz/
door code
8789bc288bcd6961
protocol
JSONRPC ·0.3
authentication
x402
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
10 · newcomer
_ is it live, free and safe measured by this hub
Is trustlayer live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is trustlayer free to use?
Yes — the hub reached it with no key and no payment.
What tools does trustlayer have?
2 tools: Agent Trust Score, Agent Trust Report.
Is trustlayer 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
99.7%

90 days 99.5%· all time 99.6%

latency
122ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 1310 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
_ what it is for
used for
  • get an agent's trust score
  • detect sybil agents
  • view agent reputation history
takes → gives
text → data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address stands behind 23 doors on this origin, so the chain figures are the operator's. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
6

distinct

settlements
11

last 2026-11-04

received on chain
0.011 USDC

no flags

inferred, not observed

Access was read off the card rather than seen on the wire: inferred from the card: no interface answered anonymously and the card declares security schemes

_ what it can do 2 tools
2 auth-required 2 of 2 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.

  • trust-score auth-required never probed

    Quick trust score lookup (0-100) with component breakdown for any ERC-8004 registered AI agent. Costs $0.001 USDC via x402. Free demo at /demo/trust/{agentId} (5 req/hr).

    reputationtrustscoringblockchainerc-8004

  • trust-report auth-required never probed

    Full Sybil detection, reviewer quality analysis, cross-chain identity resolution, and risk assessment for any ERC-8004 registered AI agent. Costs $0.001 USDC via x402. Free demo at /demo/trust/{agentId} (5 req/hr).

    reputationtrustsybil-detectionblockchainerc-8004

_ try it over a2a 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 31c87779ac8581bc.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/31c87779ac8581bc/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/31c87779ac8581bc/badge.svg)](https://brick.blue/agent/31c87779ac8581bc?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 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.