1. Introduction
The token economy has made launching digital assets easier than ever. Yet most tokens remain disconnected from meaningful products, applications or ongoing utility.
At the same time, artificial intelligence is changing how software is built and consumed. Applications are becoming modular, tools are becoming callable by AI agents, and the Model Context Protocol (MCP) is creating new ways for intelligent systems to interact with external capabilities.
MCPX brings these worlds together.
MCPX is a Solana-based platform that connects token creation with functional software. Instead of launching a token with little more than a name, image and ticker, creators can launch a token linked to a working application and an MCP-compatible endpoint.
The long-term vision extends beyond a curated collection of tools.
MCPX aims to become an open marketplace for MCP-powered applications, where developers contribute capabilities, token creators launch products using those capabilities, and revenue can be shared across the ecosystem.
Our ambition is to create a continuously expanding library of useful, entertaining and experimental applications that can be discovered, launched, used and monetised.
2. The Problem
Tokens without products
Traditional token launchpads make asset creation accessible but generally leave product development to the creator.
The result is an ecosystem where launching a token is easy, but delivering a working application is substantially harder.
Developers without distribution
Independent developers can build valuable AI tools, blockchain utilities and MCP services, but face significant challenges in distribution, monetisation and attracting users.
A useful tool may never reach an audience.
Fragmented application infrastructure
Launching an application can require separate systems for hosting, APIs, authentication, interfaces, usage tracking, payments and distribution.
These barriers prevent many ideas from becoming usable products.
Limited participation in tool success
In traditional software marketplaces, developers may receive a one-time payment or subscription revenue, but cannot necessarily participate in the economic activity that emerges when other creators build products using their work.
MCPX seeks to introduce alternative models of attribution and revenue sharing.
3. The MCPX Solution
MCPX combines five core components:
An expanding MCP Library
A discoverable marketplace of ready-to-use MCP capabilities, AI applications, blockchain utilities and experimental software.
Token-linked applications
Creators select a template, configure their product and launch a token linked to an executable application.
Interactive product interfaces
Every supported product provides a web interface so visitors can use the application directly rather than receiving only a technical API endpoint.
MCP connectivity
Products expose supported capabilities through MCP-compatible endpoints for AI agents, developers and external clients.
Revenue participation
MCPX aims to support transparent economic relationships between application developers, token creators and the wider ecosystem.
Together, these components turn token creation into an entry point for software distribution.
4. The MCP Marketplace
The long-term objective is to transform MCPX from a platform-curated library into a community-powered marketplace.
Independent developers will be able to submit eligible MCP applications for review and inclusion.
Approved submissions will become discoverable templates that other users can select when launching token-linked products.
A single application could potentially power multiple independently launched tokens, with each product maintaining its own identity, creator, configuration and activity history.
Developer participation
Developers will be able to:
- Submit MCP tools or approved application packages.
- Define supported capabilities and input/output schemas.
- Provide a suitable interactive user experience.
- Maintain and update their applications.
- Track adoption across token-linked products.
- Receive an attributable share of eligible revenue under published marketplace terms.
Creator participation
Token creators will be able to:
- Browse and compare available MCP applications.
- Select an application to power a new token.
- Configure supported settings.
- Launch a token using the MCPX launch infrastructure.
- Receive a public product page and executable MCP endpoint.
- Manage the resulting application through their creator dashboard.
Marketplace standards
Community submissions will need to satisfy security, reliability, compatibility and cost requirements.
MCPX will not automatically execute arbitrary unreviewed code submitted by third parties.
The marketplace will require defined review, approval, permission and versioning processes before community software is made available for token launches.
5. A New Model for Developer Revenue
A central principle of MCPX is that developers who create useful applications should be able to participate in the economic value those applications generate.
Rather than simply listing software, MCPX aims to connect application adoption to transparent revenue attribution.
Potential revenue sources include:
- Eligible creator fees associated with token-linked applications.
- Paid application execution and usage.
- Premium capabilities or metered access.
- Future marketplace services.
A developer's revenue entitlement must be defined by the applicable product terms and verifiable accounting rules.
The specific developer share, its funding source, settlement currency and payout timing will be established before marketplace monetisation is activated.
The goal is simple: developers build the applications, creators bring them to market, and both can participate in their success.
6. The $MCP Ecosystem
$MCP is the native token at the centre of the MCPX ecosystem.
The platform is designed around token-linked applications and a native-token economic model.
Native token rewards
MCPX's defined native-token creator-fee allocation model is:
- 30% — SOL allocations for eligible $MCP holders.
- 30% — $MCP buybacks and token distributions.
- 40% — Other allocations under the platform's defined Treasury model.
The system uses five-minute UTC accounting windows.
Allocations are based on fees actually collected and must remain distinguished from confirmed onchain distributions.
Child-token ecosystem
Tokens launched through MCPX are designed to pair with $MCP under the platform's custom-pair launch model.
The existing child-token creator-fee allocation framework is:
- 60% — Creator allocation.
- 25% — Operations allocation.
- 15% — Platform allocation.
The future community-developer revenue model must be reconciled with this framework transparently, without double-counting fees or presenting new percentages as already implemented.
7. Applications, Not Just Endpoints
MCPX applications are designed to serve both human users and software agents.
Each supported token-linked product provides two complementary interfaces:
Use Tool
A browser-based application with appropriate controls, inputs, readable results and real execution.
Connect via MCP
A programmatic interface that allows compatible AI clients and developers to access the same underlying capabilities using supported authentication and usage policies.
This dual-interface approach is intended to expand the audience for every application.
A blockchain analysis tool can serve an individual investor through a visual interface and an AI agent through its MCP endpoint.
An entertainment application can serve casual visitors through a playful interface while remaining callable by other software.
The same capability can support multiple forms of interaction.
8. Application Categories
The MCPX Library is designed to support a broad range of software, including:
Onchain Intelligence
Wallet inspection, token analysis, holder intelligence, blockchain reporting and related tools.
Entertainment & Experimental AI
AI-powered personalities, comedy tools, creative generators and novel interactive experiences.
AI Playground
Creative applications including fictional storytelling, Web3 idea generation, character creation and interactive AI experiences.
Community Applications
Future developer-submitted tools across additional categories including research, productivity, data, creativity, automation and developer services.
MCPX does not intend to restrict its library to blockchain analytics.
Its goal is to support a diverse marketplace of applications wherever supported execution, security and economics make them practical.
9. Infrastructure and Trust
The MCPX platform uses Solana for token-linked transactions and relies on existing execution and data services for its applications.
The platform's core requirements include:
- Verifiable token and product association.
- Secure wallet authentication.
- Controlled transaction construction.
- Product-level access credentials.
- Application execution limits.
- Secure API credential handling.
- Reliable usage and revenue accounting.
- Operational monitoring and failure recovery.
- Transparent distinction between accrued, allocated and paid amounts.
Future community applications will require additional isolation, review and lifecycle controls.
MCPX aims to make application execution trustworthy without requiring token creators to assemble an entire software infrastructure themselves.
10. Roadmap
Foundation — Token-Powered Applications
Establish the Solana launch infrastructure, curated MCP Library, interactive product interfaces, product endpoints and creator dashboard.
Expansion — Growing the Library
Broaden AI, onchain and experimental templates while improving usability, external MCP interoperability and application reliability.
Marketplace — Community Submissions
Introduce reviewed third-party MCP submissions, developer identities, submission management and application versioning.
Revenue Marketplace — Developer Participation
Enable developer attribution, revenue rules, transparent accounting and eligible distributions connected to application adoption and use.
Ecosystem — Scale and Discovery
Develop richer marketplace discovery, application reputation, developer analytics, usage-based services and broader integration opportunities.
These roadmap items describe product direction, not guaranteed delivery dates.
11. The Long-Term Vision
MCPX aims to become a destination for discovering, launching and monetising token-powered applications.
We envision a marketplace where thousands of applications can exist, each capable of powering independent token-linked products.
Some will be practical. Some will be experimental. Some will be deliberately ridiculous.
What matters is that they work.
A developer should be able to build something useful, contribute it to the marketplace and participate when creators use it.
A creator should be able to launch a token with an application without building the entire product infrastructure from scratch.
A user should be able to visit a token page and immediately interact with something real.
And an AI agent should be able to connect to the same application through a standardised interface.
MCPX is building towards an open economy of token-powered applications.
Launch a token. Make it useful.
Draft status: This whitepaper describes the existing MCPX product direction alongside proposed future marketplace capabilities. Community submissions and developer revenue sharing are not represented as live functionality. Economic parameters, operational availability and roadmap details require confirmation before publication.