Skip to main content
Glama
kukapay

solana-launchpads-mcp

by kukapay
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
get_daily_tokens_deployedA
Retrieve the daily count of tokens deployed by Solana memecoin launchpads.

This tool fetches data from a Dune Analytics query and pivots it to show the number of tokens
deployed per day by each platform. Optionally, it can return the data as percentages of the
total daily deployments.

Args:
    return_percent (bool, optional): If True, returns the data as percentages of total daily
        deployments for each platform. Defaults to False.
    limit (int, optional): Maximum number of rows to fetch from the Dune query. Defaults to 1000.

Returns:
    str: A markdown-formatted table of daily token deployments by platform, or an error message
        if the query fails.
get_daily_graduatesA
Fetch the daily number of graduates from Solana memecoin launchpads.

This tool retrieves data from a Dune Analytics query and pivots it to show the number of
successful graduates (e.g., completed token sales or projects) per day by each platform.

Args:
    limit (int, optional): Maximum number of rows to fetch from the Dune query. Defaults to 1000.

Returns:
    str: A markdown-formatted table of daily graduates by platform, or an error message if the
        query fails.
get_daily_graduation_rateA
Fetch the daily graduation rate of Solana memecoin launchpads.

This tool retrieves data from a Dune Analytics query and pivots it to show the graduation rate
(e.g., percentage of projects that successfully complete their goals) per day by each platform.

Args:
    limit (int, optional): Maximum number of rows to fetch from the Dune query. Defaults to 1000.

Returns:
    str: A markdown-formatted table of daily graduation rates by platform, or an error message
        if the query fails.
get_daily_active_addressesA
Fetch the daily count of active wallet addresses interacting with Solana memecoin launchpads.

This tool retrieves data from a Dune Analytics query and pivots it to show the number of unique
active wallets per day by each platform.

Args:
    limit (int, optional): Maximum number of rows to fetch from the Dune query. Defaults to 1000.

Returns:
    str: A markdown-formatted table of daily active wallets by platform, or an error message if
        the query fails.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.2/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: get_daily_active_addresses tracks wallet activity, get_daily_graduates counts successful projects, get_daily_graduation_rate measures success percentages, and get_daily_tokens_deployed monitors token deployments. The descriptions explicitly differentiate these metrics, eliminating any ambiguity.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with 'get_daily_' as a prefix, followed by a specific metric (e.g., active_addresses, graduates). This uniform naming convention makes the tools predictable and easy to understand at a glance.

Tool Count4/5

With 4 tools, the server is well-scoped for its purpose of monitoring Solana memecoin launchpad metrics, though it feels slightly thin. Each tool earns its place by covering distinct aspects of launchpad activity, but additional tools for broader analytics or historical trends could enhance completeness.

Completeness3/5

The tools cover key daily metrics (activity, graduates, rates, deployments) but lack broader operations like historical trends, platform comparisons, or CRUD functionality for managing data. This creates notable gaps that agents might need to work around, limiting the server's utility for comprehensive analysis.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources