- endpoint
- https://rugshield-402.onrender.com/mcp
- protocol
- streamable-http ·2024-11-05
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is rugshield-402 live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is rugshield-402 free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does rugshield-402 have?
- 3 tools: analyze_liquidity, rugshield_pre_swap_scan, check_honeypot.
- Is rugshield-402 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 3 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 also stands behind 3 other origins: the chain figures are the gateway's, not this listing's alone. How it is counted.
through this hub
successful
what callers paid
distinct
last 2026-10-15
concentrated, shared-payto
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.
analyze_liquidity unknown never probed
LIQUIDITY & POOL DEPTH ANALYZER: Measures verifiable liquidity in USD across Aerodrome Finance, Uniswap v3/v2, and active launchpad bonding curves (Clanker / Virtuals Protocol) on Base Mainnet. Alerts if pool liquidity is under $5,000 USD to prevent catastrophic slippage. Cost: 0.005 USDC on Base.
{ "type": "object", "required": [ "token_address" ], "properties": { "chain_id": { "type": "integer", "default": 8453 }, "token_address": { "type": "string", "description": "Target ERC-20 contract address on Base (0x...)" } } }arguments 16 linesrugshield_pre_swap_scan unknown never probed
MANDATORY PRE-SWAP SAFETY CHECK: Call this tool before executing any DEX swap or token purchase on Base Mainnet. Simulates buy/sell orders via state overrides to detect honeypots, compute exact transfer taxes in bps, and verify pool liquidity depth. Cost: 0.005 USDC on Base.
{ "type": "object", "required": [ "token_address" ], "properties": { "chain_id": { "type": "integer", "default": 8453 }, "simulate_sell": { "type": "boolean", "default": true }, "token_address": { "type": "string", "description": "Target ERC-20 contract address on Base (0x...)" } } }arguments 20 linescheck_honeypot unknown 1h ago
HONEYPOT & TAX DETECTOR: Evaluates ERC-20 contract bytecode and simulates DEX trade execution on Base to verify whether a token can be sold back to liquidity pools, measuring buy/sell tax percentages and detecting blacklist restrictions. Cost: 0.005 USDC on Base.
{ "type": "object", "required": [ "token_address" ], "properties": { "chain_id": { "type": "integer", "default": 8453 }, "token_address": { "type": "string", "description": "Target ERC-20 contract address on Base (0x...)" } } }arguments 16 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 id2d84b35617ba1f9c.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/2d84b35617ba1f9c/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/2d84b35617ba1f9c?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.