tokensafe
https://tokensafe-production.up.railway.app
Registry code: bcd7ce079da1bf9c
Solana token safety check — mint authority, freeze authority, top holder concentration, liquidity, honeypot detection, metadata mutability, token age, Token-2022 extension risks, rug risk score
from a public catalogue that lists it, not from the operator
- endpoint
- https://tokensafe-production.up.railway.app/mcp
- protocol
- http-sse ·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 tokensafe live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is tokensafe free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does tokensafe have?
- 1 tool: solana_token_safety_check.
- Is tokensafe 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.
90 days 99.3%· all time 99.3%
last good check
of 1 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- used for
- check solana token rug risk
- takes → gives
- text → data
- tools
- 1 reads
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.
through this hub
successful
what callers paid
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
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_safety_check reads unknown 8h ago
Quick safety screening for any Solana SPL token. Returns: rug risk score (0-100), risk level (LOW/MODERATE/HIGH/CRITICAL/EXTREME), human-readable summary, token name/symbol, whether authorities are renounced, liquidity rating (DEEP/MODERATE/SHALLOW/NONE), top-10 holder concentration percentage, honeypot status (can_sell), token age, Token-2022 extension risks, data_confidence ('complete' or 'partial'), and degraded_note (human-readable explanation when partial). This is a FREE lite check — for full details (individual authority addresses, holder breakdown with addresses, LP lock status and locker identity, honeypot sell tax, field-level change detection), use the x402 paid endpoint at GET /v1/check?mint=<address> ($0.02 USDC per request). If data_confidence='partial', some checks failed (see degraded_checks array and uncertainty_penalties). The risk_score includes uncertainty penalties for missing data — it may not reflect true risk. The actual risk could be much higher if the failed checks would have revealed problems.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "mint_address" ], "properties": { "mint_address": { "type": "string", "description": "Solana token mint address in base58 format" } }, "additionalProperties": false }arguments 14 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idbcd7ce079da1bf9c.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/bcd7ce079da1bf9c/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/bcd7ce079da1bf9c?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.