Nodit MCP Gateway

This Model Context Protocol (MCP) server acts as a unified portal, bridging sophisticated Artificial Intelligence entities and software developers with structured, immediately consumable ledger intelligence sourced from Nodit's extensive Web3 infrastructure.

Conceptual Overview

The Nodit MCP Gateway substantially streamlines the process by which intelligent systems and applications interface with decentralized ledger ecosystems. Bypassing the need to manage intricate remote procedure calls (RPCs), raw event stream parsing, or network-specific data serialization, this service delivers data that is normalized and pre-processed into formats optimized for machine reasoning and automated policy execution.

Leveraging the Nodit MCP architecture empowers users to: - Construct autonomous AI agents capable of interrogating, assessing, and executing actions based on live ledger telemetry across a wide array of protocols (EVM and others). - Accelerate the creation of Web3-native software solutions by removing the prerequisite for specialized blockchain engineering skills. - Utilize Nodit's robust network access, advanced data indexing services, and high-level Web3 APIs through a singular, abstracted access point. - Seamlessly integrate blockchain context within development workflows via both localized hosting and direct remote connectivity.

Supported ecosystems encompass major platforms including Ethereum, Base, Optimism, Arbitrum, Polygon, Aptos, Bitcoin, Dogecoin, TRON, XRPL, GIWA(Sepolia), and many others.

Navigational Index

Operational Methodology of Nodit MCP Tools
Core Functionality
System Requirements
Local Deployment Procedures
Remote Connection Guide
Issue Resolution
Illustrative Agent Interactions
Operational Boundaries
Licensing Terms

Operational Methodology of Nodit MCP Tools

The Nodit MCP Gateway furnishes AI agents with discovery and interaction capabilities for Nodit's suite of Web3 services. The toolset is engineered to promote context efficiency and minimize token overhead by segmenting API interactions into discrete, manageable steps:

Identify Service Categories (list_nodit_api_categories)
Obtain a hierarchical listing of the available high-level service domains.
Inventory Available Endpoints (list_nodit_node_apis, list_nodit_data_apis, list_nodit_aptos_indexer_api_query_root,list_nodit_webhook_apis)
Retrieve the specific callable operations within a chosen domain (e.g., Direct Node Access, Indexed Data Query, Aptos Specific Indexing, Notification Subscriptions).
Retrieve Service Schema (get_nodit_api_spec,get_nodit_aptos_indexer_api_spec)
Acquire comprehensive documentation for a chosen endpoint, detailing parameter constraints, input data structures, and output formats.
Execute Service Call (call_nodit_api,call_nodit_aptos_indexer_api)
Initiate the requested operation using the resolved endpoint identifier and correctly formatted input parameters.

Communication between the Nodit MCP Gateway and its clients adheres strictly to the Model Context Protocol (MCP) using the standard JSON-RPC protocol transmitted over standard input/output (stdio). Currently, this stdio channel is the sole supported medium for synchronous server-client dialogue.

Core Functionality

The subsequent list details the primary capabilities and the spectrum of supported distributed ledgers accessible to AI entities via the Nodit MCP Gateway. Detailed API signatures and usage instructions are available in the Nodit Developer Documentation.

Direct Node Access & RPC Services
Access to underlying ledger endpoints managed by Nodit's professional infrastructure. Facilitates live state queries, transaction broadcasting, decentralized application state interrogation, and more.
Advanced Web3 Data Indexing Services
High-level interfaces for accessing deeply analyzed and aggregated ledger data. This includes curated datasets detailing chronological block sequences, transaction histories, comprehensive account activity summaries, and asset flow attribution—information that is prohibitively complex to reconstruct from raw RPC outputs alone.
Specialized GraphQL Indexing (Aptos Focus)
Enables precise querying of historical and current activity records specific to the Aptos network utilizing its native GraphQL interface.
Supported Ledger Environments
EVM Kin: Ethereum, Arbitrum, Avalanche, Base, Chiliz, Kaia, Optimism, Polygon, BNB Chain, GIWA(Sepolia)
Non-EVM Architectures: Aptos, Bitcoin, Dogecoin, TRON, XRPL, Sui, Solana

System Requirements

Node.js runtime environment, version 18 or newer.
A valid Nodit Access Credential (Acquire via the Nodit Management Portal)

