Skip to main content
Glama
Sign In
p1xelapp

solana-nft-mcp

by p1xelapp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to solana-nft-mcp

No user-submitted related servers found.

    Related Servers

    • onchain-mcp

      sylvainlondon136
      A
      license
      A
      quality
      D
      maintenance
      Provides read-only access to Solana on-chain data, enabling natural language queries for wallet balances, token holdings, prices, transactions, and more via MCP-compatible clients.
      8
      MIT

    • Corvus

      Allen-Saji
      A
      license
      A
      quality
      D
      maintenance
      Solana DeFi Intelligence MCP server enabling natural language queries for wallet analytics, DeFi positions, protocol metrics, and token prices.
      8
      1
      MIT
    • polskidegen-hl-tracker by polskidegen

      polskidegen-hl-trackerofficial

      polskidegen
      A
      license
      A
      quality
      D
      maintenance
      MCP server for Hyperliquid that provides read-only on-chain wallet analytics. Enables natural-language queries about positions, fills, funding, and realized PnL for any public address.
      8
      4 npm
      MIT

    • PumpPill

      JackedBased
      A
      license
      Not graded
      quality
      B
      maintenance
      Read-only token intelligence for Robinhood Chain and Solana, providing safety checks, ticker resolution, deployer records, whale wallet tracking, and outcome measurements via a hosted MCP server.
      MIT
    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

    A4.2/5.0

    Scored across 21 tools

    Disambiguation4/5

    The descriptions go to unusual lengths to separate tools, explicitly stating when to use one vs another (e.g. get_floor_prices vs get_collection_stats, get_top_traders vs get_collection_sales vs get_collection_holders, get_wallet_holdings/profile/activity). Still, a few pairs genuinely overlap: get_recent_sales vs get_collection_sales both return collection sales, and the three wallet tools share a subject, so an agent could misselect without rereading the fine print.

    Naming Consistency4/5

    Names are uniformly lowercase snake_case and heavily dominated by a verb_noun pattern (get_collection_stats, get_wallet_activity, find_listings). Minor deviations exist: several verbs are synonyms for retrieval (get vs search_collections vs find_in_group), and identify/verify_claim/explain_mechanics drop the noun, but the set remains predictable.

    Tool Count4/5

    At 21 tools the surface is on the heavy side, but the domain genuinely spans collections, wallets, assets, sales, listings, provenance, trust and reference content, and each tool maps to a distinct query type. Nothing looks like filler, though a couple of retrieval tools could conceivably be merged.

    Completeness5/5

    For a deliberately read-only market/intelligence server the coverage is thorough: identification, discovery, floors/stats, listings, sales, holders, per-wallet and per-asset views, on-chain provenance and trust decoding, plus meta-tools (source status, mechanics, integration recipes, claim verification). No obvious lifecycle gap given the stated read-only purpose.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources