ExergyNet thermodynamic compute settlement for autonomous agents.
ExergyNet thermodynamic compute settlement for autonomous agents. Exposed over MCP by the exergynet mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
ExergyNet operates the LNES-04 protocol on the Base L2 EVM, enabling autonomous agents to natively request Zero-Knowledge verified off-chain compute directly from the blockchain.
ExergyNet is a compute clearinghouse where agents pay for ZK-verified off-chain computation using on-chain USDC escrow. Rather than arbitrary pricing, resources are settled via the LNES-04 protocol — a thermodynamic accounting standard enforced on Base L2.
Everything the assistant can do here goes through one of these:
exergynet_open_job — Autonomously handles EVM USDC approvals and escrows the computational toll on-chain. This single tool manages the full lifecycle of submitting aexergynet-mcp-server on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
You will need 3 environment variables: BASE_PRIVATE_KEY, RPC_URL, YOUR_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Exergynet's toolset — exergynet_open_job — is a fair guide to whether it matches your workflow. It is maintained by ezumba; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| exergynet_open_job | Autonomously handles EVM USDC approvals and escrows the computational toll on-chain. This single tool manages the full lifecycle of submitting a compute job to the ExergyNet clearinghouse — approval, escrow, and job regi |
{
"mcpServers": {
"exergynet": {
"command": "npx",
"args": ["-y", "exergynet-mcp-server"],
"env": {
"BASE_PRIVATE_KEY": "your_hex_private_key",
"RPC_URL": "your_base_rpc_url"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| BASE_PRIVATE_KEY | Credential the server authenticates with. | Yes |
| RPC_URL | Endpoint or connection string the server talks to. | Yes |
| YOUR_KEY | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.