io.github.ezumba/exergynet

MCPcommunity
v0.1.10io.github.ezumbaUnknownUpdated 5mo agonpmGitHub

ExergyNet thermodynamic compute settlement for autonomous agents.

The official MCP server for the ExergyNet physical-reality ZK proof infrastructure. ExergyNet operates the LNES-04 protocol on Base L2 EVM and LNES-03 on Solana Mainnet. Android edge witnesses capture physical sensor data (GPS, camera, magnetometer, NFC, network density), desktop provers compress payloads to ZK-STARK receipts, and agents pay USDC for verified physical truth. ExergyNet is a…

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
5mo agoLast update
Package
Authorio.github.ezumba
LicenseUnknown
Version0.1.10
Sourcemcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies60 resolved · 1 with advisories
Tool surface5 tools · none privileged
Security scan✓ Cleanv0.2.2 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

5 tools · none privileged
Statically extracted from the published packagev0.2.2 · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

exergynet_open_jobNo description published

This tool published no description. Forge does not invent one.

exergynet_estimate_gateNo description published

This tool published no description. Forge does not invent one.

exergynet_get_program_idNo description published

This tool published no description. Forge does not invent one.

exergynet_verify_programNo description published

This tool published no description. Forge does not invent one.

exergynet_get_proof_transactionNo description published

This tool published no description. Forge does not invent one.

0 of 5 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

The official MCP server for the ExergyNet physical-reality ZK proof infrastructure. ExergyNet operates the LNES-04 protocol on Base L2 EVM and LNES-03 on Solana Mainnet. Android edge witnesses capture physical sensor data (GPS, camera, magnetometer, NFC, network density), desktop provers compress payloads to ZK-STARK receipts, and agents pay USDC for verified physical truth. ExergyNet is a sovereign DePIN compute clearinghouse. Physical sensor readings from Android edge witnesses are…

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.