Server facts
nodit-mcp-server
Project
- Author
- noditlabs
- Repository
- github.com/noditlabs/nodit-mcp-server
- Website
- nodit.io
- License
- Apache-2.0
- Category
- Blockchain & Web3
Tech
- Runtime / language
- node
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 23
- Last commit
- Data as of
Tags
- ai
- blockchain
- blockchain data
- blockchain node
- llm
- mcp
- mcp server
- onchain
- onchain data
- rpc node
- web3
Overview
Blockchain queries through Nodit follow a discovery-to-request workflow: agents first list API categories, explore available operations, inspect specifications, and then call an operation with its parameters. The toolset covers node services, indexed Web3 data, webhook operation discovery, and a dedicated Aptos GraphQL path with query-root listings and specifications. This gives developers and AI applications access to transaction records, token transfers, account activity, and asset movements without assembling those datasets solely from raw node responses. Supported networks span EVM chains such as Ethereum and Base alongside networks including Bitcoin, Aptos, and Solana.
For wallet research and application development, the supplied examples include reviewing holdings, summarizing activity across chains, examining contract usage, and building asset-movement dashboards. Node APIs also support submitting transactions and interacting with contracts. Local use communicates over stdio, while the documentation separately describes a hosted remote integration. API calls consume Nodit quota. The server supplies API context and response structures; choosing suitable operations and interpreting results remain dependent on the consuming model and agent design.
nodit-mcp-server setup notes
- nodit-mcp-server records stdio only; confirm a network transport upstream before planning remote access.