novai-mcp-server
NOVAI MCP server
A read-only Model Context Protocol (MCP) server that lets any MCP-equipped agent query the live NOVAI chain over its public JSON-RPC endpoint. It exposes query tools only. There is no write, sign, submit, or key-handling path anywhere in this package.
NOVAI is an AI-native layer 1 with chained-BFT consensus. This server is a thin, typed bridge: an agent discovers the tools through standard MCP tooling and reads the chain without writing any SDK code.
Safety boundary
This is version 0 and it is read-only by design.
Every tool is a query that maps to a single read method on the public endpoint.
The package never holds a private key, never signs, and never submits a transaction.
The write methods the chain exposes are deliberately not wired in.
Related MCP server: Grove Public Endpoints MCP Server
Requirements
Node.js 18 or newer.
Install and run
Run it directly with npx:
npx novai-mcp-serverOr install it and run the binary:
npm install novai-mcp-server
novai-mcp-serverThe server speaks MCP over stdio. Point your MCP client at the command above.
Example MCP client configuration
{
"mcpServers": {
"novai": {
"command": "npx",
"args": ["novai-mcp-server"]
}
}
}Configuration
NOVAI_RPC_URLoverrides the JSON-RPC endpoint. It defaults to the public NOVAI URL,https://rpc.novai.network. No other configuration, no secrets, and no auth are required, because the public endpoint is open and read-only.
Tools
All hashes and ids are 64 hex characters (32 bytes, no 0x prefix). All heights are non-negative integers. Every input is validated before any network call, and both chain errors and transport failures are returned as clean tool errors with no stack traces.
Tool | Returns | Required params | Optional params |
| The latest committed block, so you can verify the chain is live and learn the tip height | none | none |
| A single block | exactly one of | none |
| A confirmed transaction, or null if unknown |
| none |
| An AI entity (agent) record, or null if unknown |
| none |
| Balance (decimal string) and nonce for an address |
| none |
| Signal commitments recorded at a height |
| none |
| Signals issued by an entity within a height range |
| none |
| Signals of a type within a height range |
| none |
| An oracle anchor by signal hash, or null if unknown |
| none |
| Oracle anchors by issuer within a height range |
|
|
| Oracle anchors by data tag within a height range |
|
|
| On-chain memory objects owned by an entity |
| none |
A note on block lookups by height
The endpoint retains a bounded recent window of blocks by height, so a height far below the current tip can return null even though it was a valid block. Lookups by hash work for any block the node still indexes. Call novai_get_chain_status first to learn the current tip height.
Development
npm install
npm run build
npm testnpm test runs the offline unit and validation tests. To exercise the live endpoint:
npm run test:liveAn end-to-end stdio check that spawns the built server and drives it with a real MCP client is available:
npm run build && node scripts/smoke.mjsLicense
MIT. See the LICENSE file.
Available Tools
12 toolsnovai_get_ai_entityNOVAI AI entity by idA
Fetch an on-chain AI entity (agent) by its entity id. Returns the entity record including code hash, creator, autonomy mode, capability bits, economic and stake balances, reputation score, transaction count, and activity timestamps, or null if no entity exists for that id.
Inputs: entity_id (required).
novai_get_balanceNOVAI account balanceA
Fetch the balance and nonce for an account or entity address. The balance is returned as a decimal string to preserve full precision.
Inputs: address (required).
novai_get_blockNOVAI block by height or hashA
Fetch a single committed block by height or by hash. Provide exactly one of height or hash. Returns the block height, block hash, parent hash, round, state root, and transaction count, or null if no such block is known. Note: the endpoint retains a bounded recent window of blocks by height, so very old heights can return null even though they were valid blocks. Lookups by hash work for any block the node still indexes.
Inputs: height, hash.
novai_get_chain_statusNOVAI chain statusA
Return the latest committed block of the live NOVAI chain: its height, block hash, round, transaction count, state root, and parent hash. Use this to verify the chain is live and advancing, and to learn the current tip height before requesting a specific block. Takes no parameters.
Inputs: no named parameters.
novai_get_memory_objectsNOVAI memory objects by entityA
List the on-chain memory objects owned by an entity. Each object has an object id, a numeric object type, owner, creation and update heights, and hex encoded data. Object type codes: 0 ChainSummary, 1 LabelIndex, 2 EmbeddingCommitment, 3 AnomalyLog, 4 StatisticsSnapshot, 5 ReputationEvent, 6 Rating, 7 SignalCatalog, 8 CompositionGraph, 9 VerificationRecord, 10 DelegationGrant, 11 Subscription, 12 ServiceDescriptor, 13 VkRegistration, 14 SlaAgreement, 15 PaymentChannel.
Inputs: entity_id (required).
novai_get_oracle_anchorNOVAI oracle anchor by signal hashA
Fetch a single oracle anchor by its signal hash. Returns the issuer entity, data hash, external timestamp, source hash, expiry and anchor heights, and data tag, or null if no anchor exists for that hash.
Inputs: signal_hash (required).
novai_get_oracle_anchors_by_entityNOVAI oracle anchors by issuer entityB
List oracle anchors issued by a given entity within a block height range, optionally filtered by an external timestamp range. Returns issuer entity, data hash, external timestamp, source hash, expiry and anchor heights, and data tag for each.
Inputs: entity_id (required), start_height (required), end_height (required), ts_min, +1 more.
novai_get_oracle_anchors_by_tagNOVAI oracle anchors by data tagA
List oracle anchors carrying a given data tag within a block height range, optionally filtered by an external timestamp range. Returns issuer entity, data hash, external timestamp, source hash, expiry and anchor heights, and data tag for each.
Inputs: data_tag (required), start_height (required), end_height (required), ts_min, +1 more.
novai_get_signals_by_heightNOVAI signals at a block heightA
List the signal commitments recorded at a specific block height. Each entry has a commitment hash, a numeric signal type, the height, and the issuer. Use this to see which signals were committed in a given block.
Inputs: height (required).
novai_get_signals_by_issuerNOVAI signals by issuerB
List the signal commitments issued by a given entity within a block height range. Returns commitment hash, signal type, height, and issuer for each.
Inputs: issuer (required), start_height (required), end_height (required).
novai_get_signals_by_typeNOVAI signals by typeA
List the signal commitments of a given type within a block height range. The endpoint currently accepts these signal type codes: 0 Anomaly, 1 Optimization, 2 Prediction, 3 RiskScore, 4 AuditReport, 5 SpamRisk, 6 CongestionForecast. Returns commitment hash, signal type, height, and issuer for each.
Inputs: signal_type (required), start_height (required), end_height (required).
novai_get_transactionNOVAI transaction by idA
Fetch a confirmed transaction by its transaction id. Returns the block height, transaction index, sender address, nonce, fee, and payload length, or null if the transaction is not found.
Inputs: txid (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 12 tools
Each tool targets a distinct resource or query pattern (entity, balance, block, chain status, memory objects, oracle anchors, signals, transaction). Even similar tools like the various oracle anchor and signal queries are differentiated by filter parameters (by entity, by tag, by height, by issuer, by type).
All tools follow a strict 'novai_get_<resource>' pattern in snake_case. The verb 'get' is used uniformly, and the resource names are descriptive and consistent.
With 12 tools covering block, transaction, account, entity, memory objects, oracle anchors, and multiple signal query dimensions, the count is well-scoped for a read-only blockchain explorer. No tool feels redundant or missing.
The tool set covers major query needs: chain status, blocks, transactions, balances, entities, memory objects, oracles, and signals. Minor gaps include lack of listing recent transactions or searching entities by name, but these are not essential for core functionality.
Maintenance
Related MCP Connectors
Blockchain RPC for 125+ chains: endpoints, method support, probing and RPC calls with your key.
Read chain data on 200+ networks and Sui: transactions, logs, balances, objects, ABI-decoded.
Read-only BlockReq docs, EVM JSON-RPC, and on-chain DEX and wallet data
USDC-gated Base JSON-RPC: free 10 req/min, $0.50 per 10k. Failover, cache, /mcp, ledger.
Related MCP Servers
- FlicenseBqualityNot gradedmaintenanceEnables AI-powered blockchain data queries and analysis through the Native Indexer (NIX) system. Supports querying blocks, transactions, account information, and network status across various blockchain networks.3-
- AlicenseBqualityDmaintenanceEnables natural language queries and JSON-RPC calls to 69+ blockchain networks through Grove's free public endpoints. Supports Ethereum, Solana, Cosmos chains, and Layer 2 solutions without requiring authentication or API keys.6712MIT
- AlicenseAqualityDmaintenanceProvides read-only access to the XRP Ledger for querying accounts, transactions, NFTs, DEX order books, and more.12MIT
- AlicenseAqualityCmaintenanceBlockchain JSON-RPC on 23 EVM chains for AI agents — Ethereum, Base, Arbitrum, plus young chains like Robinhood Chain, Plasma and Ink. Free reads with no key; heavy methods (eth_getLogs, trace, debug) via a free API key or x402 USDC pay-per-call.12334 npm1MIT