Server facts
neo-n3-mcp
Project
- Author
- r3e-network
- Repository
- github.com/r3e-network/neo-n3-mcp
- Website
- neomcp.xyz
- License
- MIT
- Category
- Blockchain & Web3
Tech
- Runtime / language
- node
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 4
- Last commit
- Data as of
Overview
Neo N3 wallet activity, contract operations, and blockchain inspection are available through neo-n3-mcp's tools for MCP clients. Developers can create or import wallets, retrieve locally stored wallet metadata, and inspect NEO, GAS, NEP-17, and NEP-11 holdings. Account queries cover token transfer histories and claimable GAS. For outgoing activity, the tools estimate transfer fees, send NEP-17 assets using a sender WIF, and claim available GAS. Transaction lookup, application logs, and confirmation waiting support follow-up after submission.
Contract workflows include discovering known contracts, inspecting metadata and deployment status, calling read methods, and preparing or sending write invocations. References can use known names, script hashes, or Neo addresses; unresolved plain names can fall back to N3Index lookup before on-chain validation. Deployment accepts compiled contracts and requires explicit confirmation. Other tools retrieve blocks by height or hash, report network and validator information, and create or list NeoFS containers. The Node-based server supports stdio integration, with configuration for mainnet, testnet, or both. Resources expose network status and block data through a height-based template.
neo-n3-mcp setup notes
- neo-n3-mcp records stdio only; confirm a network transport upstream before planning remote access.