MCP Gateway | ExergyNet

STATUS NOTICE — ZK Compute Settlement

ZK-STARK compute settlement is operating in testnet mode. Status labels on this page reflect the target ExergyNet compute architecture. On-chain ZK proof verification for the compute grid is in development. See On-Chain Proof for current contract and verification status.

WRITE SETTLEMENT: TEMPORARILY DISABLED PENDING VERIFIED PRODUCTION MIGRATION

The HTTP/Ed25519 handshake and exergynet_open_job write-settlement flow documented below describe ExergyNet's target compute-settlement architecture — they are not currently operational, and no transaction is created or broadcast by following them. For a currently working, read-only MCP integration, see the exergynet-mcp-server npm package, whose own write path is likewise disabled pending the same migration — see its security advisory for detail.

Gateway Endpoint

Connection Coordinates

Endpoint https://exergynet.org/mcp
Protocol Model Context Protocol (MCP)
Method HTTP POST
Auth Ed25519 signature of method||timestamp|nonce
Replay Guard60-second timestamp window

Handshake Protocol — Target Design, Not Yet Live

Ed25519 Authentication

This is the target handshake for the write-settlement gateway once it migrates to production: requests would be signed with an agent's Solana Ed25519 private key to prevent replay attacks and MITM intercepts. This handshake is not active today — the endpoint does not currently process signed requests.

Step 01 — Generate Entropy

const timestamp = Math.floor(Date.now() / 1000);
const nonce = crypto.randomBytes(8).toString('hex');

Step 02 — Construct Payload

const message = `${method}||${timestamp}|${nonce}`;

Step 03 — Sign

const signature = nacl.sign.detached(
  Buffer.from(message), 
  agentKeypair.secretKey
);

Step 04 — POST Payload

{
  "method": "exergynet_open_job",
  "client_id": "",
  "timestamp": 1777728610,
  "nonce": "a1b2c3d4e5f60718",
  "signature": ""
}

Target Success Response (once live)

{ "status": "proxy_initiated", "verified": true }

This is the intended response shape once write settlement migrates to production. Today, no request to this endpoint clears an agent to broadcast a transaction — the write path is disabled.

Available Methods

MCP Action Reference

Method	Description	Cost
exergynet_open_job	Target: initiate a compute job, locking SOL escrow. Write settlement is temporarily disabled pending verified production migration — no job is opened and no transaction is created today.	Disabled
exergynet_status	Query execution status by job ID	Read-only
exergynet_get_proof	Retrieve the on-chain settlement record for a completed job	Read-only

LNES-03 compute-job settlement is designed around a RISC Zero-produced ZK-STARK proof; see On-Chain Proof for which contracts currently enforce on-chain verification versus recording a receipt pending it. This is a separate mechanism from the VMN/memory-query receipt, which returns a SHA-256 content hash, not a ZK proof.

ElizaOS Plugin

Native Plugin Integration

For ElizaOS agents, the official plugin handles the full MCP handshake automatically.

pnpm install @elizaos/plugin-exergynet

Deploy Your First MCP-Enabled Agent

Integration Guide Agent Manifest

MCPGateway