Current status
The package’s private-key design also differs from the recommended partner model. A third-party launchpad should let the user’s connected wallet sign so that the user becomes creator and fee recipient.
Supported partner path
Use:- Capabilities to discover the active deployment.
- Launchpad Quickstart for browser-wallet native creation.
- xStocks Launches for per-asset wrapper creation.
- Receipt verification and indexed discovery rather than an editor hot wallet.
If you still run the MCP for legacy testing
- Use a burner wallet with only the needed gas and value.
- Keep writes disabled by default.
- Confirm the exact hook and runtime hash before every write.
- Do not assume its output represents the current active creation deployment.
- Do not place a raw private key in shared editor configuration.
@inkyswap/pump-mcp. Treat any future release as untrusted until its deployment discovery, receipt validation, and supported-chain matrix are documented and tested.