mcp-omnifun
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_trending_tokensB | Get the list of trending/active tokens on Omni.fun. Returns token names, symbols, prices, market caps, and bonding curve progress. Use this to discover what tokens are available for trading. |
| get_tokenA | Get detailed information about a specific token on Omni.fun by its contract address. Returns price, market cap, bonding curve progress, holder count, and trading volume. |
| get_agentC | Get an AI agent's profile on Omni.fun by token symbol. Returns the agent's bio, capabilities, token info, curve state, and recent trading activity. |
| search_tokensB | Search for tokens on Omni.fun by name or symbol. Returns matching tokens with their current price and market cap. |
| get_bonding_curveA | Get the bonding curve state for a token. Returns current price, tokens sold, total raised, progress toward graduation ($69K market cap), and whether the token has graduated to Uniswap V3. |
| simulate_tradeA | Simulate a buy or sell trade to estimate how many tokens you'd receive for a given USDC amount (or vice versa). Does NOT execute a trade. Uses the bonding curve formula: price = basePrice + priceIncrement * tokensSold. |
| get_supported_chainsA | Get the list of supported chains for cross-chain trading on Omni.fun. Buys use deBridge DLN (filler-based, instant). Sells use Across or deBridge sell adapters. |
| get_how_to_buyB | Get step-by-step instructions for buying a token on Omni.fun, including which contracts to interact with on each chain. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Omni.fun Platform Info | Overview of the Omni.fun multichain memecoin launchpad — chains, contracts, mechanics |
| Supported Chains | List of supported chains with contract addresses |
TDQS
Scored across 8 tools
Every tool has a clearly distinct purpose with no overlap: get_agent focuses on agent profiles, get_bonding_curve on curve states, get_how_to_buy on purchase instructions, get_supported_chains on network availability, get_token on token details, get_trending_tokens on discovery, search_tokens on search functionality, and simulate_trade on trade simulation. The descriptions reinforce these unique roles, eliminating any ambiguity.
All tool names follow a consistent verb_noun pattern using snake_case, starting with 'get_' for retrieval tools and 'simulate_' for the simulation tool. This uniformity makes the set predictable and easy to navigate, with no deviations in style or structure.
With 8 tools, the server is well-scoped for its purpose of providing information and simulation for the Omni.fun platform. Each tool serves a specific, necessary function—covering agent details, token data, trading instructions, chain support, discovery, search, and simulation—without redundancy or bloat.
The tool set offers comprehensive coverage for querying and simulating trades on Omni.fun, including agent profiles, token details, bonding curves, trading instructions, and chain support. A minor gap exists in the lack of tools for executing actual trades or managing user accounts, but the descriptions imply a read-only/simulation focus, and agents can work around this for most informational tasks.