MOSN Solana Safety
by mosn-api.mosn-3r41y.workers.dev in Onchain & crypto
Solana token rug checks and safety-checked Jupiter swaps for AI agents; paid data via x402.
https://mosn-api.mosn-3r41y.workers.dev/mcp- Tools
- 3
- open to any client
- Uptime
- 50.0%
- last 30 days
- Response time
- 448 ms
- 1.1 s slowest 5%
- Last check
- Passed
- 9 h ago, next any minute now
Reliability
Status and outage history · Atom feed · Watch with other listings
How to connect
Add it to any MCP client that supports remote servers.
{
"mcpServers": {
"mosn-solana-safety": {
"type": "http",
"url": "https://mosn-api.mosn-3r41y.workers.dev/mcp"
}
}
}3 tools
- mosn_token_check
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.
- mosn_safe_swap
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.
- mosn_paid_endpoints
List MOSN paid data endpoints (x402, USDC on Solana or Base): fresh screened Solana alpha, real-time new pools, holder checks, labeled memecoin dataset.
Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 9 h ago | Passed | 200 | 741 ms |
| 22 h ago | initialize returned HTTP 503 | 503 | 347 ms |
| 33 h ago | Passed | 200 | 410 ms |
| 44 h ago | Passed | 200 | 539 ms |
| 2 days ago | initialize returned HTTP 503 | 503 | 179 ms |
Show 10 older checks
| 3 days ago | initialize returned HTTP 503 | 503 | 144 ms |
| 3 days ago | Passed | 200 | 552 ms |
| 4 days ago | Passed | 200 | 436 ms |
| 4 days ago | Passed | 200 | 532 ms |
| 5 days ago | initialize returned HTTP 503 | 503 | 183 ms |
| 5 days ago | initialize returned HTTP 503 | 503 | 145 ms |
| 6 days ago | Passed | 200 | 839 ms |
| 7 days ago | initialize returned HTTP 503 | 503 | 228 ms |
| 7 days ago | Passed | 200 | 425 ms |
| 8 days ago | Passed | 200 | 518 ms |