GotSOL.app
REMOTE · GOTSOL.APP
USDC wallets, payment links and x402 payments on Solana for AI agents.
Available components
Last scanned (15 hours ago)
Scores higher than 35% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
Checks we ran (5)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
Checks we could not complete (6)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Transport in Transport & Reachability (scores 0 for this)Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Tool safety in Tool Safety (scores 0 for this)Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Capabilities in Capabilities (scores 0 for this)Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 1 Nov 26 −23
- Endpoint reachability: reachable → behind authorisation ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: unverified → pass ▲ security
- First check of Authorization: pass security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 31 Oct 26 62
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://gotsol.app/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=gotsol.app | CN=YR1,O=Let's Encrypt,C=US | 24 Oct 2026 | 22 Jan 2027 | RSA 2048 | SHA256-RSA | 520ada868035879112a2fe7207cd1a786c0 |
| SANs: gotsol.app | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of gotsol.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| gotsol.app. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer realm="gotsol", resource_metadata="https://gotsol.app/.well-known/oauth-protected-resource"
Bearer realm="gotsol", resource_metadata="https://gotsol.app/.well-known/oauth-protected-resource" | Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-eval' 'unsafe-inline' https://*.privy.io https://*.solana.com https://www.googletagmanager.com https://static.hotjar.com https://challenges.cloudflare.com https://maps.googleapis.com https://maps.gstatic.com https://api.mapbox.com https://*.mapbox.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://maps.googleapis.com https://maps.gstatic.com https://api.mapbox.com https://*.mapbox.com; img-src 'self' data: https: blob: https://maps.gstatic.com https://maps.googleapis.com https://api.mapbox.com https://*.mapbox.com; font-src 'self' https://fonts.gstatic.com https://maps.gstatic.com https://api.mapbox.com https://*.mapbox.com; connect-src 'self' https://*.solana.com https://*.helius-rpc.com https://*.helius.xyz https://*.supabase.co https://*.privy.io https://privy.gotsolpay.com https://heroswap.com https://explorer-api.walletconnect.com https://token.jup.ag https://quote-api.jup.ag https://cache.jup.ag https://api.coingecko.com https://*.hot |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(self) |
| www-authenticate | Bearer realm="gotsol", resource_metadata="https://gotsol.app/.well-known/oauth-protected-resource" |
Protected resource metadata
| Document | https://gotsol.app/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://gotsol.app/api/mcp |
| Authorisation server | https://gotsol.app |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://gotsol.app/api/mcp | Auth required | 401 | |
| http (plaintext) | http://gotsol.app/api/mcp | HTTPS enforced | 308 | https://gotsol.app/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_payment_link ~86
Create 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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | USDC amount the payer should send |
| bearerToken | string | – | – |
| memo | string | – | Optional memo shown to the payer |
No output schema declared.
No examples provided.
create_wallet ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotencyKey | string | – | Retry key. The same key returns the same wallet and does not mint a second API key. |
| name | string | – | Label stored with the API key |
No output schema declared.
No examples provided.
get_merchant_goal ~60
Get revenue goal and progress for a merchant. Query by merchantPubkey or merchantId.
| Name | Type | Req | Description |
|---|---|---|---|
| bearerToken | string | – | Optional Bearer token for API auth |
| merchantId | string | – | – |
| merchantPubkey | string | – | – |
No output schema declared.
No examples provided.
get_merchant_metadata ~61
Get metadata for a merchant by their Solana public key (merchantPubkey).
| Name | Type | Req | Description |
|---|---|---|---|
| bearerToken | string | – | Optional Bearer token for API auth (agent can pass its own) |
| merchantPubkey | string | yes | Merchant Solana public key |
No output schema declared.
No examples provided.
get_payment_history ~58
Get payment history for a merchant. Paginated.
| Name | Type | Req | Description |
|---|---|---|---|
| bearerToken | string | – | Optional Bearer token for API auth |
| limit | number | – | – |
| merchant | string | yes | Merchant pubkey |
| page | number | – | – |
No output schema declared.
No examples provided.
get_payment_link ~57
Get one GotSOL.app payment link, including status. Set check to true to look for the on-chain payment.
| Name | Type | Req | Description |
|---|---|---|---|
| bearerToken | string | – | – |
| check | boolean | – | – |
| id | string | yes | Payment link id |
No output schema declared.
No examples provided.
get_profile ~60
Get the profile for the authenticated API key: userId, emails, wallets (Solana and Ethereum), and all merchants (merchantPubkey, merchantName) tied to this account.
| Name | Type | Req | Description |
|---|---|---|---|
| bearerToken | string | – | Optional Bearer token for API auth |
No output schema declared.
No examples provided.
get_usdc_balance ~30
USDC balance of the signed-in GotSOL.app wallet.
| Name | Type | Req | Description |
|---|---|---|---|
| bearerToken | string | – | – |
No output schema declared.
No examples provided.
list_merchant_metadata ~39
List merchants with location data (heatmap) for the authenticated user.
| Name | Type | Req | Description |
|---|---|---|---|
| bearerToken | string | – | Optional Bearer token for API auth |
No output schema declared.
No examples provided.
list_payment_links ~29
List GotSOL.app payment links for the signed-in wallet.
| Name | Type | Req | Description |
|---|---|---|---|
| bearerToken | string | – | – |
No output schema declared.
No examples provided.
list_products ~54
List products for a merchant. Optional search term.
| Name | Type | Req | Description |
|---|---|---|---|
| bearerToken | string | – | Optional Bearer token for API auth |
| merchantPubkey | string | yes | Merchant Solana public key |
| search | string | – | – |
No output schema declared.
No examples provided.
prepare_transfer ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | USDC amount debited from the sender |
| bearerToken | string | – | – |
| from | string | yes | Sender Solana address |
| to | string | yes | Recipient Solana address |
No output schema declared.
No examples provided.
send_usdc ~107
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | USDC amount debited from the sender |
| bearerToken | string | – | – |
| to | string | yes | Recipient Solana address |
No output schema declared.
No examples provided.
How do I install the GotSOL.app MCP server?
GotSOL.app is a hosted endpoint at https://gotsol.app/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · gotsol.app
claude mcp add --transport http app-gotsol-gotsol 'https://gotsol.app/api/mcp'
What is the GotSOL.app MCP server?
GotSOL.app is an MCP server listed in the public MCP registry as app.gotsol/gotsol. USDC wallets, payment links and x402 payments on Solana for AI agents. This page covers its hosted endpoint (https://gotsol.app/api/mcp).
Is the GotSOL.app MCP server safe to use?
GotSOL.app scores 39 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the GotSOL.app MCP server expose?
GotSOL.app exposes 13 tools: get_merchant_metadata, list_merchant_metadata, get_profile, get_merchant_goal, list_products, and 8 more. Their descriptions and schemas cost roughly 842 tokens of context every time the server is loaded.
Does the GotSOL.app MCP server require authentication?
Yes. GotSOL.app asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the GotSOL.app MCP server still maintained?
GotSOL.app is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the GotSOL.app MCP server?
VerifyMCP ran 5 checks on GotSOL.app, covering TLS certificate, Authorization, HTTPS, HSTS header and 1 more. 6 items could not be completed, a gap on our side rather than a finding about GotSOL.app: Transport, Schema quality, Stability, Tool coverage and 2 more. 6 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.