justi-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JUSTI_API_KEY | No | Optional API key for higher rate limits | |
| JUSTI_API_URL | No | The URL of the justi.fun API (default: the production API) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| justi_list_coinsA | List coins launched on justi.fun (a Solana launchpad on Meteora), newest first by default. Search by ticker or name with q, or pass an exact mint. Sort by new, marketcap, volume24h, lastTrade, progress or trades. Returns compact rows and nextCursor for paging. |
| justi_get_coinA | Full detail of one coin by mint: name, ticker, description, socials, fee split, safety facts (mint and freeze authority, metadata, LP lock), bonding curve progress, graduation and DAMM v2 pool, sniper window, totals. |
| justi_protocol_infoA | What justi.fun is and how it works on chain: Meteora DBC program, the 20 fee-tier configs, fee claimer, lookup table, how to tell a coin is from justi.fun, every fee split, the 5 second sniper window schedule, dev buy cap, copy rule, holder rewards and graduation. Use this before explaining fees or building a launch. |
| justi_quoteA | Quote a trade on a justi.fun coin (bonding curve before graduation, Meteora DAMM v2 after). For a buy give amountSol, for a sell give amountTokens (whole tokens) or amountRaw. Returns expected and minimum output, price impact, the fee and where it goes (creator, holders, burns, Meteora). |
| justi_build_swapA | Build an unsigned Solana v0 transaction that buys or sells a justi.fun coin for a wallet. Nothing is signed or sent: the user's wallet must sign it. The server quotes fresh, simulates, and sets the compute limit and priority fee. Returns swapId, the base64 transaction, the quote and how to submit. |
| justi_build_launchA | Build the create transaction for a new coin on justi.fun, with the same rules as the site (fee tiers, 5 second sniper window, dev buy cap of 15% of supply, copy rule, 10 launches per wallet per day). The creator wallet must sign it; nothing is sent. mode: creator (creator earns 0 to 2.5%), holders (holders earn 0.5% in SOL), split (0.5% holders plus creator 0.25 to 2%). Without customMint the server picks a ...JUST vanity mint and signs that slot. |
| justi_recent_tradesA | Trades of one justi.fun coin, newest first, on the curve and on DAMM v2 after graduation. Filter by side or wallet. Amounts in SOL and whole tokens. |
| justi_platform_statsA | Platform-wide totals of justi.fun: coins launched, volume, fees, holder payouts, burns. |
| justi_tx_statusA | Status of any Solana signature (pending, confirmed, finalized, failed, unknown), and the swap or launch it belongs to when it was built through justi.fun. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool has a clearly distinct resource and action: stats, transaction status, recent trades, coin listing, coin detail, protocol info, quote, swap building, and launch building. The only potential overlap is quote versus build_swap, but quote is explicitly read-only while build_swap constructs an unsigned transaction, so the boundary is clear.
All tools share the predictable justi_ prefix and snake_case style, with mostly verb_noun names such as list_coins, get_coin, build_swap, and build_launch. A few names are noun phrases like platform_stats, tx_status, protocol_info, and quote, which is a minor deviation but still readable and consistent enough.
Nine tools is well-scoped for a launchpad trading and launch-building server, with each tool covering a distinct part of the workflow. There is no obvious redundancy or missing slot that would justify adding or removing tools.
The surface covers the core lifecycle: protocol explanation, coin discovery and detail, quotes, transaction building for swaps and launches, transaction status, trade history, and platform stats. Minor gaps exist around wallet-centric views such as a wallet's coin holdings or creator fee claims, but these are not blockers for the stated read-and-build workflow.