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

publicaml

https://mcp.publicaml.org

Registry code: 1b8efd4b6453f94c

api record

Free crypto AML/KYT screening for BTC/ETH/BSC/TRON — risk score, sanctions, source of funds.

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

endpoint
https://mcp.publicaml.org/mcp
protocol
http-sse ·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 publicaml live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is publicaml free to use?
Yes — the hub reached it with no key and no payment.
What tools does publicaml have?
7 tools: screen_address, trace_source_of_funds, follow_swap, list_counterparties, list_transactions, trace_funds, screen_transaction.
Is publicaml 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
292ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 326 checks · signed record
  • degraded → live
  • unknown → live
_ what it is for
used for
  • screen a crypto address for aml risk
  • trace the source of funds of a wallet
  • screen a transaction for risk
  • list wallet counterparties
takes → gives
text → data
tools
7 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

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 7 tools
7 never probed 0 of 7 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.

  • screen_address reads unknown never probed

    Screen a crypto wallet address for AML/KYT risk. Returns an AML score (0-100), risk_level (LOW/MEDIUM/HIGH/CRITICAL), category, sanctioned exposure and source-of-funds. Read-only: it only looks the address up, it never changes anything.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "address",
        "chain"
      ],
      "properties": {
        "chain": {
          "enum": [
            "bitcoin",
            "ethereum",
            "bsc",
            "tron"
          ],
          "type": "string",
          "description": "Blockchain: bitcoin, ethereum, bsc or tron."
        },
        "address": {
          "type": "string",
          "description": "The wallet address to screen."
        }
      },
      "additionalProperties": false
    }
    arguments 25 lines
  • trace_source_of_funds reads unknown 14h ago

    Walk an address's INCOMING funds backwards to answer 'where did this wallet's money come from'. Stops at labelled entities (exchanges, mixers, services) and reports them with hop distance. Answers source-of-funds questions. Read-only: it only reads on-chain history.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "address",
        "chain"
      ],
      "properties": {
        "chain": {
          "enum": [
            "bitcoin",
            "ethereum",
            "bsc",
            "tron"
          ],
          "type": "string",
          "description": "Blockchain: bitcoin, ethereum, bsc or tron."
        },
        "address": {
          "type": "string",
          "description": "The address whose funding to trace."
        },
        "max_hops": {
          "type": "integer",
          "maximum": 8,
          "minimum": 1,
          "description": "How far back to walk. Default set by the API."
        }
      },
      "additionalProperties": false
    }
    arguments 31 lines
  • follow_swap reads unknown 1h ago

    For one transaction that went through a DEX or aggregator, show the net balance change per address and asset and flag who the swap was actually for. Use it to continue a trace past a swap. EVM chains (ethereum, bsc). Read-only.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "tx_hash",
        "chain"
      ],
      "properties": {
        "chain": {
          "enum": [
            "ethereum",
            "bsc"
          ],
          "type": "string",
          "description": "ethereum or bsc."
        },
        "tx_hash": {
          "type": "string",
          "description": "0x-prefixed transaction hash."
        },
        "block_number": {
          "type": "integer",
          "description": "Optional. Looked up automatically."
        }
      },
      "additionalProperties": false
    }
    arguments 27 lines
  • list_counterparties reads unknown 1h ago

    List the counterparties an address has transacted with — optionally filtered by entity category (cex, mixer, gambling, bridge, ...). Set with_risk=true to attach AML risk per counterparty. Read-only: it only lists existing on-chain counterparties, it never writes anything.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "address",
        "chain"
      ],
      "properties": {
        "chain": {
          "enum": [
            "bitcoin",
            "ethereum",
            "bsc",
            "tron"
          ],
          "type": "string",
          "description": "Blockchain: bitcoin, ethereum, bsc or tron."
        },
        "limit": {
          "type": "integer",
          "maximum": 200,
          "minimum": 1,
          "description": "Max counterparties to return."
        },
        "address": {
          "type": "string",
          "description": "The wallet whose counterparties to look at."
        },
        "category": {
          "type": "string",
          "description": "Optional. Only return counterparties of this entity type: cex, mixer, gambling, bridge, etc. Leave empty to list all significant counterparties."
        },
        "with_risk": {
          "type": "boolean",
          "description": "Attach aml_score/risk_level/sanctioned to each counterparty."
        }
      },
      "additionalProperties": false
    }
    arguments 39 lines
  • list_transactions reads unknown 1h ago

    A wallet's recent transfers, newest first, with direction and counterparty for each, plus what we know about each counterparty. Optionally only transfers with one kind of counterparty (e.g. 'did this wallet deposit to a casino'). Read-only.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "address",
        "chain"
      ],
      "properties": {
        "chain": {
          "enum": [
            "bitcoin",
            "ethereum",
            "bsc",
            "tron"
          ],
          "type": "string",
          "description": "Blockchain: bitcoin, ethereum, bsc or tron."
        },
        "limit": {
          "type": "integer",
          "maximum": 100,
          "minimum": 1,
          "description": "Max transfers to return. Default 25."
        },
        "since": {
          "type": "string",
          "description": "Optional start date, ISO-8601 (e.g. 2026-09-01)."
        },
        "until": {
          "type": "string",
          "description": "Optional end date, ISO-8601."
        },
        "address": {
          "type": "string",
          "description": "The wallet to list."
        },
        "counterparty_category": {
          "type": "string",
          "description": "Optional. Only transfers whose counterparty is of this type: cex, mixer, gambling, bridge, etc."
        }
      },
      "additionalProperties": false
    }
    arguments 43 lines
  • trace_funds reads unknown 14h ago

    Follow the OUTGOING funds from an address across the chain and report where the money ends up (exchanges, mixers, sanctioned wallets) and how many hops away. Read-only: it only reads on-chain history, it never moves or changes funds.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "address",
        "chain"
      ],
      "properties": {
        "chain": {
          "enum": [
            "bitcoin",
            "ethereum",
            "bsc",
            "tron"
          ],
          "type": "string",
          "description": "Blockchain: bitcoin, ethereum, bsc or tron."
        },
        "address": {
          "type": "string",
          "description": "The address whose outgoing funds to follow."
        },
        "max_hops": {
          "type": "integer",
          "maximum": 12,
          "minimum": 1,
          "description": "How many hops to follow. Default 3 (6 on bitcoin); raise it only if the result is incomplete."
        }
      },
      "additionalProperties": false
    }
    arguments 31 lines
  • screen_transaction reads unknown 14h ago

    Screen one transaction by hash: what moved, who took part, a label and AML risk for every participant, and an overall verdict. Pass focus_address (e.g. your own deposit address) to get the verdict from that wallet's point of view. Read-only.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "tx_hash",
        "chain"
      ],
      "properties": {
        "chain": {
          "enum": [
            "bitcoin",
            "ethereum",
            "bsc",
            "tron"
          ],
          "type": "string",
          "description": "Blockchain: bitcoin, ethereum, bsc or tron."
        },
        "tx_hash": {
          "type": "string",
          "description": "Transaction hash (0x-prefixed on EVM chains, bare hex txid on bitcoin)."
        },
        "block_number": {
          "type": "integer",
          "description": "Optional. Looked up automatically on ethereum and bsc."
        },
        "focus_address": {
          "type": "string",
          "description": "Optional. The wallet you are screening for, to scope the verdict to it."
        }
      },
      "additionalProperties": false
    }
    arguments 33 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 1b8efd4b6453f94c.

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