io.github.ezumba/exergynet
NPM · EXERGYNET-MCP-SERVER · SCANNED SEP 20
Read-only ExergyNet MCP lookups and compute-cost estimates; write settlement is disabled.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 22 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 255 tokens (~51/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.ezumba/exergynet MCP server?
io.github.ezumba/exergynet runs locally as an npm package, launched with npx -y exergynet-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · exergynet-mcp-server
claude mcp add ezumba-exergynet -- npx -y exergynet-mcp-server
{
"mcpServers": {
"ezumba-exergynet": {
"command": "npx",
"args": [
"-y",
"exergynet-mcp-server"
]
}
}
} {
"servers": {
"ezumba-exergynet": {
"command": "npx",
"args": [
"-y",
"exergynet-mcp-server"
]
}
}
} codex mcp add ezumba-exergynet -- npx -y exergynet-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ezumba-exergynet": {
"type": "local",
"command": [
"npx",
"-y",
"exergynet-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add ezumba-exergynet --command npx --arg -y --arg exergynet-mcp-server
mcp_servers:
ezumba-exergynet:
command: "npx"
args: ["-y", "exergynet-mcp-server"] {
"McpServers": {
"ezumba-exergynet": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"exergynet-mcp-server"
]
}
}
} assistant mcp add ezumba-exergynet -t stdio -c npx -a -y exergynet-mcp-server
{
"mcpServers": {
"ezumba-exergynet": {
"command": "npx",
"args": [
"-y",
"exergynet-mcp-server"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 −3
- Stability: pass → 0.80 functional
- 18 Sept 26 +1
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −3
- Stability: pass → 0.80 functional
- 11 Sept 26 +1
- Stability: 0.97 → pass security
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
- Security disclosure: fail → pass ▲ functional
- Package version: 0.1.10 → 0.2.6 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/exergynet-mcp-server@0.2.6
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
exergynet_estimate_gate ~70
Local arithmetic only. Compares an external compute cost estimate against a settlement cost plus risk margin. Makes no network call and touches no on-chain state.
| Name | Type | Req | Description |
|---|---|---|---|
| externalComputeCostUsd | number | yes | – |
| riskMarginUsd | number | – | – |
| settlementCostUsd | number | yes | – |
No output schema declared.
No examples provided.
exergynet_get_program_id ~55
Returns the LNES-03 Solana Mainnet program ID. Does not return a Base L2 contract address — see https://exergynet.org/proof.html for current, verified Base contract addresses and status.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
exergynet_get_proof_transaction ~24
Returns a reference LNES-03 settlement transaction signature.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
exergynet_open_job ~57
DISABLED pending safe contract migration (security advisory 2026-08-28). Always returns a fail-closed message. Does not construct, sign, or submit any transaction, and does not read or require any private key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
exergynet_verify_program ~49
Read-only check of whether the LNES-03 Solana program account exists and is executable on the given (or default) Solana RPC endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| rpcUrl | string | – | – |
No output schema declared.
No examples provided.
What is the io.github.ezumba/exergynet MCP server?
io.github.ezumba/exergynet is an MCP server listed in the public MCP registry as io.github.ezumba/exergynet. Read-only ExergyNet MCP lookups and compute-cost estimates; write settlement is disabled. This page covers its npm package (exergynet-mcp-server).
Is the io.github.ezumba/exergynet MCP server safe to use?
io.github.ezumba/exergynet scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.ezumba/exergynet MCP server expose?
io.github.ezumba/exergynet exposes 5 tools: exergynet_open_job, exergynet_estimate_gate, exergynet_get_program_id, exergynet_verify_program, exergynet_get_proof_transaction. Their descriptions and schemas cost roughly 255 tokens of context every time the server is loaded.
Is the io.github.ezumba/exergynet MCP server still maintained?
io.github.ezumba/exergynet is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.ezumba/exergynet MCP server under?
io.github.ezumba/exergynet declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.