Skip to main content
Glama
kukapay

crypto-pegmon-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_supported_stablecoinsA
Fetch the list of supported USD-pegged stablecoins with their symbols and descriptions.

Returns:
    str: A Markdown-formatted table listing stablecoin symbols and their descriptions.
get_current_priceA
Fetch the current price of a USD-pegged stablecoin in USD and calculate peg deviation.

Args:
    coin (str): The symbol of the stablecoin (e.g., 'usdt', 'usdc', 'dai').

Returns:
    str: A string with the current price and peg deviation in Markdown format.
get_historical_dataA
Fetch historical price data for a USD-pegged stablecoin and return as a Markdown table.

Args:
    coin (str): The symbol of the stablecoin (e.g., 'usdt', 'usdc', 'dai').
    days (int, optional): Number of days for historical data. Defaults to 7.

Returns:
    str: A Markdown table with date, price, and deviation.
analyze_peg_stabilityB
Generate a peg stability analysis report for a USD-pegged stablecoin.

Args:
    coin (str): The symbol of the stablecoin (e.g., 'usdt', 'usdc', 'dai').
    days (int, optional): Number of days for analysis. Defaults to 7.

Returns:
    str: A Markdown-formatted report with historical data, current price, and stability analysis.

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

A3.9/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: analyze_peg_stability generates a comprehensive report, get_current_price provides current price and deviation, get_historical_data returns historical data in table format, and get_supported_stablecoins lists available coins. The descriptions clearly differentiate their functions, making misselection unlikely.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using snake_case: analyze_peg_stability, get_current_price, get_historical_data, and get_supported_stablecoins. The naming is predictable and readable throughout, with no deviations in style or convention.

Tool Count4/5

With 4 tools, the count is reasonable for a stablecoin analysis server, covering core functions like current price, historical data, stability analysis, and coin listing. It's slightly lean but well-scoped; adding tools for alerts or deeper analytics could enhance it without being necessary.

Completeness4/5

The tool surface covers essential operations for stablecoin analysis: listing coins, fetching current and historical data, and generating stability reports. Minor gaps exist, such as lack of update/delete operations or advanced features like alerts, but agents can perform core workflows effectively without dead ends.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources