Skip to main content
Glama
Dekalabs

Peppermint MCP Server

by Dekalabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Peppermint MCP Server

No user-submitted related servers found.

    Related Servers

    • Tatum MCP Server by tatumio

      Tatum MCP Serverofficial

      tatumio
      A
      license
      B
      quality
      C
      maintenance
      Provides access to Tatum's blockchain API across 40+ networks, enabling developers to interact with blockchain data, manage notifications, estimate fees, access RPC nodes, and work with smart contracts through natural language.
      31
      87 npm
      15
      MIT
    • NFTGo MCP Server by NFTGo

      NFTGo MCP Serverofficial

      NFTGo
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides access to NFTGo's Developer API for retrieving NFT collection details, asset information, market data, wallet information, and search capabilities on the Ethereum blockchain.
      2 npm
      5
      MIT

    • Algorand MCP Server

      Algodev-Studio
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides 50+ tools for comprehensive Algorand blockchain development including account management, asset operations, smart contracts, atomic transactions, swap functionality via Pera Swap, and semantic search through Algorand documentation.
      11 npm
      1
      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

    B3.2/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools have clear, distinct purposes (auth, blockchains, contracts, transactions, vaults, tokens). A few near-boundaries exist, e.g., create_token vs deploy_contract, but descriptions clarify the difference.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (get_, list_, create_, deploy_, read_, write_, mint_, burn_, transfer_). No mixed conventions or vague names.

    Tool Count4/5

    18 tools is on the higher side but appropriate given the broad scope covering blockchains, contracts, transactions, vaults, and tokens. Each tool addresses a distinct operation, though a few could be consolidated without loss.

    Completeness4/5

    The surface covers core operations for auth, blockchain info, contract lifecycle (deploy/read/write), transactions, vaults, and token management. Missing native token transfers or wallet balance queries are minor gaps given the token/contract focus.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources