Skip to main content
Glama
NautilusOSS

UluAlgorandMCP

by NautilusOSS
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to UluAlgorandMCP

No user-submitted related servers found.

    Related Servers

    • UluAlgorandMCP

      MaidToShelly
      A
      license
      A
      quality
      D
      maintenance
      Algorand ecosystem knowledge layer as an MCP server, enabling identification of applications and assets, protocol discovery, name resolution, and protocol summaries without on-chain queries.
      10
      MIT

    • UluCoreMCP

      NautilusOSS
      A
      license
      Not graded
      quality
      D
      maintenance
      Low-level blockchain interface MCP server for Algorand and Voi networks, providing account/asset/app inspection, transaction search, block retrieval, TEAL compilation, and transaction simulation.
      MIT

    • algorand-mcp

      T-WREKX
      A
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive Model Context Protocol (MCP) server providing 50+ tools for Algorand blockchain development, including account management, asset operations, smart contracts, API integration, swap functionality, and advanced transaction capabilities.
      5 npm
      MIT

    • UluVoiMCP

      MaidToShelly
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that provides a semantic layer for the Voi ecosystem, translating raw blockchain data into human-readable information about protocols, applications, and assets. It enables users to identify contract roles, resolve enVoi names, and explore curated registry data for ecosystem services like HumbleSwap and Nautilus.
      10
      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

    A3.9/5.0

    Scored across 10 tools

    Disambiguation4/5

    Tools are mostly distinct: protocol operations are split into list, get, contracts, and summary, and name tools are clearly separated. However, identify_application and get_contract_role overlap since identify_application already returns the role, which could cause misselection.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with snake_case, using verbs like get, identify, resolve, and search. The convention is uniform and predictable across the entire set.

    Tool Count5/5

    10 tools is well within the ideal 3-15 range and fits the server's purpose of providing Algorand protocol, contract, asset, and name lookups. Each tool covers a distinct aspect without unnecessary bloat.

    Completeness4/5

    The surface covers protocol discovery, application/asset identification, contract roles, and name resolution (forward, reverse, search), which is comprehensive for a read-only static registry. Minor gaps exist, such as no direct list-all-assets or list-all-applications, but these are not critical dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources