shaniu-mcp
Registry code: c62fc7e842ee2d11
Agent Shaniu (SHANIU): first AI-driven community meme coin on BSC (chainId 56). Mint = call claim() on token 0x67B8c7abeB7A6b6ef29f15032423AfAB4006888f (caller wallet must hold a Binance Agent ID; one claim per address). Trade = on-chain order book 0xCF19D05878Ab8bC53280299442De280afaaA16C8 (no AMM pool; never sell via plain transfer). All 'prepare' tools return unsigned tx intents {to, data, valueWei} — sign and broadcast with the user's own wallet. Invite link: https://bn.shaniu.ai/?ref=<address>.
- endpoint
- https://bn.shaniu.ai/mcp
- door code
- 36b0f4bd9f211e84
- 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 shaniu-mcp live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is shaniu-mcp free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does shaniu-mcp have?
- 7 tools: shaniu_invite_stats, shaniu_prepare_claim, shaniu_market_orders, shaniu_prepare_buy, shaniu_invite_register, shaniu_prepare_list, shaniu_stats.
- Is shaniu-mcp 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 100%· all time 100%
last good check
of 7 tools
- unknown → live
- unknown → live
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
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.
shaniu_stats open 1h ago
Live SHANIU stats: total supply, claim pool remaining, claim count, current claim fee (wei of BNB, ~0.2 USD via Chainlink oracle), whether claiming is open, and optionally a wallet's balance / claimed status.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "address": { "type": "string", "pattern": "^0x[0-9a-fA-F]{40}$", "description": "Optional wallet to check balance and hasClaimed" } } }arguments 11 linesshaniu_invite_stats unknown never probed
Referral program stats: global slots/budget usage, and (with address) one inviter's bound count, earned and pending SHANIU. Invite link format: https://bn.shaniu.ai/?ref=<address>
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "address": { "type": "string", "pattern": "^0x[0-9a-fA-F]{40}$" } } }arguments 10 linesshaniu_prepare_claim unknown never probed
Prepare an unsigned claim() (mint) transaction. Caller wallet must hold a Binance Agent ID (.ai); one claim per address; reward is a block-hash lottery (50-150 typical, up to 21,000; last claim sweeps the pool). Returns {to, data, valueWei} to sign with the user's wallet.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "address" ], "properties": { "address": { "type": "string", "pattern": "^0x[0-9a-fA-F]{40}$", "description": "Wallet that will claim (gets the tokens)" } } }arguments 14 linesshaniu_market_orders unknown never probed
List currently fillable sell orders on the on-chain order book, cheapest first. Each order: id, maker, remainingSHANIU, priceBNBperToken. No AMM pool exists — buying fills these orders atomically.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "limit": { "type": "integer", "default": 20, "maximum": 100, "minimum": 1, "description": "Max orders to return" } } }arguments 13 linesshaniu_prepare_buy unknown never probed
Prepare an unsigned buy transaction that fills one or more sell orders. Computes exact BNB cost. Single order uses the market contract; multiple orders use the cart contract (buyMany) in one tx.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "fills" ], "properties": { "fills": { "type": "array", "items": { "type": "object", "required": [ "id", "amountSHANIU" ], "properties": { "id": { "type": "integer", "maximum": 9007199254740991, "minimum": 0, "description": "Order id" }, "amountSHANIU": { "type": "string", "description": "Amount to buy, e.g. \"100\"" } } }, "maxItems": 50, "minItems": 1 } } }arguments 33 linesshaniu_invite_register unknown never probed
Register a referral binding. Prefer mode=intent BEFORE the invitee calls claim(); or bind after the fact with the invitee's claim tx hash. Always ask your user for consent first. Rewards (10/50/200/1000 SHANIU tiers) roll automatically and are paid in batches.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "inviter", "invitee" ], "properties": { "claimTx": { "type": "string", "pattern": "^0x[0-9a-fA-F]{64}$", "description": "Omit for pre-claim intent registration" }, "invitee": { "type": "string", "pattern": "^0x[0-9a-fA-F]{40}$" }, "inviter": { "type": "string", "pattern": "^0x[0-9a-fA-F]{40}$" } } }arguments 23 linesshaniu_prepare_list unknown 1h ago
Prepare unsigned transactions to list SHANIU for sale: (1) approve the market contract, (2) list(amount, priceWei). The tokens stay in the seller's wallet until filled — the market is authorization-based, no custody.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "amountSHANIU", "priceBNBperToken" ], "properties": { "amountSHANIU": { "type": "string", "description": "Total amount to list, e.g. \"817\"" }, "priceBNBperToken": { "type": "string", "description": "BNB price per 1 SHANIU, e.g. \"0.0000078\"" } } }arguments 18 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 idc62fc7e842ee2d11.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/c62fc7e842ee2d11/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/c62fc7e842ee2d11?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
- 1
- ok
- 0
- failed
- 1
- success rate
- 0%
- median latency
- 441ms
- 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
- —
1 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.