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

chainward

https://api.chainward.ai

Registry code: 4e06ad6e754b0e26

api record

The full dataset behind a published ChainWard decode (e.g. every wallet in an incentive-farming audit, tiered, with the transactions behind each one). CSV.

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

endpoint
https://api.chainward.ai/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 chainward live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is chainward free to use?
Yes — the hub reached it with no key and no payment.
What tools does chainward have?
9 tools: lookup_agent, get_agent_profile, get_agent_economics, list_decodes, find_decodes_for_address, check_counterparty, get_observatory_overview, get_activity_feed, ….
Is chainward 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
519ms

last good check

priced tools
0

of 9 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 10 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
5

distinct

settlements
30

last 2026-10-12

received on chain
42.41 USDC

concentrated

_ what it can do 9 tools
3 open 6 never probed 3 of 9 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_observatory_overview open 2h ago

    Ecosystem-wide stats: total tracked agents, 24h transaction volume across all agents, gas burned, active-agent count, total portfolio value. Use when the user asks broad questions like "how active is the AI agent economy on Base?".

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • get_activity_feed open 2h ago

    Recent labeled-agent activity across the ecosystem. Use when the user asks "what is happening right now?" or wants a live feed.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • get_top_agents open 2h ago

    Ranked leaderboard of agents on Base by transaction volume / revenue / activity. Use when the user asks "who are the top agents?" or "show me the most active agents".

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • lookup_agent unknown never probed

    Look up an Ethereum address on Base to see if ChainWard labels it as a known AI agent. Returns the label (name, framework), any ACP profile data, and pointers to published Decodes that mention this address. Use this BEFORE the user transacts with an unfamiliar address or token deployer.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "wallet"
  ],
  "properties": {
    "wallet": {
      "type": "string",
      "pattern": "^0x[a-fA-F0-9]{40}$"
    }
  }
}
    arguments 13 lines
  • get_agent_profile unknown never probed

    Fetch a full profile for a labeled agent on Base: identity, 24h/7d transaction stats, 7-day balance history (hourly buckets), 30-day gas history (daily), the most recent 20 transactions, and any related published Decodes. Returns 404 if ChainWard does not label this address. Heavier than lookup_agent — use when the user wants detail.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "wallet"
  ],
  "properties": {
    "wallet": {
      "type": "string",
      "pattern": "^0x[a-fA-F0-9]{40}$"
    }
  }
}
    arguments 13 lines
  • get_agent_economics unknown never probed

    Fetch economics for an ACP agent. From ACP (lifetime): revenue, agentic gross dollar product (aGDP), job count, success rate, unique buyer count. From the chain (last 30 days): revenue30d (USD value the wallet received), gasCost30d, txCount30d, profit30d (revenue30d minus gasCost30d) and gasEfficiency (revenue30d / gasCost30d). Do not compare lifetime revenue with 30-day gas. Use when the user asks about agent revenue, profitability, or whether on-chain activity justifies a market cap.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "wallet"
  ],
  "properties": {
    "wallet": {
      "type": "string",
      "pattern": "^0x[a-fA-F0-9]{40}$"
    }
  }
}
    arguments 13 lines
  • list_decodes unknown never probed

    List every published ChainWard Decode (investigative article on agent on-chain behavior), newest first. Each entry includes title, subtitle, date, URL, and the addresses that decode mentions.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • find_decodes_for_address unknown never probed

    Find every published ChainWard Decode that references a given Ethereum address. Returns an array (possibly empty) of decode metadata + URL. Use when the user asks "has ChainWard written about 0x...?".

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "wallet"
  ],
  "properties": {
    "wallet": {
      "type": "string",
      "pattern": "^0x[a-fA-F0-9]{40}$"
    }
  }
}
    arguments 13 lines
  • check_counterparty unknown never probed

    Before paying or trusting an address on Base or BNB Chain, get ChainWard's verdict on it (the `verdict` field): a machine label pay / hold / unknown, a human text (Pay, Hold, Inactive, No track record or Couldn't check), the one reason it rests on, and its limits. The flags under it are the evidence. Pass chain: 'bsc' for a BNB Chain address (default 'base'). On Base, also the EAS attestation (uid + explorer link) when ChainWard has published one, so the result is verifiable on-chain (BNB Chain reports are not attested yet). Read from on-chain behavior only: Pay means nothing was found against paying, not a guarantee. If the address has no report yet, say so and point to the free check at https://chainward.ai (https://chainward.ai/?chain=bsc for BNB Chain).

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "wallet"
  ],
  "properties": {
    "chain": {
      "enum": [
        "base",
        "bsc"
      ],
      "type": "string",
      "default": "base",
      "description": "Chain the address is on: 'base' (default) or 'bsc' (BNB Chain)"
    },
    "wallet": {
      "type": "string",
      "pattern": "^0x[a-fA-F0-9]{40}$"
    }
  }
}
    arguments 22 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 4e06ad6e754b0e26.

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