novaquill-token-risk
Registry code: e7a7397f363caa3e
Honeypot/tax simulation, owner powers and LP locks for BNB Chain and Base tokens, plus new launches
from a public catalogue that lists it, not from the operator
- endpoint
- https://novaquill.dev/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 novaquill-token-risk live?
- Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
- Is novaquill-token-risk free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does novaquill-token-risk have?
- 2 tools: token_risk, new_launches.
- Is novaquill-token-risk 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 2 tools
- unknown → live
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 5 doors on this origin, so the chain figures are the operator's. How it is counted.
through this hub
successful
what callers paid
distinct
last 2026-11-20
counted from three payers (thin, concentrated)
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.
new_launches open 16h ago
Newest tokens launched on BNB Chain (PancakeSwap V2) and Base (Uniswap V2), each scanned for honeypots, taxes, liquidity and owner powers a few minutes after its pool is created. Newest first.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "chain": { "enum": [ "bsc", "base", "all" ], "type": "string", "default": "all", "description": "bsc = BNB Chain, base = Base, all = both" }, "limit": { "type": "integer", "default": 20, "maximum": 50, "minimum": 1, "description": "how many launches to return (1-50)" }, "api_key": { "type": "string", "description": "Novaquill API key for paid credits (optional; 10 free calls/day without)" }, "min_score": { "type": "integer", "maximum": 100, "minimum": 0, "description": "only return tokens with a safety score of at least this (0-100, higher is safer)" } } }arguments 33 linestoken_risk unknown 16h ago
Risk report for a BNB Chain (bsc) or Base token: honeypot and buy/sell/transfer tax simulation, owner privileges (mint, blacklist, pause, fee changes), upgradeable proxy, liquidity USD, LP burned/locked share, owner holdings, risk score 0-100 with flags. Use before buying or recommending a token.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "chain", "address" ], "properties": { "chain": { "enum": [ "bsc", "base" ], "type": "string", "description": "bsc = BNB Chain, base = Base" }, "address": { "type": "string", "pattern": "^0x[0-9a-fA-F]{40}$", "description": "token contract address" }, "api_key": { "type": "string", "description": "Novaquill API key for paid credits (optional; 10 free calls/day without)" } } }arguments 27 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 ide7a7397f363caa3e.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/e7a7397f363caa3e/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/e7a7397f363caa3e?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.