Skip to main content
Glama
Sign In
Nodit MCP Server

Nodit MCP Server

Official
by noditlabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Nodit MCP Server

No user-submitted related servers found.

    Related Servers

    • onchain-data-mcp

      madlabs-tech
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to access live blockchain data across multiple networks, including wallet holdings, payment verification, token prices, swaps, and scam checks.
      MIT

    • chain-data

      Baneado98
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to fetch live multi-chain portfolio, token info, gas prices, and token prices across Ethereum, Base, Polygon, Arbitrum, and Optimism with a single call. No API key required.
      4
      MIT

    • evmcp

      siriuslattice
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to query on-chain data across EVM chains like Base, Optimism, Avalanche, Celo, and Arbitrum, including balances, transactions, gas, and smart contract interactions.
      49 npm
      MIT

    • mcp-blockscout

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying on-chain data (balances, transactions, token transfers, blocks) across 20+ EVM chains through natural language.
      149 npm
      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 11 tools

    Disambiguation3/5

    There are five listing tools (node, data, webhook, multichain, categories, aptos query roots) that all sound like 'list operations,' and the boundary between list_nodit_node_apis/data_apis/multichain_apis is only clarified by reading descriptions closely. call_nodit_api vs call_nodit_multichain_api vs call_nodit_aptos_indexer_api are distinguishable by target API family, but an agent may frequently pick the wrong list tool first.

    Naming Consistency4/5

    Names follow a clear verb_nodit_noun pattern across list/get/call with snake_case throughout. The aptos indexer tools introduce longer variants (list_nodit_aptos_indexer_api_query_root) and 'query_root' rather than '_apis', a minor deviation from the otherwise uniform convention.

    Tool Count5/5

    11 tools is well within a reasonable scope and each listing spec/calling group earns its place in a discover-then-invoke workflow. The set is neither bloated nor thin for a multi-category API gateway.

    Completeness3/5

    Discovery (categories, operations, specs) and invocation are covered for Node, Data, Multichain, and Aptos Indexer APIs, but Webhook APIs can be listed yet explicitly cannot be invoked by any tool — a real dead end. There is also no generic spec-getter path described for the Aptos query roots other than the dedicated one, leaving an inconsistent lifecycle.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources