A MCP server for Bonk
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"iflow-mcp-letsbonk-ai-bonk-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# bonk-mcp MCP server The bonk-mcp server implements Solana blockchain functionality for the LetsBonk launchpad. ## Features - Token launching: launch any token on letsbonk.fun - Token trading: buy/sell any token on letsbonk.fun ## Configuration The bonk-mcp server can be configured in Claude Desktop by adding it to the MCP servers configuration. You'll need to provide: - Path to the bonk-mcp directory - Environment variables: - `KEYPAIR`: Your Solana keypair - `RPC_URL`: Solana RPC endpoint (e.g., https://api.mainnet-beta.solana.com) ## Quickstart ### Install #### Claude Desktop On MacOS: `~/Library/Application\ Support/Claude/claude_desktop_config.json` On Windows: `%APPDATA%/Claude/claude_desktop_config.json` <details> <summary>Development/Unpublished Servers Configuration</summary> ```json "mcpServers": { "bonk-mcp": { "command": "uv", "args": [ "--directory", "<PATH_TO_BONK_MCP_DIRECTORY>/bonk-mcp", "run", "bonk-mcp" ], "env": { "KEYPAIR": "<YOUR_SOLANA_KEYPAIR>", "RPC_URL": "https://api.mainnet-beta.solana.com" } } } ``` </details> <details> <summary>Published Servers Configuration</summary> ```json "mcpServers": { "bonk-mcp": { "command": "uvx", "args": [ "bonk-mcp" ], "env": { "KEYPAIR": "<YOUR_SOLANA_KEYPAIR>", "RPC_URL": "https://api.mainnet-beta.solana.com" } } } ``` </details> ## Development ### Building and Publishing To prepare the package for distribution: 1. Sync dependencies and update lockfile: ```bash uv sync ``` 2. Build package distributions: ```bash uv build ``` This will create source and wheel distributions in the `dist/` directory. 3. Publish to PyPI: ```bash uv publish ``` Note: You'll need to set PyPI credentials via environment variables or command flags: - Token: `--token` or `UV_PUBLISH_TOKEN` - Or username/password: `--username`/`UV_PUBLISH_U…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.