_ registry / mcp http-sse · checked 1h ago

spraay-solana-gateway

https://gateway-solana.spraay.app

Registry code: ff7365199dc4ca8a

api record

Batch send SOL or any SPL token to 1000+ wallets via x402. AI agent payments on Solana.

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

endpoint
https://gateway-solana.spraay.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 it live, free and safe measured by this hub
Is spraay-solana-gateway live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is spraay-solana-gateway free to use?
Yes — the hub reached it with no key and no payment.
What tools does spraay-solana-gateway have?
4 tools: spraay_solana_quote, spraay_solana_status, spraay_solana_batch_send_sol, spraay_solana_batch_send_token.
Is spraay-solana-gateway 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
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
327ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 316 checks · signed record
  • unknown → live
_ what it is for
used for
  • batch send sol to many wallets
  • batch send an spl token to many wallets
  • estimate cost of a batch send
  • check a solana transaction status
takes → gives
data, payments → data, payments
tools
2 reads2 moves money
_ usage and payments 30 days

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.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

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

_ what it can do 4 tools
4 never probed 0 of 4 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.

  • spraay_solana_quote reads unknown never probed

    Get a cost estimate for a Spraay batch send on Solana. Returns fees, tx count, and timing. Costs $0.001 USDC via x402.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "recipients"
      ],
      "properties": {
        "token": {
          "type": "string",
          "description": "Token symbol: SOL, USDC, BONK, etc."
        },
        "recipients": {
          "type": "number",
          "description": "Number of recipients",
          "exclusiveMinimum": 0
        }
      },
      "additionalProperties": false
    }
    arguments 19 lines
  • spraay_solana_status reads unknown 13h ago

    Check the status of a Solana transaction by its signature. Costs $0.001 USDC via x402.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "txid"
      ],
      "properties": {
        "txid": {
          "type": "string",
          "description": "Solana transaction signature"
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • spraay_solana_batch_send_sol moves money unknown never probed

    Batch send SOL to multiple Solana wallets in one call. Supports up to 1000 recipients. Auto-chunks large batches. Costs $0.01 USDC via x402 protocol.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "recipients"
      ],
      "properties": {
        "recipients": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "address",
              "amount"
            ],
            "properties": {
              "amount": {
                "type": "number",
                "description": "Amount of SOL to send",
                "exclusiveMinimum": 0
              },
              "address": {
                "type": "string",
                "description": "Solana wallet address (base58)"
              }
            },
            "additionalProperties": false
          },
          "maxItems": 1000,
          "minItems": 1,
          "description": "Array of recipients"
        }
      },
      "additionalProperties": false
    }
    arguments 35 lines
  • spraay_solana_batch_send_token moves money unknown never probed

    Batch send any SPL token (USDC, BONK, WIF, JUP, etc.) to multiple Solana wallets. Auto-creates token accounts. Costs $0.01 USDC via x402.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "mint",
        "recipients"
      ],
      "properties": {
        "mint": {
          "type": "string",
          "description": "SPL token mint address (base58)"
        },
        "recipients": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "address",
              "amount"
            ],
            "properties": {
              "amount": {
                "type": "number",
                "description": "Amount of tokens to send",
                "exclusiveMinimum": 0
              },
              "address": {
                "type": "string",
                "description": "Solana wallet address (base58)"
              }
            },
            "additionalProperties": false
          },
          "maxItems": 1000,
          "minItems": 1,
          "description": "Array of recipients"
        }
      },
      "additionalProperties": false
    }
    arguments 40 lines
_ try it 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 ff7365199dc4ca8a.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/ff7365199dc4ca8a/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/ff7365199dc4ca8a/badge.svg)](https://brick.blue/agent/ff7365199dc4ca8a?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 know
card completeness
80%

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.