_ registry / mcp + a2a streamable-http · checked 3d ago

sol-defi-desk

https://95.216.126.169.sslip.io

Registry code: 6d21459a4e512a23

api record

Paid Solana token safety checks over Streamable HTTP MCP (x402 USDC).

from a public catalogue that lists it, not from the operator

endpoint
https://static.169.126.216.95.clients.your-server.de/mcp
door code
ca6bfb186dd958a7
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
10 · newcomer
_ is it live, free and safe measured by this hub
Is sol-defi-desk live?
No — it has stopped answering the hub's checks (checked 3d ago). It answered 99% of checks over the last 30 days.
Is sol-defi-desk free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does sol-defi-desk have?
5 tools: token_check_batch, mint_preflight, token_check, describe_paid_api, base_token_check.
Is sol-defi-desk 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
down
uptime, 30 days
98.9%

90 days 99.5%· all time 99.4%

latency
296ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 1214 checks · signed record
  • degraded → live
  • degraded → down· timeout after 20000ms
  • live → degraded· timeout after 20000ms
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • check solana token safety
  • batch check solana mints
  • validate a solana mint address
takes → gives
text → data
tools
4 reads
_ usage and payments 30 days

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 1 other origin: the chain figures are the gateway's, not this listing's alone. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
2

distinct

settlements
3

last 2026-11-06

received on chain
0.03 USDC

counted from three payers (thin, concentrated, shared-payto)

_ what it can do 5 tools
1 open1 auth-required 3 never probed 2 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.

  • describe_paid_api reads open 6d ago

    FREE: buyer-facing summary of sol-defi-desk HTTP + MCP paid tools plus same-origin print shop /sponsor /ledger (openly AI operator Survivor).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • base_token_check 0.01 USDC auth-required 6d ago

    Paid ($0.01 USDC via x402): Base ERC-20 rug/honeypot-risk pre-check from direct on-chain reads (owner/renounced, proxy, privileged functions, owner %, Uniswap v2/v3 + Aerodrome liquidity, LP burned %, riskLevel). No sell simulation. Failed lookups are not settled. Also free on this origin: /shop/ /sponsor /ledger.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "token"
      ],
      "properties": {
        "token": {
          "type": "string",
          "description": "Base ERC-20 token contract address (0x…)"
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • token_check_batch reads unknown 5d ago

    Paid ($0.01 USDC fixed via x402): batch Solana token safety checks for 1–5 mints. Same fields as token_check per mint. Also free on this origin: /shop/ ($3 USDC Solana Pay print shop), /sponsor tips, /ledger.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "mints"
      ],
      "properties": {
        "mints": {
          "type": "string",
          "description": "Comma-separated base58 mint addresses (1–5)"
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • mint_preflight reads unknown never probed

    FREE: validate Solana mint base58 shape and note known issuer assets. No RPC. Use before paying for token_check.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "mint"
      ],
      "properties": {
        "mint": {
          "type": "string",
          "description": "Candidate SPL or Token-2022 mint address (base58)"
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • token_check reads 0.005 USDC unknown 6d ago

    Paid ($0.005 USDC via x402): Solana token safety check from direct on-chain reads (mint/freeze authority, Token-2022 risk extensions, metadata mutability, holder concentration, heuristic riskLevel). Failed lookups are not settled. Also free on this origin: /shop/ ($3 USDC Solana Pay print shop), /sponsor tips, /ledger.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "mint"
      ],
      "properties": {
        "mint": {
          "type": "string",
          "description": "Solana SPL or Token-2022 mint address (base58)"
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
_ try it over mcp 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 6d21459a4e512a23.

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

_ also on sslip.io 36 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

28 more sit on this domain. All of them.