Nodit MCP Server

Created By
noditlabsa year ago
A Model Context Protocol (MCP) server for AI agents to interact with blockchain data via Nodit’s Web3 Data and Node APIs. Enables LLMs to access structured, multi-chain blockchain context with zero blockchain-specific logic.
Overview

What is Nodit MCP Server?

Nodit MCP Server is a Model Context Provider (MCP) server that facilitates AI agents' interaction with blockchain data through Nodit’s Web3 Data and Node APIs, allowing access to structured, multi-chain blockchain context without requiring blockchain-specific logic.

How to use Nodit MCP Server?

To use Nodit MCP Server, developers can install it via npm or npx, configure it with their Nodit API key, and integrate it with AI applications to query and analyze blockchain data across various networks.

Key features of Nodit MCP Server?

  • Simplified access to multi-chain blockchain data for AI applications.
  • Support for EVM-compatible and non-EVM networks.
  • Tools for dynamic discovery and interaction with Nodit’s Web3 APIs.
  • High-level APIs for accessing indexed blockchain data.

Use cases of Nodit MCP Server?

  1. Building AI agents that analyze real-time blockchain data.
  2. Creating Web3 applications without deep blockchain expertise.
  3. Querying and interacting with various blockchain networks seamlessly.

FAQ from Nodit MCP Server?

  • What networks does Nodit MCP Server support?

It supports multiple networks including Ethereum, Bitcoin, Dogecoin, and more.

  • Is there a cost to use Nodit MCP Server?

The usage is subject to Nodit’s API pricing, which may vary based on the services used.

  • Do I need blockchain expertise to use this server?

No, Nodit MCP Server is designed to simplify blockchain interactions for developers.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
noditlabs
Star
8
Language
TypeScript
License
Apache-2.0 license
Tags

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago