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

tokenguard

https://gdzlcxskuhupymyxywzm.supabase.co

Registry code: 7b9b890188b41f78

api record

Solana rug check before you buy: SAFE/CAUTION/DANGER from chain state. Free key or x402.

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

endpoint
https://gdzlcxskuhupymyxywzm.supabase.co/functions/v1/tokenguard-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 tokenguard live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is tokenguard free to use?
Yes — the hub reached it with no key and no payment.
What tools does tokenguard have?
4 tools: solana_token_verdict, solana_token_batch, tokenguard_info, solana_token_check.
Is tokenguard 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
1,921ms

last good check

priced tools
0

of 4 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 stands behind 8 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
7

last 2026-10-17

received on chain
0.17 USDC

counted from three payers (thin, concentrated)

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

  • solana_token_verdict unknown never probed

    Use when your agent is about to buy or swap into an unknown Solana token: go/no-go rug check read from chain state. Returns SAFE/CAUTION/DANGER, 0-100 risk score and flags. Skip DANGER, reduce size on CAUTION. Costs 0.001 USDC (x402, Solana or Base).

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "address"
  ],
  "properties": {
    "address": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • solana_token_batch unknown never probed

    Use when screening up to 10 new Solana tokens at once (sniping, watchlists): same output as the full check for each mint, half the per-token price. Costs 0.025 USDC (x402, Solana or Base).

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "addresses"
  ],
  "properties": {
    "addresses": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 10,
      "minItems": 1
    }
  },
  "additionalProperties": false
}
    arguments 18 lines
  • tokenguard_info unknown never probed

    Free: what TokenGuard checks, prices and how to pay (x402).

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • solana_token_check unknown 1h ago

    Use before any Jupiter or pump.fun trade on an unknown Solana mint: full rug check from chain state. Verdict, risk score, flags (freeze or mint authority, Token-2022 traps, wallet concentration, age, pump.fun creator dumping or serial launches), authorities, holders, creator. Costs 0.005 USDC (x402, Solana or Base).

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "address"
  ],
  "properties": {
    "address": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    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 7b9b890188b41f78.

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

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.

_ also on supabase.co 95 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

87 more sit on this domain. All of them.