NANO MCP Server

Created By
dhyabi2a year ago
Overview

what is NANO MCP Server?

NANO MCP Server is a Model Context Protocol (MCP) server implementation designed for interacting with the NANO (XNO) cryptocurrency network.

how to use NANO MCP Server?

To use NANO MCP Server, you can either install it as a library using npm or run it as a standalone server. For library usage, import the NanoMCP class and utilize its methods to interact with the NANO network. For standalone usage, start the server using npm start.

key features of NANO MCP Server?

  • Account operations (balance, info)
  • Block operations (count)
  • Network information retrieval
  • Unit conversion utilities
  • Real-time RPC interaction with the NANO network
  • Detailed logging of all RPC calls

use cases of NANO MCP Server?

  1. Checking account balances and pending amounts in the NANO network.
  2. Retrieving detailed account information including frontier block and representative.
  3. Monitoring the current block count of the NANO network.
  4. Converting between NANO and raw units for transactions.

FAQ from NANO MCP Server?

  • Is NANO MCP Server free to use?

Yes! NANO MCP Server is open-source and free to use.

  • What programming language is NANO MCP Server written in?

NANO MCP Server is written in JavaScript.

  • How can I contribute to NANO MCP Server?

You can contribute by forking the repository, creating a feature branch, and submitting a pull request.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
dhyabi2
Star
0
Language
JavaScript
License
MIT license

Recommend Servers

View All
Voyei

2 hours ago
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)

a day ago