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

token-safety

https://token-safety-mcp.restockalarm.workers.dev

Registry code: 294cf62f91c352e9

api record

Base ERC-20 token safety tools. Paid tools cost $0.02 USDC via x402 (Base or Polygon). token_safety_demo is free (5 calls/day per IP). Not investment advice.

endpoint
https://token-safety-mcp.restockalarm.workers.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 token-safety live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is token-safety free to use?
Yes — the hub reached it with no key and no payment.
What tools does token-safety have?
5 tools: holder_check, momentum_score, token_safety_demo, token_risk, rug_check.
Is token-safety 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
648ms

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.

  • holder_check unknown 2h ago

    Holder analysis for an ERC-20 on Base: top 10 holders typed wallet/contract/LP/burn, wallet concentration, distribution and bundling check. Use to judge supply concentration. $0.02 via x402.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "address"
  ],
  "properties": {
    "address": {
      "type": "string",
      "pattern": "^0x[0-9a-fA-F]{40}$",
      "description": "ERC-20 contract address on Base (0x + 40 hex)"
    }
  },
  "additionalProperties": false
}
    arguments 15 lines
  • momentum_score unknown never probed

    Momentum score 0-100 for an ERC-20 on Base from 24 h volume, volume vs liquidity and price change, with confidence low/medium/high. Null for stablecoins. Use to rank Base tokens by activity. $0.02 via x402.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "address"
  ],
  "properties": {
    "address": {
      "type": "string",
      "pattern": "^0x[0-9a-fA-F]{40}$",
      "description": "ERC-20 contract address on Base (0x + 40 hex)"
    }
  },
  "additionalProperties": false
}
    arguments 15 lines
  • token_safety_demo unknown never probed

    Free demo (5 calls/day per IP): run one of token_risk, rug_check, holder_check, momentum_score without payment. Same output as the paid tool.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "tool",
    "address"
  ],
  "properties": {
    "tool": {
      "enum": [
        "token_risk",
        "rug_check",
        "holder_check",
        "momentum_score"
      ],
      "type": "string",
      "description": "Which tool to run"
    },
    "address": {
      "type": "string",
      "pattern": "^0x[0-9a-fA-F]{40}$",
      "description": "ERC-20 contract address on Base (0x + 40 hex)"
    }
  },
  "additionalProperties": false
}
    arguments 26 lines
  • token_risk unknown never probed

    Risk score 0-100 (higher = riskier) for an ERC-20 on Base: liquidity, top-5 holder concentration, honeypot/tax flags. Use before buying or listing an unknown Base token. $0.02 via x402. Not investment advice.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "address"
  ],
  "properties": {
    "address": {
      "type": "string",
      "pattern": "^0x[0-9a-fA-F]{40}$",
      "description": "ERC-20 contract address on Base (0x + 40 hex)"
    }
  },
  "additionalProperties": false
}
    arguments 15 lines
  • rug_check unknown 2h ago

    Rug-pull check for an ERC-20 on Base: rug_pull true/false, confidence and 5 signals (liquidity removal, wash trading, LP lock, owner wallet, honeypot/tax). Use before buying a new Base token. $0.02 via x402.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "address"
  ],
  "properties": {
    "address": {
      "type": "string",
      "pattern": "^0x[0-9a-fA-F]{40}$",
      "description": "ERC-20 contract address on Base (0x + 40 hex)"
    }
  },
  "additionalProperties": false
}
    arguments 15 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 294cf62f91c352e9.

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