MCPX docs

MCPX is being built as a platform where each token powers a real tool. A creator picks a template, configures it and launches a child token paired to native $MCP. The tool then reads Solana data for anyone who uses it.

Six templates are defined across three engines. Every tool is planned to run on demand, when someone asks. There is no continuous monitoring or autonomous alerting.

• WALLETWallet Inspector

  Inspect a wallet's SOL and SPL token balances and its recent transactions. Planned: 10 recent transactions by default, up to 25. USD values optional, always labelled with their source.

• WALLETWhale Watch

  Look up recent activity for a wallet when you ask for it. Planned: choose 10, 25 or 50 recent transactions. Optional filter for transfers or swaps. On-demand only, not continuous alerting or monitoring.

• TOKENToken Scanner

  Inspect a token's mint authority, freeze authority, supply and decimals. Market data shown only where a genuine source supports it. Authority fields reported exactly as stored onchain.

• TOKENSupply Monitor

  Inspect a token's total supply and its largest token accounts. Top token accounts are not the same as unique holders. One person may control several accounts, or one account may be shared.

• VERIFYTX Verifier

  Inspect a transaction signature's confirmation status, errors and slot. “Not found” is reported as not found, never as failed. Shows the error recorded onchain, if any.

• VERIFYAccount Checker

  Check whether an account exists, its owning program, lamports and data size. The owning program is not the human owner of a wallet. Reports existence plainly, without guessing intent.

The builder collects a template, name, ticker, artwork, mission, presets, display style and an optional initial buy in $MCP. One successful launch is meant to produce one verifiable token, one tool configuration, one MCP endpoint and one permanent profile.

$MCP is the native MCPX token. Each tool's child token is intended to be quoted in $MCP rather than SOL, through a custom pairing. $MCP has not been minted, and no contract address exists.

Each child token's eligible, actually collected creator fees are planned to be split:

• 60%Creator
• 25%Tool operations
• 15%Platform

These are shares of fees actually collected, not a fee rate or a share of trading volume. The split is subject to final onchain verification before any launch.

Of the creator fees actually collected on $MCP itself, 60% is planned for holders and 40% for the protocol. The holder portion would be split equally between SOL payouts and $MCP bought with SOL.

This is not live. There is no APY and no guaranteed return.

Each created tool is planned to have its own endpoint in this form:

https://mcp.mcpx.fun/{creation-id}/mcp

This endpoint is planned and not available. Nothing responds at this address today.

Available now: this website, the six template definitions, this documentation, Solana wallet connection (shows your public address only — not a sign-in, nothing is signed), and a read-only registry of verified creations shown on the Paired page.

Not available: token launching, tool execution, MCP endpoints, market listings, creator earnings and $MCP rewards.