What problem does it solve? Launching a token on pump.fun requires a metadata URI pointing to IPFS-hosted JSON containing the token's name, symbol, and image. Manually uploading images and metadata JSON to IPFS and wiring the resulting CID into the launch flow is error-prone and slows down coordinated launches. ## Core Features & Use Cases - Image and metadata upload: Uploads a local PNG/JPG/WebP image plus a metadata JSON (name, symbol, optional description and social links) to pump.fun's IPFS endpoint. - URI output for launch flows: Prints a https://ipfs.io/ipfs/<CID> URI ready to pass as the URI env var to fire-jito.js or fire-atomic-create.js. - Pre-flight endpoint check: Verifies pump.fun's IPFS endpoint is reachable before a coordinated launch. - Use Case: Before launching a token called PumpKitty, upload its logo and metadata, capture the returned IPFS URI, and feed it directly into the atomic launch script. ## Quick Start Upload my token metadata with name PumpKitty, symbol KITTY, and the image at ./pumpkitty.png to pump.fun IPFS and give me the URI for the launch.