Skip to main content
Glama
kukapay

nft-analytics-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_trading_volume_by_collectionA
Retrieve daily trading volume for top 5 Ethereum NFT collections.

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

Returns:
    str: Markdown table of daily trading volumes by collection, or error message if the query fails.
get_daily_sales_by_collectionB
Retrieve number of daily sales for NFT collections.

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

Returns:
    str: Markdown table of daily sales counts by collection, or error message if the query fails.
get_average_price_by_collectionC
Retrieve average selling price for NFT collections.

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

Returns:
    str: Markdown table of average prices by collection, or error message if the query fails.
get_unique_traders_by_collectionA
Retrieve count of unique buyers and sellers for NFT collections.

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

Returns:
    str: Markdown table of unique traders by collection, or error message if the query fails.
get_new_ownersB
Retrieve count of new NFT owners.

Returns:
    str: Count of new wallet owners as a string, or "N/A" if no data is available,
         or 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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.5/5.0

Scored across 5 tools

Disambiguation4/5

Most tools have distinct purposes focused on different NFT analytics metrics (average price, daily sales, trading volume, new owners, unique traders), but get_daily_sales_by_collection and get_daily_trading_volume_by_collection could potentially be confused as both relate to daily collection-level activity. The descriptions help clarify, but there's some overlap in their temporal and collection focus.

Naming Consistency5/5

All tools follow a consistent verb_noun_by_collection pattern (get_average_price_by_collection, get_daily_sales_by_collection, etc.), with the exception of get_new_owners which omits 'by_collection' but maintains the same verb_noun structure. This minor deviation doesn't break the overall consistency, making the naming highly predictable and readable.

Tool Count4/5

With 5 tools, the count is reasonable for an NFT analytics server, covering key metrics without being overwhelming. However, it feels slightly thin for a comprehensive analytics suite, as it lacks tools for broader analysis like trends over time or cross-collection comparisons, but it's well within an appropriate range for its focused scope.

Completeness3/5

The toolset covers several important NFT analytics metrics (price, sales, volume, owners, traders), but there are notable gaps. It lacks tools for updating or managing data, historical trend analysis, or filtering by specific parameters beyond collections, which limits the depth of analysis an agent can perform. The surface is functional but incomplete for advanced analytics workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources