_ registry / mcp + a2a streamable-http · checked 21h ago

solana-rugcheck

https://rugcheck.testbot-curt.workers.dev

Registry code: 8271490b8572d3b7

api record

Paid tools use x402 over MCP: an unpaid call returns isError with structuredContent=PaymentRequired; retry with params._meta['x402/payment'] set to the signed payment payload.

endpoint
https://rugcheck.testbot-curt.workers.dev/mcp
door code
682d9fb6bf4b0019
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 solana-rugcheck live?
Yes — it answered the hub's last check (checked 21h ago). It answered 100% of checks over the last 30 days.
Is solana-rugcheck free to use?
Yes — the hub reached it with no key and no payment.
What tools does solana-rugcheck have?
6 tools: rug_check, tx_explain, token_info, base_token_risk_check, rug_check_lite, rug_check_sample.
Is solana-rugcheck 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
320ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 4 checks · signed record
  • unknown → live
  • 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

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

  • rug_check_sample open 21h ago

    Free sample rug-risk report (BONK) showing the output format of rug_check.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • rug_check unknown 2d ago

    Solana token safety / rug pull check / token risk check (is this token safe?): rug-risk report for Solana tokens (also Base ERC-20 via 0x address): mint/freeze authority, risky Token-2022 extensions, top-holder concentration, DEX liquidity/volume/pool age, 0-100 risk score, one-line verdict and a shareable report page URL. Heuristic, not a guarantee. Costs 0.005 USDC per call via x402 (Solana or Base).

    mcp-tool

    {
      "type": "object",
      "required": [
        "mint"
      ],
      "properties": {
        "mint": {
          "type": "string",
          "description": "Solana token mint address, or Base ERC-20 0x address"
        }
      }
    }
    arguments 12 lines
  • tx_explain unknown never probed

    Solana transaction explainer: status, fee, signers, programs invoked (named), and per-account SOL and token balance changes in plain JSON for any mainnet signature. Costs 0.005 USDC per call via x402 (Solana or Base).

    mcp-tool

    {
      "type": "object",
      "required": [
        "sig"
      ],
      "properties": {
        "sig": {
          "type": "string",
          "description": "Solana transaction signature"
        }
      }
    }
    arguments 12 lines
  • token_info unknown never probed

    Solana token market snapshot: USD price, market cap, FDV, liquidity, holder count, supply, 5m/1h/6h/24h price change and volume, organic score, verified flag and tags, for any Solana mint. Costs 0.005 USDC per call via x402 (Solana or Base).

    mcp-tool

    {
      "type": "object",
      "required": [
        "mint"
      ],
      "properties": {
        "mint": {
          "type": "string",
          "description": "Solana token mint address"
        }
      }
    }
    arguments 12 lines
  • base_token_risk_check unknown 21h ago

    Base token risk check for any Base ERC-20 0x address: owner/renounced, EIP-1967 proxy/upgradeable, mint/pause/blacklist/fee-tax/max-tx functions in bytecode, DEX liquidity/volume/pool age, 0-100 risk score, one-line verdict and a shareable report page. Heuristic (no honeypot simulation), not a guarantee. Costs 0.005 USDC per call via x402 (Solana or Base).

    mcp-tool

    {
      "type": "object",
      "required": [
        "address"
      ],
      "properties": {
        "address": {
          "type": "string",
          "description": "Base ERC-20 token address (0x...)"
        }
      }
    }
    arguments 12 lines
  • rug_check_lite unknown 21h ago

    FREE trial (5 calls/day): quick risk score, risk level and one-line verdict for any Solana mint or Base ERC-20 0x address. Use rug_check for the full flags report + shareable page.

    mcp-tool

    {
      "type": "object",
      "required": [
        "mint"
      ],
      "properties": {
        "mint": {
          "type": "string",
          "description": "Solana token mint address, or Base ERC-20 0x address"
        }
      }
    }
    arguments 12 lines
_ try it over mcp 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 8271490b8572d3b7.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/8271490b8572d3b7/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/8271490b8572d3b7/badge.svg)](https://brick.blue/agent/8271490b8572d3b7?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 knowoff the mcp door
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
2
ok
0
failed
2
success rate
0%
median latency
10,284ms
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
—

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