sol-defi-desk
REMOTE · 95.216.126.169.SSLIP.IO
Paid Solana token safety checks over Streamable HTTP MCP (x402 USDC on Solana + Base).
Available components
Last scanned (14 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 22 Oct 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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 403 tokens (~80/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 0
- Schema quality: 72 → 80 ▼ functional
- New tool “base_token_check” functional
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 30. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 23. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
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 22 Oct 2026 · Probed https://95.216.126.169.sslip.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=95.216.126.169.sslip.io | CN=YE1,O=Let's Encrypt,C=US | 2 Oct 2026 | 31 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6351c3b66e1c5b5c0c433e78c0827dbeb4f |
| SANs: 95.216.126.169.sslip.io | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of 95.216.126.169.sslip.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| sslip.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://95.216.126.169.sslip.io/mcp | Verified | 200 | |
| http (plaintext) | http://95.216.126.169.sslip.io/mcp | HTTPS enforced | 301 | https://95.216.126.169.sslip.io/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 →
base_token_check ~112
Paid ($0.01 USDC via x402): Base ERC-20 rug/honeypot-risk pre-check from direct on-chain reads (owner/renounced, proxy, privileged functions, owner %, Uniswap v2/v3 + Aerodrome liquidity, LP burned %, riskLevel). No sell simulation. Failed lookups are not settled. Also free on this origin: /shop/ /sponsor /ledger.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | Base ERC-20 token contract address (0x…) |
No output schema declared.
No examples provided.
describe_paid_api ~42
FREE: buyer-facing summary of sol-defi-desk HTTP + MCP paid tools plus same-origin print shop /sponsor /ledger (openly AI operator Survivor).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mint_preflight ~53
FREE: validate Solana mint base58 shape and note known issuer assets. No RPC. Use before paying for token_check.
| Name | Type | Req | Description |
|---|---|---|---|
| mint | string | yes | Candidate SPL or Token-2022 mint address (base58) |
No output schema declared.
No examples provided.
token_check ~107
Paid ($0.005 USDC via x402): Solana token safety check from direct on-chain reads (mint/freeze authority, Token-2022 risk extensions, metadata mutability, holder concentration, heuristic riskLevel). Failed lookups are not settled. Also free on this origin: /shop/ ($3 USDC Solana Pay print shop), /sponsor tips, /ledger.
| Name | Type | Req | Description |
|---|---|---|---|
| mint | string | yes | Solana SPL or Token-2022 mint address (base58) |
No output schema declared.
No examples provided.
token_check_batch ~89
Paid ($0.01 USDC fixed via x402): batch Solana token safety checks for 1–5 mints. Same fields as token_check per mint. Also free on this origin: /shop/ ($3 USDC Solana Pay print shop), /sponsor tips, /ledger.
| Name | Type | Req | Description |
|---|---|---|---|
| mints | string | yes | Comma-separated base58 mint addresses (1–5) |
No output schema declared.
No examples provided.
How do I install the sol-defi-desk MCP server?
sol-defi-desk is a hosted endpoint at https://95.216.126.169.sslip.io/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 · 95.216.126.169.sslip.io
claude mcp add --transport http io-sslip-169-126-216-95-sol-defi-desk 'https://95.216.126.169.sslip.io/mcp'
What is the sol-defi-desk MCP server?
sol-defi-desk is an MCP server listed in the public MCP registry as io.sslip.169.126.216.95/sol-defi-desk. Paid Solana token safety checks over Streamable HTTP MCP (x402 USDC on Solana + Base). This page covers its hosted endpoint (https://95.216.126.169.sslip.io/mcp).
Is the sol-defi-desk MCP server safe to use?
sol-defi-desk scores 73 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 sol-defi-desk MCP server expose?
sol-defi-desk exposes 5 tools: mint_preflight, describe_paid_api, token_check, token_check_batch, base_token_check. Their descriptions and schemas cost roughly 403 tokens of context every time the server is loaded.
Does the sol-defi-desk MCP server require authentication?
No. We connected to sol-defi-desk without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the sol-defi-desk MCP server still maintained?
sol-defi-desk is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.