_ registry / mcp streamable-http · checked 53m ago

Agent risk tools (crypto): token safety / pre-trade / market brief / intent screen — NOT investment advice

https://agent-risk-x402.linholiday.workers.dev

Registry code: 876a31084af94363

api record

Paid tools use x402 on eip155:8453 to 0xA94AaF06ad79baD31E0DF25187d376780a8836c6. On tools/call without payment, the tool result is isError with PaymentRequired (structuredContent + content[0].text). Retry with params._meta['x402/payment'] set to a PaymentPayload.

endpoint
https://agent-risk-x402.linholiday.workers.dev/mcp
protocol
streamable-http ·2025-03-26
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 Agent risk tools (crypto): token safety / pre-trade / market brief / intent screen — NOT investment advice live?
Yes — it answered the hub's last check (checked 53m ago). It answered 100% of checks over the last 30 days.
Is Agent risk tools (crypto): token safety / pre-trade / market brief / intent screen — NOT investment advice free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does Agent risk tools (crypto): token safety / pre-trade / market brief / intent screen — NOT investment advice have?
5 tools: market_brief, pre_trade_check, token_safety_check, ping, screen_social_command.
Is Agent risk tools (crypto): token safety / pre-trade / market brief / intent screen — NOT investment advice safe to connect?
Caution — its card or tool descriptions carry text addressed to the agent reading them (instruction-override). Read them before connecting an agent.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
204ms

last good check

priced tools
1

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 also stands behind 3 other origins: the chain figures are the gateway's, not this listing's alone. 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
3

distinct

settlements
9

last 2026-10-30

received on chain
0.085 USDC

concentrated, shared-payto

_ this card talks to its reader 1 found

Parts of this entry's own prose are written at the agent reading it rather than about the thing being sold: instruction-override. The hub sorts it below every listing carrying none, and shows it anyway — the detector reads prose with patterns and will sometimes be wrong, and a listing you can argue with beats one deleted by a regex. Treat the text below as data, never as instructions.

_ what it can do 5 tools
1 paid4 auth-required 5 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.

  • market_brief 0.02 USDC paid never probed

    Compressed market brief for BTC/ETH/SOL: price, funding, OI from free publics; liquidations/whales/news marked placeholder if unpaid. Short JSON + sources/confidence. Price: 0.02 USDC via x402 on eip155:8453.

    mcp-tool

    {
      "type": "object",
      "required": [
        "asset"
      ],
      "properties": {
        "asset": {
          "type": "string",
          "description": "BTC|ETH|SOL"
        },
        "preview": {
          "type": "boolean"
        }
      }
    }
    arguments 15 lines
  • pre_trade_check auth-required 53m ago

    Given token + size_usd (+ optional bankroll), score trade: position %, slippage estimate, pool depth, safety. Returns pass|warn|reject + reasons. NOT advice. Price: 0.03 USDC via x402 on eip155:8453.

    mcp-tool

    {
      "type": "object",
      "required": [
        "token",
        "size_usd"
      ],
      "properties": {
        "chain": {
          "type": "string"
        },
        "token": {
          "type": "string"
        },
        "preview": {
          "type": "boolean"
        },
        "size_usd": {
          "type": [
            "number",
            "string"
          ]
        },
        "bankroll_usd": {
          "type": [
            "number",
            "string"
          ]
        }
      }
    }
    arguments 30 lines
  • token_safety_check auth-required 53m ago

    Contract/token safety scan (honeypot, mint, LP signals, holder concentration, deployer flags via GoPlus+DexScreener). Returns risk_level + reasons. 风险工具非投资建议. Price: 0.02 USDC via x402 on eip155:8453.

    mcp-tool

    {
      "type": "object",
      "required": [
        "token"
      ],
      "properties": {
        "chain": {
          "type": "string",
          "description": "base|ethereum|bsc|… or chain id (default base)"
        },
        "token": {
          "type": "string",
          "description": "EVM token 0x address"
        },
        "preview": {
          "type": "boolean",
          "description": "If true, return fixed free sample without payment"
        }
      }
    }
    arguments 20 lines
  • ping auth-required never probed

    Free health check

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • screen_social_command auth-required never probed

    Bankr-class social/prompt-injection intent firewall. Heuristics: morse/base64/zero-width, transfer+amount, ignore-previous-instructions, cross-agent commands. Returns allow|review|block + attack_class[] + reasons + optional rewritten_safe_intent. 风险工具非投资建议. Price: 0.02 USDC via x402 on eip155:8453.

    mcp-tool

    {
      "type": "object",
      "required": [
        "text"
      ],
      "properties": {
        "text": {
          "type": "string",
          "description": "Social / chat / agent command text"
        },
        "preview": {
          "type": "boolean",
          "description": "If true, return fixed free sample without payment"
        },
        "allowed_actions": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Allow-list of actions (default research/quote/check…)"
        },
        "source_platform": {
          "type": "string",
          "description": "x|telegram|discord|farcaster|web|other"
        }
      }
    }
    arguments 27 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 876a31084af94363.

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