
GotSOL MCP server
Which MCP servers are GotSOL's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-31
- Registry nameapp.gotsol/gotsolverified in the MCP registry
The registry name sits under gotsol.app. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-31
- Tools13
- Server calls itselfgotsol-mcp-server
- Server version0.1.0
- Protocol version2025-06-18
On 2026-10-31 the server answered initialize and tools/list without a sign-in. First answer in 164 ms.
- Checked on 4 of the 7 days it takes to judge reliability.
Once connected
- Signs in by OAuth: the client opens the sign-in on first connect.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 4 so far
- Answeredmeasuring4 of the 7 daily checks it takes to print a share
- Median first answer310 ms
- Sign-inOAuth: the client signs you inclients register themselves: claude.ai and ChatGPT connect with nothing set up first
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
get_merchant_metadataGet metadata for a merchant by their Solana public key (merchantPubkey).
list_merchant_metadataList merchants with location data (heatmap) for the authenticated user.
get_profileGet the profile for the authenticated API key: userId, emails, wallets (Solana and Ethereum), and all merchants (merchantPubkey, merchantName) tied to this account.
get_merchant_goalGet revenue goal and progress for a merchant. Query by merchantPubkey or merchantId.
list_productsList products for a merchant. Optional search term.
get_payment_historyGet payment history for a merchant. Paginated.
create_walletOpen 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.
create_payment_linkCreate a GotSOL.app USDC payment link for the signed-in wallet. Returns a pay URL, QR page, and x402 URL. Incoming payments are not charged the 0.25% transfer fee.
list_payment_linksList GotSOL.app payment links for the signed-in wallet.
get_payment_linkGet one GotSOL.app payment link, including status. Set check to true to look for the on-chain payment.
get_usdc_balanceUSDC balance of the signed-in GotSOL.app wallet.
prepare_transferBuild 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. 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…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"gotsol": {
"type": "http",
"url": "https://gotsol.app/api/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http gotsol https://gotsol.app/api/mcpclaude.ai, ChatGPT and other clients: add https://gotsol.app/api/mcp as a custom connector in the settings.
OpenAPI spec
5 paths, read 2026-10-31. Open the spec ↗
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.