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

rugradar

https://rugradar-dun.vercel.app

Registry code: 49dd9e95d88788b1

api record

Is this crypto token a scam? Rule-based checks on 64 networks, read-only, no wallet or API key.

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

endpoint
https://rugradar-dun.vercel.app/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 rugradar live?
Yes — it answered the hub's last check (checked 30m ago). It answered 100% of checks over the last 30 days.
Is rugradar free to use?
Yes — the hub reached it with no key and no payment.
What tools does rugradar have?
5 tools: scan_message, check_token, token_history, explain_finding, get_report.
Is rugradar 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
446ms

last good check

priced tools
0

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

  • scan_message unknown never probed

    Scan a crypto pitch message for scam tactics (seed phrase requests, wallet-drainer links, guaranteed returns, urgency, send-to-receive) without touching the network. Private data is stripped.

    mcp-tool

    {
      "type": "object",
      "title": "scan_messageArguments",
      "required": [
        "text"
      ],
      "properties": {
        "lang": {
          "type": "string",
          "title": "Lang",
          "default": "en"
        },
        "text": {
          "type": "string",
          "title": "Text"
        }
      }
    }
    arguments 18 lines
  • check_token unknown 30m ago

    Check if a crypto token is a scam before buying. `text` can be a contract address, a DexScreener or pump.fun link, or a whole forwarded "gem" message, on any of 64 networks (chain "auto" detects it; or pass a DexScreener chain id like "ton", "sui", "tron", "hyperevm"). Returns a rule-based verdict (LOW_RISK, CAUTION, HIGH_RISK, UNKNOWN), a 0-100 risk score, plain-language findings (lang "en" or "pcm" for Nigerian Pidgin), what you'd get back in naira, and red flags in the message itself.

    mcp-tool

    {
      "type": "object",
      "title": "check_tokenArguments",
      "required": [
        "text"
      ],
      "properties": {
        "lang": {
          "type": "string",
          "title": "Lang",
          "default": "en"
        },
        "text": {
          "type": "string",
          "title": "Text"
        },
        "chain": {
          "type": "string",
          "title": "Chain",
          "default": "auto"
        },
        "amount_ngn": {
          "type": "integer",
          "title": "Amount Ngn",
          "default": 50000
        }
      }
    }
    arguments 28 lines
  • token_history unknown never probed

    What RugRadar saw the last time this token was checked (verdict, score, pool size, how long ago).

    mcp-tool

    {
      "type": "object",
      "title": "token_historyArguments",
      "required": [
        "chain",
        "address"
      ],
      "properties": {
        "chain": {
          "type": "string",
          "title": "Chain"
        },
        "address": {
          "type": "string",
          "title": "Address"
        }
      }
    }
    arguments 18 lines
  • explain_finding unknown never probed

    Plain-language meaning of a RugRadar finding code such as HONEYPOT or LP_UNLOCKED.

    mcp-tool

    {
      "type": "object",
      "title": "explain_findingArguments",
      "required": [
        "code"
      ],
      "properties": {
        "code": {
          "type": "string",
          "title": "Code"
        },
        "lang": {
          "type": "string",
          "title": "Lang",
          "default": "en"
        }
      }
    }
    arguments 18 lines
  • get_report unknown 30m ago

    Fetch a saved RugRadar check by its id (the code at the end of a rugradar-dun.vercel.app/r/... link). Saved checks last 30 days. Re-run check_token before relying on an old one: tokens change fast.

    mcp-tool

    {
      "type": "object",
      "title": "get_reportArguments",
      "required": [
        "trace_id"
      ],
      "properties": {
        "trace_id": {
          "type": "string",
          "title": "Trace Id"
        }
      }
    }
    arguments 13 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 49dd9e95d88788b1.

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