Local Deployment Procedures

Deployment via npx (Recommended Method)

bash npx @noditlabs/nodit-mcp-server@latest

Manual Compilation and Execution

bash

Clone the source repository and initialize submodules

git clone --recurse-submodules https://github.com/noditlabs/nodit-mcp-server.git

Navigate into the project folder

cd nodit-mcp-server

Install necessary dependencies

npm install

Compile source code

npm run build

Prior to initiation, ensure your API credential is set in the execution environment:

bash export NODIT_API_KEY=your-secret-key

Then launch the localized server instance:

bash node build/index.js

Interacting with the Local Instance

Communication must conform to the JSON-RPC specification over the stdio stream. Below illustrates sending primitive requests to the server process:

Query Example: Obtain Tool Registry

You may feed the JSON payload directly:

bash {"method":"tools/list","params":{},"jsonrpc":"2.0","id":1}

Alternatively, pipe the request via standard shell utilities:

bash echo '{"method":"tools/list","params":{},"jsonrpc":"2.0","id":1}' | node build/index.js

Command Example: Invoke Category Listing Tool

bash echo '{"method":"tools/call","params":{"name":"list_nodit_api_categories","arguments":{}},"jsonrpc":"2.0","id":1}' | node build/index.js

Configuration for AI Development Environments (Cursor IDE / Claude Desktop)

Modify your environment configuration file as follows:

Cursor IDE Profile Path
Unix/macOS: ~/.cursor/mcp.json
Windows: C:\Users\<Username>\.cursor\mcp.json
Claude Desktop Profile Path
Unix/macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: C:\Users\<Username>\AppData\Roaming\Claude\claude_desktop_config.json

Inject the configuration into the mcpServers map:

{ "mcpServers": { "nodit": { "command": "npx", "args": ["@noditlabs/nodit-mcp-server@latest"], "env": { "NODIT_API_KEY": "****" } } } }

⚠️ Crucial Notice
Substitute **** with your actual authentication key. Failure to configure the key correctly will result in authorization failures for subsequent API requests.

Configuration for Claude Command Line Interface (CLI)

Integration with the Claude CLI offers a rapid startup path:

bash

Register the Nodit MCP service

claude mcp add nodit-mcp-server npx @noditlabs/nodit-mcp-server

Set the required environment variable

export NODIT_API_KEY=your-secret-key

Launch the Claude environment

claude

Integrating Nodit Remote MCP Server

For AI environments supporting Remote MCP connections, you can bypass local execution entirely by connecting directly to Nodit’s hosted gateway endpoint, provided you possess a valid API credential.

Remote Endpoint Address

Utilize the following Server-Sent Events (SSE) URL for connectivity. Remember to substitute INSERT_YOUR_API_KEY with your actual secret key.

bash https://mcp.nodit.io/sse?apiKey=INSERT_YOUR_API_KEY

Connection Guide for Claude (Web Interface)

If operating within an Enterprise, Pro, or Max tier of Claude, Remote MCP integration is accessible:

Navigate to the application Settings area, then select Integrations.
Select the option to [Add custom integration].
Choose to integrate a new Remote MCP component.
Input the dedicated SSE endpoint URL provided above to finalize setup.

Upon successful connection, the Nodit MCP service will be visible and activatable within the Search and Tooling sections on the primary Claude interface.

Connection Guide for Cursor IDE

To establish remote linkage within Cursor IDE: 1. Access Preferences, navigate to Cursor Settings, and select MCP Tools. 2. Initiate a new MCP Service registration via [+ New MCP Server], opening the mcp.json configuration file.

Alternatively, direct file manipulation is possible at: - Unix/macOS: ~/.cursor/mcp.json - Windows: C:\Users\<Username>\.cursor\mcp.json

Append the following structure to the mcpServers object. If other services are present, ensure entries are correctly delimited by commas:

{ "mcpServers": { "nodit": { "url": "https://mcp.nodit.io/sse?apiKey=INSERT_YOUR_API_KEY" } } }

After saving, return to the MCP Tools panel within Cursor and activate the 'nodit' service. Connection confirmation is indicated when the status displays "9 tools enabled" in green text.

Issue Resolution

