MOSN Solana Safety
REMOTE · MOSN-API.MOSN-3R41Y.WORKERS.DEV
Solana token rug checks and safety-checked Jupiter swaps for AI agents; paid data via x402.
Available components
Last scanned (22 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 23 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 Security46
- 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 3 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 check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- 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 Usability63
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 284 tokens (~94/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 57% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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.
- 23 Oct 26 +40
- HTTPS: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.07 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 22 Oct 26 −39
- Endpoint reachability: reachable → not serving MCP ▼ security
- HTTPS: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 21 Oct 26 57
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 23 Oct 2026 · Probed https://mosn-api.mosn-3r41y.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mosn-3r41y.workers.dev | CN=YE1,O=Let's Encrypt,C=US | 14 Oct 2026 | 12 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 543c281da32ea6261572574650d9600afed |
| SANs: *.mosn-3r41y.workers.dev, mosn-3r41y.workers.dev | ||||||
| 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 mosn-api.mosn-3r41y.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mosn-api.mosn-3r41y.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://mosn-api.mosn-3r41y.workers.dev/mcp | Served over HTTP | 200 |
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 →
mosn_paid_endpoints ~48
List MOSN paid data endpoints (x402, USDC on Solana or Base): fresh screened Solana alpha, real-time new pools, holder checks, labeled memecoin dataset.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mosn_safe_swap ~128
Build a Solana token swap that is safety-checked first: MOSN refuses buys into DANGER tokens, then returns an unsigned Jupiter swap transaction for YOUR wallet to sign (MOSN takes a 0.3% platform fee). Free to call.
| Name | Type | Req | Description |
|---|---|---|---|
| amountRaw | string | – | For sells: token amount in base units |
| amountSol | number | – | For buys: SOL to spend |
| mint | string | yes | – |
| side | string | yes | – |
| slippageBps | number | – | – |
| wallet | string | yes | Your Solana wallet public key |
No output schema declared.
No examples provided.
mosn_token_check ~83
Rug/safety check for a Solana token: mint & freeze authority, dangerous Token-2022 settings, real-wallet holder concentration (pools excluded), live sell-route test. Returns SAFE/CAUTION/DANGER with reasons. 5 free checks per day, then use the paid x402 endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| mint | string | yes | Solana token mint address |
No output schema declared.
No examples provided.
How do I install the MOSN Solana Safety MCP server?
MOSN Solana Safety is a hosted endpoint at https://mosn-api.mosn-3r41y.workers.dev/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 · mosn-api.mosn-3r41y.workers.dev
claude mcp add --transport http dev-workers-mosn-3r41y-mosn-api-mosn 'https://mosn-api.mosn-3r41y.workers.dev/mcp'
What is the MOSN Solana Safety MCP server?
MOSN Solana Safety is an MCP server listed in the public MCP registry as dev.workers.mosn-3r41y.mosn-api/mosn. Solana token rug checks and safety-checked Jupiter swaps for AI agents; paid data via x402. This page covers its hosted endpoint (https://mosn-api.mosn-3r41y.workers.dev/mcp).
Is the MOSN Solana Safety MCP server safe to use?
MOSN Solana Safety scores 58 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 MOSN Solana Safety MCP server expose?
MOSN Solana Safety exposes 3 tools: mosn_token_check, mosn_safe_swap, mosn_paid_endpoints. Their descriptions and schemas cost roughly 259 tokens of context every time the server is loaded.
Does the MOSN Solana Safety MCP server require authentication?
No. We connected to MOSN Solana Safety without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the MOSN Solana Safety MCP server still maintained?
MOSN Solana Safety is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.