💊 MCPill – Pumpfun MCP Server

Created By
xaspxa year ago
A Model Context Protocol (MCP) server for interacting with the Pump.fun platform on Solana. This server enables AI assistants to create, buy, and sell tokens on the Pump.fun platform.
Overview

What is MCPill?

MCPill is a Model Context Protocol (MCP) server designed for interacting with the Pump.fun platform on Solana. It allows AI assistants to autonomously create, buy, and sell tokens, enabling fully automated crypto experiences powered by artificial intelligence.

How to use MCPill?

To use MCPill, clone the repository, install dependencies, set up your environment variables, and run the server. You can configure it with your MCP-compatible assistant by adding specific settings to your client configuration.

Key features of MCPill?

  • Launch new tokens on Pump.fun
  • Purchase and sell tokens
  • Query token metadata
  • Manage accounts and balances
  • Supports multiple named accounts for account management

Use cases of MCPill?

  1. Automating the creation and trading of memecoins on the Solana blockchain.
  2. Enabling AI-driven interactions for crypto trading.
  3. Facilitating token management and metadata querying for developers.

FAQ from MCPill?

  • Can MCPill be used with any AI assistant?

Yes! MCPill is compatible with any MCP-compatible AI assistant.

  • Is there a cost to use MCPill?

MCPill is open-source and free to use under the MIT license.

  • What blockchain does MCPill operate on?

MCPill operates on the Solana blockchain, leveraging its capabilities for token transactions.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
xaspx
Star
0
Language
Python
License
AGPL-3.0 license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

10 minutes ago