@noditlabs/nodit-mcp-server 1.0.10 → 1.0.12

package/README.md

@@ -22,10 +22,10 @@ With Nodit's MCP, you can:
 - Leverage Nodit's **reliable node infrastructure, Web3 Data APIs, and GraphQL indexing services** through a unified access layer.
 - Easily develop with blockchain MCP in **both local and remote integration**, depending on your workflow needs.
 
-Supported networks include Ethereum, Base, Optimism, Arbitrum, Polygon, Aptos, Bitcoin, Dogecoin, TRON, XRPL, and more.
+Supported networks include Ethereum, Base, Optimism, Arbitrum, Polygon, Aptos, Bitcoin, Dogecoin, TRON, XRPL, GIWA(Sepolia) and more.
 
 ## Table of Contents
-- [How Nodit MCP Tools Work](#how-nodit-mcp-tools-work)
+- [List of Tools](#list-of-tools)
 - [Features](#features)
 - [Prerequisites](#prerequisites)
 - [Running Local Nodit MCP Server](#running-local-nodit-mcp-server)
@@ -35,21 +35,30 @@ Supported networks include Ethereum, Base, Optimism, Arbitrum, Polygon, Aptos, B
 - [Scope & Limitations](#scope--limitations)
 - [License](#license)
 
-## How Nodit MCP Tools Work
+## List of Tools
 
 Nodit MCP Server provides tools enabling AI agents to dynamically discover, understand, and interact with Nodit's Web3 APIs and data infrastructure. The tools minimize token consumption and maintain a lightweight context by modularizing API interactions into distinct steps:
 
-- **List API Categories (`list_nodit_api_categories`)**  
+- **Tools for Listing API Categories**<br>
   Retrieve a list of high-level API categories available.
+	- `list_nodit_api_categories`
 
-- **List API Operations (`list_nodit_node_apis`, `list_nodit_data_apis`, `list_nodit_aptos_indexer_api_query_root`,`list_nodit_webhook_apis`)**  
+- **Tools for Listing API Operations**  
   Fetch available operations within a selected category (Node APIs, Data APIs, Aptos Indexer APIs, Webhook APIs).
+  	- `list_nodit_node_apis`
+  	- `list_nodit_data_apis`
+  	- `list_nodit_aptos_indexer_api_query_root`
+  	- `list_nodit_webhook_apis`
 
-- **Get API Specification (`get_nodit_api_spec`,`get_nodit_aptos_indexer_api_spec`)**  
+- **Tools for Getting API Specification**  
   Obtain detailed information for a specific API operation (parameters, request/response schema).
+  	- `get_nodit_api_spec`
+  	- `get_nodit_aptos_indexer_api_spec`
 
-- **Call API (`call_nodit_api`,`call_nodit_aptos_indexer_api`)**  
+- **Tools for Calling API**  
   Execute an API call using the operationId and validated parameters.
+  	- `call_nodit_api`
+  	- `call_nodit_aptos_indexer_api`
   
 Nodit MCP Server communicates using the standard JSON-RPC over stdio protocol, following the Model Context Protocol (MCP) conventions.
 Currently, only stdio-based communication is supported for server-client interactions.
@@ -71,8 +80,8 @@ For detailed API specifications and usage guidelines, please refer to the [Nodit
   Query detailed Aptos blockchain activities through GraphQL endpoints.
 
 - **Supported Networks**  
-  - EVM-Compatible: Ethereum, Arbitrum, Avalanche, Base, Chiliz, Kaia, Optimism, Polygon, BNB Chain
-  - Non-EVM: Aptos, Bitcoin, Dogecoin, TRON, XRPL, Sui
+  - EVM-Compatible: Ethereum, Arbitrum, Avalanche, Base, Chiliz, Kaia, Optimism, Polygon, BNB Chain, GIWA(Sepolia)
+  - Non-EVM: Aptos, Bitcoin, Dogecoin, TRON, XRPL, Sui, Solana
 
 
 ## Prerequisites

package/build/helper/nodit-apidoc-helper.js

@@ -4,6 +4,20 @@ import path from 'path';
 import { fileURLToPath } from 'url';
 const __filename = fileURLToPath(import.meta.url);
 const __dirname = path.dirname(__filename);
+export const BLOCKED_OPERATION_IDS = new Set([
+    "solana-getProgramAccounts",
+    "solana-getClusterNodes",
+    "solana-getLeaderSchedule",
+    "solana-getSignaturesForAddress",
+    "solana-getBlock",
+    "solana-getBlocks",
+    "solana-getBlocksWithLimit",
+    "solana-getVoteAccounts",
+    "solana-getInflationGovernor",
+    "solana-getInflationRate",
+    "solana-getInflationReward",
+    "solana-getSupply",
+]);
 export function log(message, ...args) {
     console.error(message, ...args);
 }
@@ -53,6 +67,17 @@ export function loadNoditNodeApiSpecMap() {
                 });
             }
         }
+        const solanaNodeApiSpecDir = path.resolve(__dirname, '../spec/reference/solana-node-api/http-methods');
+        const solanaNodeApiSpecFiles = fs.readdirSync(solanaNodeApiSpecDir);
+        for (const file of solanaNodeApiSpecFiles) {
+            if (file.endsWith('.yaml')) {
+                const filePath = path.join(solanaNodeApiSpecDir, file);
+                const solanaNodeApiSpecMap = loadMultiPathApiSpec(filePath);
+                solanaNodeApiSpecMap.forEach((spec, operationId) => {
+                    noditApiSpecMap.set(operationId, spec);
+                });
+            }
+        }
         return noditApiSpecMap;
     }
     catch (error) {
@@ -82,7 +107,7 @@ export function loadNoditAptosIndexerApiSpec() {
     return loadOpenapiSpecFile(schemaPath);
 }
 export function isNodeApi(operationId) {
-    return operationId.includes("_");
+    return operationId.includes("_") || operationId.startsWith("solana-");
 }
 export function isEthereumNodeApi(operationId) {
     return !operationId.includes("-");
@@ -90,6 +115,9 @@ export function isEthereumNodeApi(operationId) {
 export function isWebhookApi(operationId) {
     return operationId.includes("Webhook");
 }
+export function isBlockedOperationId(operationId) {
+    return BLOCKED_OPERATION_IDS.has(operationId);
+}
 export function findNoditNodeApiSpec(operationId, noditNodeApiSpecMap) {
     let key = operationId;
     if (isEthereumNodeApi(operationId)) {