_ registry / mcp streamable-http · checked 1h ago

ethos

https://developers.ethos.network

Registry code: 392352095bd3c3ec

api record

Ethos is a reputation network for crypto: people review each other, vouch with staked ETH, and link wallets and social accounts to one profile. These tools answer "can I trust this wallet, X account or person?" They are read-only and free. Which tool: ethos_score for a quick trust check (score 0 to 2800; below 800 untrusted, 800 to 1199 questionable, 1200 to 1399 neutral, 1400 and up increasingly reputable, to renowned); ethos_user_by_x or ethos_user_by_address for the full profile behind an X handle or wallet, including every linked account; ethos_search_users when you only have a name or…

endpoint
https://developers.ethos.network/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is ethos live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is ethos free to use?
Yes — the hub reached it with no key and no payment.
What tools does ethos have?
5 tools: ethos_score, ethos_user_by_x, ethos_user_by_address, ethos_xp, ethos_search_users.
Is ethos 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
100%

90 days 100%· all time 100%

latency
425ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 8 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
1

distinct

settlements
5

last 2026-11-03

received on chain
0.005 USDC

counted from three payers (thin, concentrated)

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

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

  • ethos_score unknown 1h ago

    Is this wallet, X account or person trustworthy? Ethos credibility score (0 to 2800) and level, from untrusted to renowned, built from peer reviews, ETH-backed vouches, slashes and linked on-chain and social history. Use it before trading with, following, quoting or paying an unknown counterparty, to rank accounts by reputation, or to flag likely scams and bots. Takes an EVM address, X handle or account id, Discord or Telegram id, or Ethos profile id. Free, no payment or key; the same answer as the free Ethos API. Example input: {"userkey":"service:x.com:username:ethos_network"}. Example output: {"score":2441,"level":"revered"}

    mcp-tool

    {
      "type": "object",
      "required": [
        "userkey"
      ],
      "properties": {
        "userkey": {
          "type": "string",
          "description": "An Ethos userkey: address:0x… (EVM address), profileId:<n>, service:x.com:<X account id>, service:x.com:username:<X handle>, service:discord:<id> or service:telegram:<id>."
        }
      }
    }
    arguments 12 lines
  • ethos_user_by_x unknown 1h ago

    Who is behind an X (Twitter) handle, and can they be trusted? The Ethos profile for a handle or numeric account id: display name, credibility score and status, every wallet address and social account linked to the same person, XP, influence factor, and how many positive, neutral and negative reviews and vouches they have received. Use it to vet an account before engaging, resolve a handle to its wallets, or enrich a mention with reputation. Free, no payment or key; the same answer as the free Ethos API. Example input: {"handle":"ethos_network"}. Example output: {"id":32936,"profileId":1,"displayName":"Ethos","username":"ethos_network","avatarUrl":"https://pbs.twimg.com/profile_images/2074951227599646720/85k3GJ-s.jpg","score":2441,"status":"ACTIVE","userkeys":["profileId:1","service:x.com:1234567890","address:0x1234…"],"xpTotal":4076702,"influenceFactor":276,"stats":{"review":{"received":{"positive":120,"neutral":3,"negative":2}},"vouch":{"received":{"count":40}}}}

    mcp-tool

    {
      "type": "object",
      "required": [
        "handle"
      ],
      "properties": {
        "handle": {
          "type": "string",
          "description": "X handle without the @, or the numeric X account id."
        }
      }
    }
    arguments 12 lines
  • ethos_user_by_address unknown never probed

    Who owns this wallet, and what is their reputation? The Ethos profile holding an EVM address: display name, X handle and other linked accounts, credibility score and status, XP, influence factor, and review and vouch counts. Use it to attach a name and trust level to a counterparty address before a trade, transfer, airdrop or allowlist decision, or to screen addresses in a transaction for known bad actors. Free, no payment or key; the same answer as the free Ethos API. Example input: {"address":"0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"}. Example output: {"id":32936,"profileId":1,"displayName":"vitalik.eth","username":null,"avatarUrl":"https://pbs.twimg.com/profile_images/2074951227599646720/85k3GJ-s.jpg","score":1311,"status":"INACTIVE","userkeys":["profileId:1","service:x.com:1234567890","address:0x1234…"],"xpTotal":4076702,"influenceFactor":276,"stats":{"review":{"received":{"positive":120,"neutral":3,"negative":2}},"vouch":{"received":{"count":40}}}}

    mcp-tool

    {
      "type": "object",
      "required": [
        "address"
      ],
      "properties": {
        "address": {
          "type": "string",
          "pattern": "^0x[0-9a-fA-F]{40}$",
          "description": "EVM address, 0x-prefixed."
        }
      }
    }
    arguments 13 lines
  • ethos_xp unknown never probed

    How active and invested is this person in the Ethos reputation network? Total XP earned across all seasons for a userkey (address, X handle or id, Discord or Telegram id, or profile id). XP accrues from reviews, vouches, invitations and other contributions, so it separates long-standing, engaged members from fresh or dormant accounts. Use it alongside the credibility score to weigh how much history stands behind a reputation. Free, no payment or key; the same answer as the free Ethos API. Example input: {"userkey":"profileId:1"}. Example output: 4076702

    mcp-tool

    {
      "type": "object",
      "required": [
        "userkey"
      ],
      "properties": {
        "userkey": {
          "type": "string",
          "description": "An Ethos userkey: address:0x… (EVM address), profileId:<n>, service:x.com:<X account id>, service:x.com:username:<X handle>, service:discord:<id> or service:telegram:<id>."
        }
      }
    }
    arguments 12 lines
  • ethos_search_users unknown 1h ago

    Find a person or project on Ethos when you only have a name, a partial handle or part of an address. Returns matching profiles with credibility score, status, linked wallets and social accounts, paginated. The starting point when a user asks about someone by name: search, pick the match, then score or profile it by userkey. Also useful for disambiguating impersonators from the real account. Free, no payment or key; the same answer as the free Ethos API. Example input: {"query":"vitalik","limit":"5"}. Example output: {"values":[{"id":32936,"profileId":1,"displayName":"Ethos","username":"ethos_network","avatarUrl":"https://pbs.twimg.com/profile_images/2074951227599646720/85k3GJ-s.jpg","score":2441,"status":"ACTIVE","userkeys":["profileId:1","service:x.com:1234567890","address:0x1234…"],"xpTotal":4076702,"influenceFactor":276,"stats":{"review":{"received":{"positive":120,"neutral":3,"negative":2}},"vouch":{"received":{"count":40}}}}],"total":1,"limit":5,"offset":0}

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 50,
          "minimum": 1,
          "description": "Results per page, default 10."
        },
        "query": {
          "type": "string",
          "description": "Name, handle or address fragment to search for."
        },
        "offset": {
          "type": "integer",
          "minimum": 0,
          "description": "Results to skip, for paging."
        }
      }
    }
    arguments 23 lines
_ try it 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 392352095bd3c3ec.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/392352095bd3c3ec/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/392352095bd3c3ec/badge.svg)](https://brick.blue/agent/392352095bd3c3ec?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 know
card completeness
90%

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.