Difficulties Executing MCP via npx in Hosted Desktop Clients

If execution of the MCP server via npx fails when integrated with Claude Desktop or similar Node.js-dependent tools, the underlying cause is frequently related to: * Presence of multiple, conflicting Node.js runtime installations (e.g., managed via Homebrew alongside a direct installer). * Inconsistencies or errors within the system's PATH environment variables. * The desktop application failing to correctly locate the designated Node.js binary.

Execute the following diagnostic procedures to ensure Node.js version 18 or higher is correctly recognized:

1. Verify Current Runtime Version

Execute this command in your active shell to see the utilized version:

node --version

You must observe a version string beginning with v18 or a subsequent major version (e.g., v18.19.0).

If the version is inadequate, you must either install a compliant version or modify your environment to point to the correct binary.

[!NOTE] Claude Desktop might utilize a different Node.js version than what your interactive terminal session reports. Version clashes often arise from multiple installations (e.g., nvm, Homebrew, system package). To map common binary locations:

Homebrew locations

ls /usr/local/bin/node ls /opt/homebrew/bin/node

nvm managed versions

ls ~/.nvm/versions/node/

Standard system location

ls /usr/bin/node

2. Installation or Version Switching (If Required)

If you lack a compatible runtime, utilize one of these installation methods:

Official Installer: Fetch from nodejs.org
Homebrew (for macOS users):

bashbrew install node@20

nvm (Recommended for version control):

curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.0/install.sh | bash nvm install 20 nvm use 20 nvm alias default 20

3. Identify Node.js Binary Path Used by Claude

In your terminal, execute the following to reveal the path of the currently active Node.js executable, which is generally what Claude inherits:

which node

This output indicates the path Claude is likely referencing during its execution lifecycle.

4. Forcing the Correct Node.js Version for Desktop Clients

If utilizing nvm for management:

nvm use 18 # Set the target version nvm alias default 18

If using Homebrew, ensure its bin directory takes precedence in your PATH variable:

export PATH="/opt/homebrew/bin:$PATH" # For Apple Silicon architectures

OR

export PATH="/usr/local/bin:$PATH" # For Intel macOS architectures

It is advisable to standardize on one version management approach (either nvm or Homebrew) to preempt environmental conflicts.

5. Reinitialize Claude Desktop

Always restart the Claude Desktop application after modifying environment variables or Node.js installations to guarantee the new configuration is loaded correctly.

Illustrative Agent Interactions with Nodit MCP

Once the Nodit Gateway is successfully linked, agents can issue natural language directives to query ledger data from diverse blockchains directly. The subsequent examples showcase a small fraction of potential use cases, encouraging exploration beyond these boundaries.

📊 On-chain Behavior Monitoring

Provide a summary of the recent activity for the address 0xabc…def across the Ethereum and Arbitrum networks. This summary must detail significant transaction events, ERC-20 token movements, and NFT engagements within the last seven days.

Detail the complete inventory of fungible and non-fungible assets currently held by this specific wallet across Ethereum and Polygon. Include current quantity/balance and the corresponding official asset names.

Perform a risk assessment of the entity at address 0xabc… based on their documented historical on-chain transactional patterns.

🧾 Contract and Transaction Deep Dive

Examine user interaction patterns with the smart contract located at 0xcontract… on the Ethereum network over the preceding week.

Generate an analysis summarizing the contents and metadata of the ten most recent blocks confirmed on the Arbitrum network.

🧠 AI Agent Specific Applications

Formulate a set of optimal decentralized finance (DeFi) engagement strategies for the wallet 0xabc… considering its current asset allocation across Ethereum and Arbitrum.

Compile a comprehensive, daily status report for the governance entity 0xdao… This report must integrate token balance snapshots, net token flow (in/out), and any recent governance proposal participation.

⚙️ Web3 Application Development Scaffolding

Produce functional TypeScript code utilizing the fetch API to retrieve every ERC-20 token transfer associated with address 0xabc… on the Ethereum ledger, specifically querying Nodit’s Node API interface.

Develop the foundational structure for a visualization utility designed to track asset transfers recorded in recent transactions on the XRPL ledger.

Construct the necessary backend logic to aggregate and present synthesized ledger intelligence drawn from several different chains via the Nodit infrastructure.

