Skip to content

GotSOL.app MCP server

app.gotsol/gotsolgotsol.appstreamable-httpv0.1.0Scanned

USDC wallets, payment links and x402 payments on Solana for AI agents.

13 tools: 2 do something that can't be undone, 2 change things and 9 only read.

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

Sign-in required, OAuth metadata published. 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 GotSOL.app MCP server can do

The GotSOL.app MCP server is published by gotsol.app, a domain the MCP Registry verified. It has 13 tools. It can do things that cannot be undone, such as sending, paying or publishing (prepare_transfer and send_usdc) and create or change data (2 tools: create_wallet and create_payment_link), but cannot delete data. 9 tools only read.

1 tool reads private data (get_profile); 1 tool brings in text other people can write (get_profile); 2 tools can send data out of your system (prepare_transfer and send_usdc). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

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

Its remote endpoint asks for sign-in and publishes OAuth metadata.

Last scanned Oct 31, 2026, version 0.1.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.

13 tools

Can't be undone 2Claude Code: ask
  • prepare_transferBuild an unsigned USDC transfer.Can send data outNo findings

    Why it is in this group

    • The name "prepare_transfer" says "transfer": a word for a change that another call does not undo.
    • The input addresses people (input.to): what it sends cannot be taken back.

    What it can reach

    • outboundThe input takes a destination (input.to): what the tool writes goes there.
    Description, as the server wrote it
    Build an unsigned USDC transfer. Recipient receives the amount minus a 0.25% fee. The sender must sign and broadcast it, and that wallet pays the Solana network fee in SOL. Use send_usdc when the network fee should be paid in USDC.
  • send_usdcSend USDC from the GotSOL.app wallet for this API key.Can send data outNo findings

    Why it is in this group

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

    What it can reach

    • outboundThe name "send_usdc" says "send": it sends or publishes something to other people.
    • outboundThe input takes a destination (input.to): what the tool writes goes there.
    Description, as the server wrote it
    Send USDC from the GotSOL.app wallet for this API key. Applies the 0.25% transfer fee through December 31, 2027. The Solana network fee is paid in USDC, so the sender does not need SOL. A missing recipient USDC account is opened in the same send.
Changes things 2Claude Code: ask
  • create_walletOpen a GotSOL.app Solana wallet for this agent.No findings

    Why it is in this group

    • The name "create_wallet" says "create": a word for a change.
    Description, as the server wrote it
    Open a GotSOL.app Solana wallet for this agent. Returns the address and an API key once. No email signup or delegation click. Store the API key and send it as Authorization: Bearer on later calls.
Only reads 9Show 9 read-only tools
  • get_merchant_goalGet revenue goal and progress for a merchant.No findings

    Why it is in this group

    • The name "get_merchant_goal" says "get": a word for reading.
    Description, as the server wrote it
    Get revenue goal and progress for a merchant. Query by merchantPubkey or merchantId.
  • get_merchant_metadataGet metadata for a merchant by their Solana public key (merchantPubkey).No findings

    Why it is in this group

    • The name "get_merchant_metadata" says "get": a word for reading.
    Description, as the server wrote it
    Get metadata for a merchant by their Solana public key (merchantPubkey).
  • get_payment_historyGet payment history for a merchant.No findings

    Why it is in this group

    • The name "get_payment_history" says "get": a word for reading.
    Description, as the server wrote it
    Get payment history for a merchant. Paginated.
  • get_profileGet the profile for the authenticated API key: userId, emails, wallets (Solana and Ethereum), and all merchants (merchantPubkey, merchantName) tied to this account.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_profile" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "get" and "email": it reads mail.
    • untrusted-inputThe description's first sentence says "get" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    Get the profile for the authenticated API key: userId, emails, wallets (Solana and Ethereum), and all merchants (merchantPubkey, merchantName) tied to this account.
  • get_usdc_balanceUSDC balance of the signed-in GotSOL.app wallet.No findings

    Why it is in this group

    • The name "get_usdc_balance" says "get": a word for reading.
    Description, as the server wrote it
    USDC balance of the signed-in GotSOL.app wallet.
  • list_merchant_metadataList merchants with location data (heatmap) for the authenticated user.No findings

    Why it is in this group

    • The name "list_merchant_metadata" says "list": a word for reading.
    Description, as the server wrote it
    List merchants with location data (heatmap) for the authenticated user.
  • list_productsList products for a merchant.No findings

    Why it is in this group

    • The name "list_products" says "list": a word for reading.
    Description, as the server wrote it
    List products for a merchant. Optional search term.

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.

