# 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.

- Trust score: 58/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `mosn-api.mosn-3r41y.workers.dev`: 58/100 (this document), [markdown](https://verifymcp.io/servers/dev-workers-mosn-3r41y-mosn-api-mosn/mosn-api.md), [page](https://verifymcp.io/servers/dev-workers-mosn-3r41y-mosn-api-mosn/mosn-api)

## Channel facts

- Endpoint: `https://mosn-api.mosn-3r41y.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.4.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-23.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 284 tokens (~94/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 86/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 57% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http dev-workers-mosn-3r41y-mosn-api-mosn 'https://mosn-api.mosn-3r41y.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-workers-mosn-3r41y-mosn-api-mosn": {
      "url": "https://mosn-api.mosn-3r41y.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-workers-mosn-3r41y-mosn-api-mosn": {
      "type": "http",
      "url": "https://mosn-api.mosn-3r41y.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-workers-mosn-3r41y-mosn-api-mosn]
url = "https://mosn-api.mosn-3r41y.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-workers-mosn-3r41y-mosn-api-mosn": {
      "type": "remote",
      "url": "https://mosn-api.mosn-3r41y.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-workers-mosn-3r41y-mosn-api-mosn --url 'https://mosn-api.mosn-3r41y.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-workers-mosn-3r41y-mosn-api-mosn:
    url: "https://mosn-api.mosn-3r41y.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-workers-mosn-3r41y-mosn-api-mosn": {
      "Transport": "http",
      "Url": "https://mosn-api.mosn-3r41y.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-workers-mosn-3r41y-mosn-api-mosn -t streamable-http -u 'https://mosn-api.mosn-3r41y.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-workers-mosn-3r41y-mosn-api-mosn": {
      "type": "http",
      "url": "https://mosn-api.mosn-3r41y.workers.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-23 (score 58, +40)

- [security regression] HTTPS: unverified → fail
- [security improvement] Injection markers: unverified → pass
- [security improvement] 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.
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.07
- [functional improvement] MCP protocol: unverified → pass

### 2026-10-22 (score 18, −39)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] HTTPS: fail → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → fail
- [security] Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-10-21 (score 57)

First indexed and scored.

## MCP tools (3)

### `mosn_token_check` (~83 tokens)

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.

Input parameters:

- `mint` (string, required): Solana token mint address

### `mosn_safe_swap` (~128 tokens)

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.

Input parameters:

- `amountRaw` (string): For sells: token amount in base units
- `amountSol` (number): For buys: SOL to spend
- `mint` (string, required)
- `side` (string, required)
- `slippageBps` (number)
- `wallet` (string, required): Your Solana wallet public key

### `mosn_paid_endpoints` (~48 tokens)

List MOSN paid data endpoints (x402, USDC on Solana or Base): fresh screened Solana alpha, real-time new pools, holder checks, labeled memecoin dataset.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-workers-mosn-3r41y-mosn-api-mosn/mosn-api#diagnostics

## Score history

- 2026-10-23: 58
- 2026-10-22: 18
- 2026-10-21: 57

## Common questions

### 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.

## Links

- Remote endpoint: https://mosn-api.mosn-3r41y.workers.dev/mcp
- Repository: https://github.com/mosn-agent/mosn-solana-mcp
- Changelog RSS feed: https://verifymcp.io/servers/dev-workers-mosn-3r41y-mosn-api-mosn/mosn-api.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-workers-mosn-3r41y-mosn-api-mosn/mosn-api.json
- HTML version of this page: https://verifymcp.io/servers/dev-workers-mosn-3r41y-mosn-api-mosn/mosn-api