Skip to main content
Glama
Sifu213

Monad NFT Analytics MCP

by Sifu213
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Local

Monad MCP Magic Eden

This project allows you to create an MCP server that interacts with various APIs to retrieve NFT-related data on the Monad testnet. The MCP server provides several tools:

  • Retrieve the list of holder addresses for an NFT contract -Calculate the total NFT value held by an address using floor prices

  • List all NFT collections that an address holds

  • Get the top-selling collections by number of sales (5 min, 10 min, 30 min, 1 h, 6 h, 24 h, 1 d, 7 d, 30 d)

  • Get the top-selling collections by volume (5 min, 10 min, 30 min, 1 h, 6 h, 24 h, 1 d, 7 d, 30 d)

Prerequisites

  • Node.js (v16 or later)

  • npm

  • Claude Desktop

Related MCP server: Monad MCP

Getting Started

  1. Clone this repository

git clone https://github.com/Sifu213/monad-mcp-magiceden.git

  1. Install dependencies:

npm install

  1. Add a Thirdweb client key :

Get an Thirdweb client key to be able to use the list of holders for a NFT collection by creating a project and make the origin allowance to *. Add you api client key in the nft-owners.ts file on line :

const THIRDWEB_CLIENT_ID = "yourclientkey";

  1. Build the project

npm run build

The server is now ready to use!

Adding the MCP server to Claude Desktop

  1. Open "Claude Desktop"

  2. Open Settings

Claude > Settings > Developer

  1. Open claude_desktop_config.json

  2. Add details about the MCP server and save the file. Use your machine absolute path to the js files resulting from the build

{
    "mcpServers": {
		"top-selling-collections": {
            "command": "node",
            "args": ["*absolutepath*\\dist\\top-selling-collections.js"]
        },
		"top-volume-collections": {
            "command": "node",
            "args": ["*absolutepath*\\dist\\top-volume-collections.js"]
        },
        "collections": {
            "command": "node",
            "args": ["*absolutepath*\\dist\\user-collection.js"]
        },
        "totalValue": {
            "command": "node",
            "args": ["*absolutepath*\\dist\\user-nft-value.js"]
        },
		"nft-owners": {
            "command": "node",
            "args": ["*absolutepath*\\dist\\nft-owners.js"]
        }
    }
}

  1. Restart "Claude Desktop" and make sure it's a hard restart

All the MCP tools may be availables

final result

Here's the final result

Using the MCP server for holders adress for an Nft collection

final result

Using the MCP server for User Nft value

final result

Using the MCP server for User Nft collection

final result

Using the MCP server for getting the trendng NFT collection by volume

final result

Using the MCP server for getting the trendng NFT collection by number of sales

final result

Available Tools

1 tool
get-top-selling-collectionsC

Retrieve top selling NFT collections on Magic Eden testnet

ParametersJSON Schema
NameRequiredDescriptionDefault
periodYesMagic Eden user address on Monad testnet

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions retrieving data but lacks details on rate limits, authentication needs, response format, or any side effects. This leaves significant gaps in understanding how the tool behaves in practice.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, direct sentence that efficiently conveys the core function without unnecessary words. It is appropriately sized for a simple tool, though it could be slightly more structured by including key details like output format or usage context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is incomplete. It does not explain what the tool returns, potential errors, or behavioral traits like performance or limitations. For a tool with no structured support, the description should provide more context to be fully helpful.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 100%, with the parameter 'period' documented in the schema. The description does not add any meaning beyond the schema, such as explaining what 'period' represents or valid values. However, with high schema coverage, the baseline score of 3 is appropriate as the schema handles the parameter documentation adequately.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Retrieve') and resource ('top selling NFT collections on Magic Eden testnet'), making the purpose understandable. However, with no sibling tools mentioned, it cannot demonstrate differentiation from alternatives, which prevents a score of 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, prerequisites, or constraints. It merely states what the tool does without context for its application, leaving usage unclear beyond the basic function.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool update
    • First observedget-top-selling-collections
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.1/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool has a clear, distinct purpose focused on retrieving top-selling NFT collections.

Naming Consistency5/5

The single tool follows a consistent verb_noun pattern (get-top-selling-collections), which is clear and descriptive. With only one tool, naming consistency is inherently perfect.

Tool Count2/5

A single tool is too few for a server labeled 'NFT Analytics MCP', which implies a broader scope of analytics operations. This feels thin and incomplete for the apparent domain.

Completeness2/5

The tool surface is severely incomplete for NFT analytics. It only retrieves top-selling collections, missing essential operations like collection details, sales trends, wallet analysis, or market data, which are expected in this domain.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • Monad MCP Server

    monad-vibe
    A
    license
    A
    quality
    D
    maintenance
    A Model Context Protocol server that enables AI models to interact with the Monad testnet for checking token balances, sending transactions, and deploying smart contracts.
    7
    Apache 2.0

  • Monad MCP

    bble
    F
    license
    B
    quality
    D
    maintenance
    An MCP server that allows querying MON token balances and NFT counts on the Monad testnet, enabling Claude Desktop to interact with the Monad blockchain.
    2
    -
  • Blockscout MCP Server by blockscout

    Blockscout MCP Serverofficial

    blockscout
    F
    license
    A
    quality
    B
    maintenance
    A server that exposes blockchain data (balances, tokens, NFTs, contract metadata) via the Model Context Protocol, enabling AI agents and tools to access and analyze blockchain information contextually.
    18
    45
    -

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Sifu213/monad-mcp-magiceden'

If you have feedback or need assistance with the MCP directory API, please join our Discord server