Skip to content

spraay-solana-gateway MCP server

io.github.plagtech/spraay-solana-gatewayplagtechstreamable-httpv1.0.0Scanned

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

4 tools: 2 do something that can't be undone and 2 only read.

Tools: 0 delete, 2 irreversible, 0 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 2
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here do something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the spraay-solana-gateway MCP server can do

The spraay-solana-gateway MCP server is published by the GitHub account plagtech. It has 4 tools. It can do things that cannot be undone, such as sending, paying or publishing (spraay_solana_batch_send_sol and spraay_solana_batch_send_token), but cannot delete data. 2 tools only read.

2 tools can send data out of your system (spraay_solana_batch_send_sol and spraay_solana_batch_send_token).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 20, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Can't be undone 2Claude Code: ask
  • spraay_solana_batch_send_solBatch send SOL to multiple Solana wallets in one call.Can send data outNo findings

    Why it is in this group

    • The name "spraay_solana_batch_send_sol" says "send": a word for sending, and what is sent cannot be taken back.
    • The input addresses people (input.recipients): what it sends cannot be taken back.

    What it can reach

    • outboundThe name "spraay_solana_batch_send_sol" says "send": it sends or publishes something to other people.
    • outboundThe input takes a destination (input.recipients): what the tool writes goes there.
    Description, as the server wrote it
    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.
  • spraay_solana_batch_send_tokenBatch send any SPL token (USDC, BONK, WIF, JUP, etc.) to multiple Solana wallets.Can send data outNo findings

    Why it is in this group

    • The name "spraay_solana_batch_send_token" says "send": a word for sending, and what is sent cannot be taken back.
    • The input addresses people (input.recipients): what it sends cannot be taken back.

    What it can reach

    • outboundThe name "spraay_solana_batch_send_token" says "send": it sends or publishes something to other people.
    • outboundThe input takes a destination (input.recipients): what the tool writes goes there.
    Description, as the server wrote it
    Batch send any SPL token (USDC, BONK, WIF, JUP, etc.) to multiple Solana wallets. Auto-creates token accounts. Costs $0.01 USDC via x402.
Only reads 2Show 2 read-only tools
  • spraay_solana_quoteGet a cost estimate for a Spraay batch send on Solana.No findings

    Why it is in this group

    • The description's first verb is "get": a word for reading.
    Description, as the server wrote it
    Get a cost estimate for a Spraay batch send on Solana. Returns fees, tx count, and timing. Costs $0.001 USDC via x402.
  • spraay_solana_statusCheck the status of a Solana transaction by its signature.No findings

    Why it is in this group

    • The name "spraay_solana_status" says "status": a word for reading.
    Description, as the server wrote it
    Check the status of a Solana transaction by its signature. Costs $0.001 USDC via x402.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:09 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 irreversible). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://gateway-solana.spraay.app/mcp: tools/list returned 4 tools to an anonymous client, including spraay_solana_batch_send_sol (irreversible), spraay_solana_batch_send_token (irreversible)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http spraay-solana-gateway https://gateway-solana.spraay.app/mcp
claude mcp add --transport http spraay-solana-gateway https://gateway-solana.spraay.app/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__spraay-solana-gateway__spraay_solana_quote",
      "mcp__spraay-solana-gateway__spraay_solana_status"
    ],
    "ask": [
      "mcp__spraay-solana-gateway__spraay_solana_batch_send_sol",
      "mcp__spraay-solana-gateway__spraay_solana_batch_send_token"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as spraay-solana-gateway. Review it before you use it.

Capability tags behind 2 rules
  • mcp__spraay-solana-gateway__spraay_solana_batch_send_sol outbound
  • mcp__spraay-solana-gateway__spraay_solana_batch_send_token outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.plagtech/spraay-solana-gateway/verify?hash=75c60661ef7a4ecf2606c80b8fc664daaa07d8d82eafa19ffdbdd1cf8d1a14e2" | jq -e '.changed == false'

Pinned hash 75c60661ef7a, from Nov 20, 2026, 08:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.plagtech/spraay-solana-gateway/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.plagtech/spraay-solana-gateway
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.plagtech/spraay-solana-gateway.svg)](https://radar.anlyon.com/servers/io.github.plagtech/spraay-solana-gateway)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:45 UTC.

spraay-solana-gateway MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the spraay-solana-gateway MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the spraay-solana-gateway MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the spraay-solana-gateway MCP server do things that cannot be undone?

Yes. 2 tools can send, pay, publish or merge: spraay_solana_batch_send_sol and spraay_solana_batch_send_token.

What tools does the spraay-solana-gateway MCP server have?

4 tools: 2 irreversible, 2 read. spraay_solana_batch_send_sol, spraay_solana_batch_send_token, spraay_solana_quote and spraay_solana_status.

Does the spraay-solana-gateway MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the spraay-solana-gateway MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): spraay_solana_batch_send_sol and spraay_solana_batch_send_token.

Has the spraay-solana-gateway MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.