広告掲載
MCP.so
ログイン

Neo N3 MCP Server

@r3e-network

リポジトリホームページ

基本情報

カテゴリ

その他

ライセンス

MIT

トランスポート

stdio

作者

r3e-network

Neo N3 MCP Server について

An MCP server for interacting with the Neo N3 blockchain.

Neo N3 MCP Server の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "neo-n3-mcp": {
      "command": "npx",
      "args": [
        "@r3e/neo-n3-mcp"
      ]
    }
  }
}

Neo N3 MCP Server のツール

27

Get the active network mode and available Neo networks.

Get blockchain height, validator info, and the active network.

Get the current block height for the selected network.

Get NEO, GAS, and NEP-17 balances for an address.

Get the amount of GAS claimable by an address.

Get NEP-17 transfer history for an address.

Get NEP-11 balances for an address.

Get NEP-11 transfer history for an address.

List supported well-known contracts for the selected network.

Get metadata and operations for a contract by known name, script hash, or Neo address.

Check whether a contract is deployed and inspect its current on-chain status by known name, script hash, or Neo address.

Create a Neo N3 wallet, persist it locally, and return a NEP-2 encrypted private key.

Get sanitized metadata for a locally stored wallet by address.

Set the configured network mode. Restart may be required.

Get block details by height or hash.

Get transaction details by hash.

Get the application log for a transaction hash.

Wait for a transaction to be confirmed on-chain.

Transfer NEP-17 assets using a sender WIF.

Invoke a contract read method or prepare/send a write invocation by script hash or a generic contract reference.

Import a wallet from a private key or WIF.

Estimate network and system fees for a transfer.

Estimate network and system fees for a contract invocation by script hash or a generic contract reference.

Claim available GAS for an account.

Deploy a compiled Neo N3 contract. Requires explicit confirmation.

Create a NeoFS container.

List NeoFS containers for an owner.

概要

What is Neo N3 MCP Server?

A production-ready MCP server for Neo N3 blockchain integration, providing 27 tools, 3 fixed resources, and a parameterized block resource for wallet management, transaction lifecycle, asset transfers, contract deployment and interaction, and blockchain queries.

How to use Neo N3 MCP Server?

Install globally via npm install -g @r3e/neo-n3-mcp or locally via npm install @r3e/neo-n3-mcp. Run with npx @r3e/neo-n3-mcp or neo-n3-mcp (if installed globally). Configure using environment variables (NEO_NETWORK, NEO_MAINNET_RPC, NEO_TESTNET_RPC, etc.) or via Docker. MCP client configuration (e.g., Claude/Cursor) uses the neo-n3 server entry with npx -y @r3e/neo-n3-mcp and the desired environment.

Key features of Neo N3 MCP Server?

  • 27 tools for blockchain interaction
  • 3 fixed resources + parameterized block resource
  • Supports mainnet, testnet, or both networks
  • Wallet creation, import, and balance queries
  • Asset transfers and gas claiming
  • Contract deployment, invocation, and lookup
  • HTTP endpoints for health, metrics, and API access
  • Built-in rate limiting and secure logging
  • Docker support with compose configuration
  • N3Index-backed name resolution for contracts

Use cases of Neo N3 MCP Server?

  • Automate wallet management and asset transfers on Neo N3
  • Query blockchain data (blocks, transactions, application logs)
  • Deploy and invoke smart contracts via MCP tools or HTTP API
  • Monitor and manage NeoFS containers
  • Integrate Neo N3 capabilities into AI assistants (Claude, Cursor)

よくある質問

1

What runtime or dependencies are required?

Node.js 18.x, 20.x, or 22.x is required. The server is published on npm and can also run via Docker.

2

How are private keys handled?

Private keys are encrypted and stored securely. Input validation is enforced, and sensitive operations require explicit confirmation.

3

Which Neo N3 networks are supported?

Mainnet, testnet, or both simultaneously. When set to `both`, stdio tool calls default to mainnet; HTTP mode requires a single network.

4

Where does contract name resolution happen?

The server includes a local famous-contract registry; unrecognized names can be resolved via the N3Index API (`https://api.n3index.dev`) before on-chain validation.

5

Is there rate limiting?

Yes, rate limiting is enabled by default (60 requests per minute, 1000 per hour) and can be configured via environment variables.

コメント

「その他」の他のコンテンツ

Senso MCP for Joomla

sensomedia

Senso MCP turns a Joomla 5 or 6 site into a remote MCP server. It runs inside Joomla itself (no extra server, no Node.js bridge) and is secured with OAuth 2.1 and Joomla's own ACL. The free pack lets an AI assistant crea

Hindsight

vectorize-io

Hindsight: Agent Memory That Learns

50.4K

MCP Toolbox for Databases

googleapis

MCP Toolbox for Databases is an open source MCP server for databases.

15.9K

Screenpipe

screenpipe

YC (S26) | Open Computer History | Continuously record your company computer work, map your workflows, help you find work worth automating, and power your agents' context

22.0K

Yuppsy

Yuppsy MCP: build and publish real estate websites from your AI assistant. Yuppsy lets your AI assistant create live websites for real estate agents and individual property listings. You don't need a designer or any code

広告掲載