# Shinjuku Shielded (npm · shinjuku-shielded)

Private x402 payments on Solana: shield, pay, and unshield USDC under caps you set.

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

## Components

- npm · `shinjuku-shielded`: 47/100 (this document), [markdown](https://verifymcp.io/servers/shinjukustaition-shinjuku-mcp/shinjuku-shielded.md), [page](https://verifymcp.io/servers/shinjukustaition-shinjuku-mcp/shinjuku-shielded)

## Channel facts

- Registry: `npm`
- Package: `shinjuku-shielded`
- Version: `0.3.49`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-17.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 87/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to ShinjukuStaition/shinjuku-mcp).
  - Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.
  - Actively maintained (last published 0 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.
- **Capabilities**: 0/100
  - Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet.

**Unverified: 5 categories.** Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you.

## Install

### How do I install the Shinjuku Shielded MCP server?

Shinjuku Shielded runs locally as an npm package, launched with npx -y shinjuku-shielded. 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 shinjukustaition-shinjuku-mcp -- npx -y shinjuku-shielded
```

### Cursor

```json
{
  "mcpServers": {
    "shinjukustaition-shinjuku-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "shinjuku-shielded"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "shinjukustaition-shinjuku-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "shinjuku-shielded"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add shinjukustaition-shinjuku-mcp -- npx -y shinjuku-shielded
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "shinjukustaition-shinjuku-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "shinjuku-shielded"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add shinjukustaition-shinjuku-mcp --command npx --arg -y --arg shinjuku-shielded
```

### Hermes

```yaml
mcp_servers:
  shinjukustaition-shinjuku-mcp:
    command: "npx"
    args: ["-y", "shinjuku-shielded"]
```

### Netclaw

```json
{
  "McpServers": {
    "shinjukustaition-shinjuku-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "shinjuku-shielded"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add shinjukustaition-shinjuku-mcp -t stdio -c npx -a -y shinjuku-shielded
```

### Other

```json
{
  "mcpServers": {
    "shinjukustaition-shinjuku-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "shinjuku-shielded"
      ]
    }
  }
}
```

## 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-16 (score 47, 0)

- [security regression] Known CVEs: pass → unverified
- [security] Stability: Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.
- [security] Tool safety: Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.
- [functional regression] Dependency health: pass → unverified
- [functional] Schema quality: Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.
- [functional] Capabilities: Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.
- [functional] Tool coverage: Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.
- [functional] Package version: 0.3.34 → 0.3.49
- [functional] Package version: 0.3.34 → 0.3.48
- [functional] Package version: 0.3.34 → 0.3.47
- [functional] Package version: 0.3.34 → 0.3.46
- [functional] Package version: 0.3.34 → 0.3.43
- [functional] Package version: 0.3.34 → 0.3.39

### 2026-10-15 (score 47, 0)

- [security regression] Known CVEs: pass → unverified
- [security] Stability: Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.
- [security] Tool safety: Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.
- [functional regression] Dependency health: pass → unverified
- [functional] Schema quality: Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.
- [functional] Capabilities: Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.
- [functional] Tool coverage: Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.
- [functional] Package version: 0.3.24 → 0.3.34
- [functional] Package version: 0.3.24 → 0.3.31
- [functional] Package version: 0.3.24 → 0.3.28
- [functional] Package version: 0.3.24 → 0.3.27
- [functional] Package version: 0.3.24 → 0.3.26
- [functional] Package version: 0.3.24 → 0.3.25

### 2026-10-14 (score 47, +11)

- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → pass
- [functional] Package version: 0.3.18 → 0.3.24
- [functional] Package version: 0.3.18 → 0.3.23
- [functional] Package version: 0.3.18 → 0.3.21
- [functional] Package version: 0.3.18 → 0.3.19

### 2026-10-13 (score 36, −11)

- [security regression] Known CVEs: pass → unverified
- [functional regression] Dependency health: pass → unverified
- [functional] Package version: 0.3.8 → 0.3.18
- [functional] Package version: 0.3.8 → 0.3.16
- [functional] Package version: 0.3.8 → 0.3.15

### 2026-10-12 (score 47)

First indexed and scored.

## MCP tools (0)

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/shinjukustaition-shinjuku-mcp/shinjuku-shielded#diagnostics

## Score history

- 2026-10-17: 47
- 2026-10-16: 47
- 2026-10-15: 47
- 2026-10-14: 47
- 2026-10-13: 36
- 2026-10-12: 47

## Common questions

### What is the Shinjuku Shielded MCP server?

Shinjuku Shielded is an MCP server listed in the public MCP registry as io.github.ShinjukuStaition/shinjuku-mcp. Private x402 payments on Solana: shield, pay, and unshield USDC under caps you set. This page covers its npm package (shinjuku-shielded).

### Is the Shinjuku Shielded MCP server safe to use?

Shinjuku Shielded scores 47 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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.

### Is the Shinjuku Shielded MCP server still maintained?

Shinjuku Shielded is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- npm package: https://www.npmjs.com/package/shinjuku-shielded
- Socket report: https://socket.dev/npm/package/shinjuku-shielded
- Repository: https://github.com/ShinjukuStaition/shinjuku-mcp
- Website: https://shinjukustaition.com/
- Changelog RSS feed: https://verifymcp.io/servers/shinjukustaition-shinjuku-mcp/shinjuku-shielded.xml
- Changelog JSON feed: https://verifymcp.io/servers/shinjukustaition-shinjuku-mcp/shinjuku-shielded.json
- HTML version of this page: https://verifymcp.io/servers/shinjukustaition-shinjuku-mcp/shinjuku-shielded