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

agentflow

https://agentflow.watch

Registry code: d21c67bd38782fb7

api record

Screen Base wallets for wash/sybil behavior and read the live Real-Agent Index. Free read tools here; the pay-per-call x402 API at agentflow.watch/v1/* gives unlimited programmatic access.

endpoint
https://agentflow.watch/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
292ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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
1 open 5 never probed 1 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.

  • index_stats open 4h ago

    AgentFlow coverage stats: wallets tracked, agents labeled, hubs excluded, authorized x402 payers, transfers in the live window, last indexed block.

    mcp-tool

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

    Wash/sybil screen for any Base wallet — real autonomous agent or fake-volume sybil? Returns a calibrated sybil_score (0-100), confidence, and the reasons. Use before an agent trusts or pays a counterparty.

    mcp-tool

    {
  "type": "object",
  "required": [
    "address"
  ],
  "properties": {
    "address": {
      "type": "string",
      "description": "0x... Base wallet address"
    }
  }
}
    arguments 12 lines
  • counterparty_risk unknown never probed

    Counterparty risk score (0-100; LOW/MEDIUM/HIGH/UNKNOWN) for any Base wallet — wash + hub detection + automation score + known-entity labels.

    mcp-tool

    {
  "type": "object",
  "required": [
    "address"
  ],
  "properties": {
    "address": {
      "type": "string",
      "description": "0x... Base wallet address"
    }
  }
}
    arguments 12 lines
  • real_agent_index unknown never probed

    The Real-Agent Index: what % of 'AI agent' USDC flow on Base is wash/self-dealing vs. genuine one-way payments. The honest benchmark.

    mcp-tool

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

    The speedometer: distinct genuine AI agents ACTIVE on Base in the live 24h / 72h window (rises AND falls), vs. the cumulative count.

    mcp-tool

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

    The Base EIP-3009 Settlement Tape: daily verifiable FLOOR on gasless x402-style USDC settlement on Base — tx count, volume, wash-suspect share (count + value), median payment, share of value >=$1, and chain coverage %. Methodology-versioned, receipts-backed. NOT total x402 volume — a lower bound with its blind spots disclosed.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 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.

_ for your README measured, not declared

measured by brick.blue

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

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 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.