Operational Boundaries

The Nodit MCP Gateway is specifically designed to furnish structured context, maximizing the utility of Nodit's proprietary APIs for LLM-based agents. Its defined scope encompasses:

Standardizing the representation of Nodit's service catalog (Node APIs, Web3 Data APIs) into formats readily digestible by large language models.
Explicitly defining endpoint specifications, input/output data contracts, example responses, and standardized error reporting protocols.

Conversely, responsibilities explicitly outside the purview of the MCP Gateway include:

The dynamic selection or preference for specific endpoints, which is contingent upon the consuming LLM's variant (e.g., GPT-4, Claude 3), prompt structure, or agent architecture.
The qualitative assessment of API results or the determination of error resolution logic, which remains the exclusive domain of the consuming LLM's reasoning engine.

The Nodit MCP Gateway commits to delivering precise and well-formed API contextual data, but it inherently does not warrant the ultimate analytical conclusions or operational execution performed by external, third-party large language models.

Licensing Terms

This software is distributed under the terms of the Apache License 2.0. Full legal stipulations are detailed within the LICENSE artifact. Relevant auxiliary legal declarations are located in the NOTICE file.

"Nodit" and the associated visual identifier are registered trademarks belonging to Lambda256. Unauthorized reproduction or use of the name or insignia is strictly prohibited without prior written consent.

WIKIPEDIA: Tron (stylized as TRON) is a decentralized, proof-of-stake blockchain with smart contract functionality. The cryptocurrency native to the blockchain is known as Tronix (TRX). It was founded in March 2014 by Justin Sun and, since 2017, has been overseen and supervised by the TRON Foundation, a non-profit organization in Singapore, established in the same year. It is open-source software. Tron was originally an Ethereum-based ERC-20 token, which switched protocol to its own blockchain in 2018. On some cryptocurrency wallets, users can't withdraw their funds until they have enough amount for the network fee. Tron has been criticised for enabling organized crime, with The Wall Street Journal stating in 2025 that it is a "popular channel for crypto’s criminal fraternity to move funds" and responsible for "more than half of all illegal crypto activity" in 2024, with the United Nations Office on Drugs and Crime calling it a “preferred choice for crypto money launderers” in Asia.

== History == Tron was founded by Justin Sun in 2017. The TRON Foundation was established in July 2017 in Singapore. The TRON Foundation raised $70 million in 2017 through an initial coin offering (ICO) shortly before China outlawed the digital tokens. The testnet, Blockchain Explorer, and Web Wallet were all launched by March 2018. TRON Mainnet launched shortly afterward in May 2018, marking the Odyssey 2.0 release as a technical milestone for TRON. In June 2018, TRON switched its protocol from an ERC-20 token on top of Ethereum to an independent peer-to-peer network. On 25 July 2018, the TRON Foundation announced it had finished the acquisition of BitTorrent, a peer-to-peer file sharing service. Upon this acquisition, in August 2018, BitTorrent Founder Bram Cohen also disclosed that he was leaving the company to found a separate cryptocurrency, Chia. By January 2019, TRON had a total market cap of about $1.6 bn. Despite this market performance, some authors viewed TRON as a typical case of the complex and disordered nature of cryptocurrencies. In February 2019, after being acquired by TRON Foundation, BitTorrent started its own token sale based on the TRON network. In late 2021, Justin Sun resigned as CEO of the TRON Foundation, which was subsequently reorganized as a DAO. In March 2023, Sun and Tron were sued by the U.S. Securities and Exchange Commission (SEC) for selling unregistered securities related to the sale and promotion of Tronix (TRX) and BitTorrent (BBT) tokens; the SEC alleged that Sun and Tron had engaged in wash trading in the secondary market for TRX in order to buoy its price. $31 million of proceeds were generated through thousands of Tronix trades between two accounts Sun controlled. Eight celebrities, including Akon, Ne-Yo, Austin Mahone, Soulja Boy, Lindsay Lohan, Jake Paul and Lil Yachty, were charged with promoting these cryptocurrencies without disclosing that they were sponsored, with all those other than Soulja Boy, and Mahone settling with t

nodit-mcp-gateway

Author

noditlabs

Quick Info

Actions

Tags