Novai MCP Server

What 0x-devc/novai-mcp-server MCP server does

The 0x-devc/novai-mcp-server MCP server gives MCP clients query access to the live NOVAI chain, an AI-native layer 1 using chained-BFT consensus. It is designed as a thin bridge between an agent and NOVAI's public JSON-RPC API, so an agent can inspect blockchain state without writing a custom SDK integration.

The available data includes the latest chain tip, individual blocks, confirmed transactions, account or entity balances, and on-chain AI entity records. Agents can also inspect signal commitments, oracle anchors, and memory objects associated with NOVAI entities. The package intentionally excludes write, signing, transaction-submission, and private-key functionality.

How it works

After the MCP client starts the process, the server advertises its query tools through MCP over standard input and output. Each tool maps to a read operation on the configured JSON-RPC endpoint. Inputs are validated before a network request is made; chain-side errors and transport failures are returned as tool errors without stack traces.

Block queries can use either a height or a hash, but not both. The chain-status query is useful as a first call because it returns the current tip height and confirms that the chain is advancing. Height-based block access is limited by the node's retained recent window, while hash lookups can work for blocks still indexed by the node.

Hashes and identifiers use 64 hexadecimal characters without a 0x prefix, and block heights are non-negative integers. Balances are represented as decimal strings to preserve precision.

Setup and configuration

The 0x-devc/novai-mcp-server MCP server requires Node.js 18 or later. It can be started directly with npx or installed from npm before running its binary. For a stdio client configuration, use the package command as the MCP server process.

By default, requests go to https://rpc.novai.network. Set NOVAI_RPC_URL to use another JSON-RPC endpoint. No secret, token, or additional configuration is required because the documented endpoint is public and the server is read-only.

For local development, the repository documents npm install, npm run build, and npm test. The live endpoint test is available through npm run test:live, and an end-to-end stdio check can be run after building with node scripts/smoke.mjs.

Tools and capabilities

The 0x-devc/novai-mcp-server MCP server exposes tools for:

• Reading the latest committed block's height, hash, round, transaction count, state root, and parent hash.
• Fetching a block by height or hash and a confirmed transaction by transaction ID.
• Looking up an AI entity, including its creator, code hash, autonomy mode, capability bits, balances, reputation, and activity data.
• Reading an address or entity balance and nonce.
• Listing signal commitments by block height, issuer, or signal type. Supported type codes cover anomaly, optimization, prediction, risk score, audit report, spam risk, and congestion forecast.
• Fetching oracle anchors by signal hash, issuer, or data tag, with optional external timestamp filters for list queries.
• Listing memory objects owned by an entity, including their type, heights, owner, identifier, and hex-encoded data.

Limitations and notes

This 0x-devc/novai-mcp-server MCP server cannot modify chain state. It does not hold private keys, sign requests, or submit transactions. Unknown transactions, entities, oracle anchors, and unavailable blocks may return null rather than an error. In particular, an old block height may no longer be available even if that block was valid, because the endpoint keeps only a bounded recent height window. Use a block hash when the node still indexes the historical block.