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

100pro-token-risk-screen

https://x402.rendraputra.dev

Registry code: 991b5c894e6e2a66

api record

Three paid read-only tools — token_risk_screen, contract_source_check, wallet_risk_screen. $0.1 USDC per single address, $0.25 per 2-5 address batch, on eip155:8453 via x402 v2. An unpaid tools/call returns HTTP 402 carrying the payment challenge; sign it and retry with the payment under params._meta ('x402/payment' or 'payment').

endpoint
https://x402.rendraputra.dev/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 100pro-token-risk-screen live?
Yes — it answered the hub's last check (checked 44m ago). It answered 100% of checks over the last 30 days.
Is 100pro-token-risk-screen 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 100pro-token-risk-screen have?
3 tools: contract_source_check, wallet_risk_screen, token_risk_screen.
Is 100pro-token-risk-screen 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 99.3%· all time 99.3%

latency
632ms

last good check

priced tools
2

of 3 tools

_ answered our checks, 90 days 439 checks · signed record
  • down → live
  • degraded → live
  • live → degraded· HTTP 530
  • degraded → live
  • live → degraded· HTTP 530
_ what it is for
used for
  • screen a token contract for risk before trading
  • check whether a contract source is verified
  • screen a wallet address for risk
takes → gives
text → data
tools
3 reads
_ 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 5 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
1

last 2026-10-26

received on chain
0.1 USDC

counted from three payers (thin, concentrated)

_ what it can do 3 tools
2 paid1 auth-required 3 of 3 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.

  • contract_source_check reads 0.1 USDC paid 18h ago

    Contract-level due diligence for an EVM contract address: whether the source is verified and through which route (sourcify / verifier-alliance / eth-bytecode-db), fully vs partially verified, whether the deployed bytecode still matches the verified source, proxy pattern and implementation address, deployer address and creation tx, contract age, and a capability scan of the verified source (and of the proxy implementation) for mint, pause, blacklist, selfdestruct and delegatecall. Returns markdown ending in a **Verdict** line. Up to 5 comma-separated addresses per call. $0.1 USDC for a single contract address, $0.25 for a 2-5 address batch, on Base (x402 v2, no account, no API key). An unpaid call answers HTTP 402 with the payment challenge; sign it and retry with the payment in the call `_meta`. Read-only: it never signs, transfers, or approves anything on the caller's behalf.

    mcp-tool

    {
      "type": "object",
      "required": [
        "address"
      ],
      "properties": {
        "chain": {
          "enum": [
            "base",
            "ethereum",
            "bsc",
            "polygon",
            "arbitrum"
          ],
          "type": "string",
          "default": null,
          "description": "Optional. Defaults to Base when omitted."
        },
        "address": {
          "type": "string",
          "examples": [
            "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"
          ],
          "maxLength": 300,
          "minLength": 20,
          "description": "EVM address (0x + 40 hex chars). Batch up to 5 addresses, comma-separated. Required."
        }
      },
      "additionalProperties": false
    }
    arguments 30 lines
  • wallet_risk_screen reads 0.1 USDC paid 18h ago

    Wallet-level due diligence for an EVM address: externally-owned account vs contract (and proxy type), age from its first transaction, activity counters, native balance, funding source, how many contracts it has deployed, Blockscout scam/reputation/tags, and GoPlus address-security flags (sanctioned, phishing, mixer, money laundering, honeypot-related, malicious contracts created). Returns markdown with a **Verdict** and a flag list. Up to 5 comma-separated addresses per call. $0.1 USDC for a single wallet address, $0.25 for a 2-5 address batch, on Base (x402 v2, no account, no API key). An unpaid call answers HTTP 402 with the payment challenge; sign it and retry with the payment in the call `_meta`. Read-only: it never signs, transfers, or approves anything on the caller's behalf.

    mcp-tool

    {
      "type": "object",
      "required": [
        "address"
      ],
      "properties": {
        "chain": {
          "enum": [
            "base",
            "ethereum",
            "bsc",
            "polygon",
            "arbitrum"
          ],
          "type": "string",
          "default": null,
          "description": "Optional. Defaults to Base when omitted."
        },
        "address": {
          "type": "string",
          "examples": [
            "0x6aAFF8af0ae8017725312C388bA3745dfE91185B"
          ],
          "maxLength": 300,
          "minLength": 20,
          "description": "EVM address (0x + 40 hex chars). Batch up to 5 addresses, comma-separated. Required."
        }
      },
      "additionalProperties": false
    }
    arguments 30 lines
  • token_risk_screen reads auth-required 18h ago

    Pre-trade risk screen for an EVM token contract or a Solana SPL mint (Base, Ethereum, BSC, Polygon, Arbitrum, Solana). Returns a markdown report: honeypot/tax/owner flags, LP-lock state, mint and freeze authority, transfer fee/hook, holder concentration, liquidity depth, wash-trade flags, and a final **Verdict** line. Up to 5 comma-separated tokens per call. $0.1 USDC for a single token contract / SPL mint, $0.25 for a 2-5 address batch, on Base (x402 v2, no account, no API key). An unpaid call answers HTTP 402 with the payment challenge; sign it and retry with the payment in the call `_meta`. Read-only: it never signs, transfers, or approves anything on the caller's behalf.

    mcp-tool

    {
      "type": "object",
      "required": [
        "token"
      ],
      "properties": {
        "chain": {
          "enum": [
            "solana",
            "base",
            "ethereum",
            "bsc",
            "polygon",
            "arbitrum"
          ],
          "type": "string",
          "default": null,
          "description": "Optional. Omit it and the chain is inferred from the address shape (0x… → Base by default, base58 → Solana). Set it explicitly when the same address shape is ambiguous."
        },
        "token": {
          "type": "string",
          "examples": [
            "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
            "So11111111111111111111111111111111111111112"
          ],
          "maxLength": 300,
          "minLength": 20,
          "description": "EVM address (0x + 40 hex chars) or Solana SPL mint (base58). Batch up to 5 addresses, comma-separated. Required."
        }
      },
      "additionalProperties": false
    }
    arguments 32 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 991b5c894e6e2a66.

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

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.