2 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 untrusted-input tool breaks every one.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
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.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__gotsol__get_profile"
    ]
  }
}

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.

Sign-in required, OAuth metadata published

Looked at Nov 15, 2026, 13:21 UTC, unchanged since Nov 8, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
401
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
yes
resource_metadata in WWW-Authenticate
https://gotsol.app/.well-known/oauth-protected-resource
RFC 9728 protected resource metadata
https://gotsol.app/.well-known/oauth-protected-resource
Authorization servers
https://gotsol.app
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes

Posture changes

  1. Nov 8, 2026
    • HTTP status of an anonymous initialize: 200 to 401
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 4 to 0
    • Protocol version: 2025-06-18 to none
    • WWW-Authenticate on 401: not observed to yes
    • resource_metadata in WWW-Authenticate: none to https://gotsol.app/.well-known/oauth-protected-resource
    • RFC 9728 protected resource metadata: none to https://gotsol.app/.well-known/oauth-protected-resource
    • Authorization servers: none to https://gotsol.app
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to yes

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.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 401; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 4 -> 0 (and 7 more).View diff
    • HTTP status of an anonymous initialize: 200 to 401
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 4 to 0
    • Protocol version: 2025-06-18 to none
    • WWW-Authenticate on 401: not observed to yes
    • resource_metadata in WWW-Authenticate: none to https://gotsol.app/.well-known/oauth-protected-resource
    • RFC 9728 protected resource metadata: none to https://gotsol.app/.well-known/oauth-protected-resource
    • Authorization servers: none to https://gotsol.app
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to yes

Install

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

claude mcp add --transport http gotsol https://gotsol.app/api/mcp
claude mcp add --transport http gotsol https://gotsol.app/api/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__gotsol__get_merchant_metadata",
      "mcp__gotsol__list_merchant_metadata",
      "mcp__gotsol__get_profile",
      "mcp__gotsol__get_merchant_goal",
      "mcp__gotsol__list_products",
      "mcp__gotsol__get_payment_history",
      "mcp__gotsol__list_payment_links",
      "mcp__gotsol__get_payment_link",
      "mcp__gotsol__get_usdc_balance"
    ],
    "ask": [
      "mcp__gotsol__create_wallet",
      "mcp__gotsol__create_payment_link",
      "mcp__gotsol__prepare_transfer",
      "mcp__gotsol__send_usdc"
    ],
    "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 gotsol. Review it before you use it.

Capability tags behind 3 rules
  • mcp__gotsol__get_profile private-data, untrusted-input
  • mcp__gotsol__prepare_transfer outbound
  • mcp__gotsol__send_usdc 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/app.gotsol/gotsol/verify?hash=74c70c1eeef366bab4b014aabeb1170f93765016452c25f8b19a6860d6cf2dfb" | jq -e '.changed == false'

Pinned hash 74c70c1eeef3, from Oct 31, 2026, 15:17 UTC.

Watch

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

https://radar.anlyon.com/servers/app.gotsol/gotsol/changes.xml

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

Badge

Anlyon Radar badge for app.gotsol/gotsol
[![Anlyon Radar](https://radar.anlyon.com/badge/app.gotsol/gotsol.svg)](https://radar.anlyon.com/servers/app.gotsol/gotsol)

Source: MCP Registry. Synced Oct 31, 2026, 15:17 UTC.

GotSOL.app MCP server: questions and answers

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

Is the GotSOL.app MCP server safe?

No scan can promise that. What its definitions show: 13 tools, 4 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 GotSOL.app MCP server delete data?

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

Can the GotSOL.app MCP server do things that cannot be undone?

Yes. 2 tools can send, pay, publish or merge: prepare_transfer and send_usdc.

What tools does the GotSOL.app MCP server have?

13 tools: 2 irreversible, 2 write, 9 read. prepare_transfer, send_usdc, create_wallet, create_payment_link, get_merchant_metadata, list_merchant_metadata, get_profile, get_merchant_goal and 5 more.

Does the GotSOL.app MCP server need sign-in or OAuth?

Yes. Its remote endpoint answered 401 without credentials, and it publishes OAuth protected resource metadata (RFC 9728); its authorization server supports dynamic client registration.

Does the GotSOL.app 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): prepare_transfer and send_usdc.

Has the GotSOL.app MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 31, 2026.