# Shinjuku Shield (npm · shinjuku-shield) 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-11-05 ## Components - npm · `shinjuku-shield`: 47/100 (this document), [markdown](https://verifymcp.io/servers/shinjukustaition-shinjuku-mcp/shinjuku-shield.md), [page](https://verifymcp.io/servers/shinjukustaition-shinjuku-mcp/shinjuku-shield) ## Channel facts - Registry: `npm` - Package: `shinjuku-shield` - Version: `0.3.131` - 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-11-05. - **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-shield). - 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: 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. - **Stability & Change Management**: 0/100 - 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. - **Tool Coverage**: 0/100 - 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. - **Tool Safety**: 0/100 - 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. - **Capabilities**: 0/100 - 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. **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 Shield MCP server? Shinjuku Shield runs locally as an npm package, launched with npx -y shinjuku-shield mcp --pool CDtxyRjCUs2pu7t3U9TwtpnZwyxBFZ4dKXvb4RCmXHXv --program 8PYPw3FSFTMbvSneXdcoH6jNoN4VD23nHwPY2A2riUy1 --memo-service https://pay.shinjukustaition.com. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation. ### Claude ```bash claude mcp add shinjukustaition-shinjuku-mcp -- npx -y shinjuku-shield mcp --pool CDtxyRjCUs2pu7t3U9TwtpnZwyxBFZ4dKXvb4RCmXHXv --program 8PYPw3FSFTMbvSneXdcoH6jNoN4VD23nHwPY2A2riUy1 --memo-service https://pay.shinjukustaition.com ``` ### Cursor ```json { "mcpServers": { "shinjukustaition-shinjuku-mcp": { "command": "npx", "args": [ "-y", "shinjuku-shield", "mcp", "--pool", "CDtxyRjCUs2pu7t3U9TwtpnZwyxBFZ4dKXvb4RCmXHXv", "--program", "8PYPw3FSFTMbvSneXdcoH6jNoN4VD23nHwPY2A2riUy1", "--memo-service", "https://pay.shinjukustaition.com" ] } } } ``` ### VS Code ```json { "servers": { "shinjukustaition-shinjuku-mcp": { "command": "npx", "args": [ "-y", "shinjuku-shield", "mcp", "--pool", "CDtxyRjCUs2pu7t3U9TwtpnZwyxBFZ4dKXvb4RCmXHXv", "--program", "8PYPw3FSFTMbvSneXdcoH6jNoN4VD23nHwPY2A2riUy1", "--memo-service", "https://pay.shinjukustaition.com" ] } } } ``` ### Codex ```bash codex mcp add shinjukustaition-shinjuku-mcp -- npx -y shinjuku-shield mcp --pool CDtxyRjCUs2pu7t3U9TwtpnZwyxBFZ4dKXvb4RCmXHXv --program 8PYPw3FSFTMbvSneXdcoH6jNoN4VD23nHwPY2A2riUy1 --memo-service https://pay.shinjukustaition.com ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "shinjukustaition-shinjuku-mcp": { "type": "local", "command": [ "npx", "-y", "shinjuku-shield", "mcp", "--pool", "CDtxyRjCUs2pu7t3U9TwtpnZwyxBFZ4dKXvb4RCmXHXv", "--program", "8PYPw3FSFTMbvSneXdcoH6jNoN4VD23nHwPY2A2riUy1", "--memo-service", "https://pay.shinjukustaition.com" ], "enabled": true } } } ``` ### Hermes ```yaml mcp_servers: shinjukustaition-shinjuku-mcp: command: "npx" args: ["-y", "shinjuku-shield", "mcp", "--pool", "CDtxyRjCUs2pu7t3U9TwtpnZwyxBFZ4dKXvb4RCmXHXv", "--program", "8PYPw3FSFTMbvSneXdcoH6jNoN4VD23nHwPY2A2riUy1", "--memo-service", "https://pay.shinjukustaition.com"] ``` ### Netclaw ```json { "McpServers": { "shinjukustaition-shinjuku-mcp": { "Transport": "stdio", "Command": "npx", "Arguments": [ "-y", "shinjuku-shield", "mcp", "--pool", "CDtxyRjCUs2pu7t3U9TwtpnZwyxBFZ4dKXvb4RCmXHXv", "--program", "8PYPw3FSFTMbvSneXdcoH6jNoN4VD23nHwPY2A2riUy1", "--memo-service", "https://pay.shinjukustaition.com" ] } } } ``` ### Other ```json { "mcpServers": { "shinjukustaition-shinjuku-mcp": { "command": "npx", "args": [ "-y", "shinjuku-shield", "mcp", "--pool", "CDtxyRjCUs2pu7t3U9TwtpnZwyxBFZ4dKXvb4RCmXHXv", "--program", "8PYPw3FSFTMbvSneXdcoH6jNoN4VD23nHwPY2A2riUy1", "--memo-service", "https://pay.shinjukustaition.com" ] } } } ``` ## 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-11-03 (score 47, +5) - [security improvement] Source repository: fail → pass ### 2026-11-02 (score 42, −5) - [security regression] Source repository: pass → fail ### 2026-10-31 (score 47, +15) - [security improvement] Malware scan: unverified → pass ### 2026-10-30 (score 32) 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-shield#diagnostics ## Score history - 2026-11-05: 47 - 2026-11-04: 47 - 2026-11-03: 47 - 2026-11-02: 42 - 2026-11-01: 47 - 2026-10-31: 47 - 2026-10-30: 32 ## Common questions ### What is the Shinjuku Shield MCP server? Shinjuku Shield 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-shield). ### Is the Shinjuku Shield MCP server safe to use? Shinjuku Shield scores 47 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 Shield MCP server still maintained? Shinjuku Shield is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced. ### What did VerifyMCP test on the Shinjuku Shield MCP server? VerifyMCP ran 8 checks on Shinjuku Shield, covering Malware scan, Known CVEs, Install scripts, Dependency health and 4 more. 6 items could not be completed, a gap on our side rather than a finding about Shinjuku Shield: License, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out. ## Links - npm package: https://www.npmjs.com/package/shinjuku-shield - Socket report: https://socket.dev/npm/package/shinjuku-shield - Repository: https://github.com/ShinjukuStaition/shinjuku-shield - Website: https://shinjukustaition.com/ - Changelog RSS feed: https://verifymcp.io/servers/shinjukustaition-shinjuku-mcp/shinjuku-shield.xml - Changelog JSON feed: https://verifymcp.io/servers/shinjukustaition-shinjuku-mcp/shinjuku-shield/changelog.json - Trust report (JSON): https://verifymcp.io/servers/shinjukustaition-shinjuku-mcp/shinjuku-shield.json - HTML version of this page: https://verifymcp.io/servers/shinjukustaition-shinjuku-mcp/shinjuku-shield