
Obsd Launchpad
io.github.lordbasilaiassistant-sudoPublished by GitHub account lordbasilaiassistant-sudov1.0.7Updated Oct 24, 2026
MCP server for AI agents to deploy tokens on Base. One command launch, earn OBSD forever.
Overview
Local MCP server that lets an AI agent deploy tokens on the Base network, with a deployer wallet key supplied by the user.
- What you can do
- Deploy tokens on Base from an AI agent session, described as a one-command launch.
- The server is positioned around launching tokens and earning OBSD, but no tool list is published, so the exact operations an assistant can call are not documented.
- Wallet signing is handled through a deployer private key the user provides.
- When to use it
- Consider it only if you specifically want an assistant to launch a token on Base mainnet and you are prepared to hand it a funded deployer wallet key. For general blockchain or crypto work, look for a server with a published tool list.
- Requirements
- Runs as a local stdio process installed from the npm package obsd-launchpad-mcp, on desktop only. Requires the environment variable DEPLOYER_PRIVATE_KEY (a hex private key for the deployer wallet) and optionally RPC_URL for a Base mainnet RPC endpoint. Network access to Base is needed.
Installation
In SourceWeft
- Open Obsd Launchpad in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v1.0.7LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.