MCP servers › io.github.stackhands › eb-stack
MCP server · registry snapshot 2026-11-18 · last checked 2026-11-18
eb-stack MCP server
Registry name io.github.stackhands/eb-stack
by stackhands · GitHub account (the registry's namespace rule)repository: same ownerSource ↗Website ↗
Plan EasyBuild recipes, CycloneDX SBOMs, and Resolvo stack locks. — the publisher's description
Summary
io.github.stackhands/eb-stack is a local MCP server listed in the official MCP registry at version 0.8.0, under the namespace of the GitHub account stackhands. Its linked repository, github.com/stackhands/eb-stack, belongs to the same GitHub account.
Record checks
5 of 5 record checks met · 4 do not apply
- met: Registry entry is active and says how to run it
- met: Source repository link opens
- met: Repository is not archived
- met: Code pushed to the repository in the 90 days before our check
- met: Repository publishes a security policy (SECURITY.md)
- not applicable: Package names its licence with a standard (SPDX) identifier
- not applicable: The version the registry lists can be installed and is not withdrawn
- not applicable: npm package carries build provenance (attestation)
- not applicable: No known critical or high advisory in the package or its dependencies
- Not ranked by downloads: not an npm or PyPI package
- Not ranked by stars: 1 star (ranked from 10)
From public records, not a safety rating. Each check with its reason · Is it safe to install?
Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it
Key facts
- Runs
- local package
- Transport
- standard input/output
- Your own values
- none declared (not a guarantee)
- Package
- Cargo
- Repository
- public
- Last tested
- not tested
Tool list
Not read: It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's. So there is no tool-list size and no result from the three APIs.
How fresh this is
- Live-tested
- no
- Last tested
- not tested
- Latest version
- 0.8.0, published 2026-11-18 (registry, as of the 2026-11-18 snapshot)
- First listed version
- 2026-11-13 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 2 versions listed, 2026-11-13 to 2026-11-18; 2 in the 90 days before the 2026-11-18 snapshot.(versions still listed in the registry only)
Most recent 2 versions
0.8.0· 2026-11-180.7.4· 2026-11-13
- Registry data
- snapshot 2026-11-18
- Package and repository
- checked 2026-11-18
Dead or stale signals
None found in the records we hold
Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.
Changes since the last refresh
Version 0.7.4 (published 2026-11-13) → 0.8.0 (published 2026-11-18), between the registry lists of 2026-11-17 and 2026-11-18.
The publisher’s GitHub release note for v0.8.0 (“0.8.0 - 2026-11-18”), published 2026-11-18.
Read the release note (the publisher’s text, shown as plain text, cut at 4,000 characters)
## Release Notes
### Added
- `ledger backfill`, `ledger anchor`, `ledger verify-anchors` and `ledger project` maintain a ledger in process. `backfill` appends a `finding` record for each observation of a manifest pinned by its SHA-256, at the observation time, and a rerun appends nothing. `anchor` signs the day's head and publishes it once as `ANCHORS/YYYY-MM-DD.head.json` after `verify` proves it binds to the log and extends the latest anchor; `verify-anchors` proves the chain. `project` writes `index.json`, `index.md` and per-package JSON and Markdown history from a log whose signed head covers every record. Each prints one JSON object and exits 2 when refused; `backfill` and `anchor` exit 75 when an append or a signature did not finish. Each has an MCP tool: `eb_ledger_backfill`, `eb_ledger_anchor`, `eb_ledger_verify_anchors` and `eb_ledger_project`.
### Fixed
- A `from-commit` read uses a directory it created for that read. It no longer shares `eb-stack-from-commit-<pid>` with every other read in the process, and it does not remove a directory that was already there.
- A failed verification command is a `sanity` finding, or `timeout`, unless its output names a transport, executor, runtime, or resource cause, so an Lmod `error:` line no longer makes it `compile`. Finding summaries and campaign history name the class and exit status as the state file does, `sanity` and `exit 1`, not `Sanity` and `exit Some(1)`.
- A generated stack policy is a new file for each solve. The MCP server no longer reuses `eb-stack-policy-<toolchain>-<pid>.json`, and it removes the file when the solve returns.
- A job `stack admit` refuses for want of inodes carries a `refusal`: the inodes it is short, then the `available`, `reserved`, `footprint` and `margin` that decided it. It was `null`, so only a failed quota or scheduler command said why.
- A lock's timestamp is `SOURCE_DATE_EPOCH` when that variable is a number of seconds. Two solves of the same inputs then write the same time.
- A pin on a package the trees have only outside the solve's toolchain hierarchy, in a `stack solve` policy or a `package plan` / `package bump` stack policy, now fails with the hierarchy searched and the toolchains the trees have the package on, instead of "unknown package" and "names a package with no candidate at all". A stack-policy exclusion gets the same message.
- A step of the Cargo prelude that fails stops EasyBuild's install command again: the host triple is read inside the prelude's `&&` chain, not after `_triple="";`, whose semicolon ended the chain. A missing or failing `rustc` still leaves the triple empty, even under `pipefail`.
- A verification command runs with the module tree of the attempt's install path, `<installpath>/modules/all` by default, first on `MODULEPATH` and on `EESSI_EXTRA_MODULEPATH`, so `module load {module}` finds the module the attempt built, also after the EESSI init replaces `MODULEPATH`.
- Compatible-release, caret, and tilde requirements exclude a pre-release of the next series. `1.3.0rc1` is outside `~=1.2.0` and `~1.2.3`, and `2.0.0rc1` is outside `^1.2.0`.
- Date versions such as LAMMPS's `29Aug2024` compare by year, month and day, and a following `_updateN` by its number, so `stack gap` names a LAMMPS `22Jul2025_update4` recipe as the newest outside the generation instead of `29Aug2024`. Requirements such as `>=29Aug2024` compare the same way.
- The CI smoke step on the eOn core fixture checks `eOn-2.17.10-foss-2026.1.eb`, the recipe the fixture holds, and passes only when `recipe check` fails on the stack dependencies the drafts leave out, with the drafts supplying quill, readcon-core and rgpot. It named the 2.17.2 recipe the fixture no longer has, so it passed on "No such file or directory" without checking anything. `tests/eon_core_rgpot.rs` runs the step as CI runs it.
- The `package plan` residuals for an inferred moduleclass and for a dropped build requirement, and the source finding for a tree that declares no verSource: the official MCP Registry list on 2026-11-17 and on 2026-11-18; release notes from the GitHub Releases API, checked 2026-11-18.
What it is
How do I add it to my client?
Config from the registry entry
- No config: no ready-made command for the Cargo crate; use the publisher's instructions.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
What do the published files and outside lists say?
Read as text · nothing run · no tool called
Package files
- MCP SDK in the package files. Not read yet: added with the next daily run.
- Build workflow. Not read yet: added with the next daily run.
Outside lists
- CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-18. This product uses the NVD API but is not endorsed or certified by the NVD.
- GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-18. GitHub Advisory Database, CC BY 4.0
- Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-18. Source: read 2026-11-18.
- Cline marketplace. Not in the Cline marketplace on 2026-11-18. Source: read 2026-11-18.
Own host
- security.txt. No security.txt at https://eb-stack.rgoswami.me/.well-known/ (HTTP 200, 2026-11-18). Source: eb-stack.rgoswami.me/.well-known/security.txt · read 2026-11-18.
- A2A agent card. No A2A agent card at https://eb-stack.rgoswami.me/.well-known/ (HTTP 200, 2026-11-18). Source: eb-stack.rgoswami.me/.well-known/agent-card.json · read 2026-11-18.
Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read
Does the registry listing match what we found?
Feature #6The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Repository github.com/stackhands/eb-stack | Opens publicly | matches | api.github.com · 2026-11-18 |
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- io.github.stackhands
- GitHub owner
- an organization (stackhands)
- Repository
- github.com/stackhands/eb-stack
- Stars
- 1
- Repository age
- 91–180 days
- Last push
- 0–30 days ago
- Archived
- no
- Security policy
- SECURITY.md
Source: the registry entry and api.github.com · 2026-11-18; security policy read from GitHub · 2026-11-14.
Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.
Choosing
Record checks
Public records · not a safety rating5 of 5 record checks met · 4 do not apply
- Not ranked by downloads: not an npm or PyPI package
- Not ranked by stars: 1 star (ranked from 10)
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- MetSource repository link opensThe linked GitHub repository is public.
- MetRepository is not archivedNot archived.
- MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
- MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
- Does not applyPackage names its licence with a standard (SPDX) identifierNot an npm or PyPI package.
- Does not applyThe version the registry lists can be installed and is not withdrawnNot an npm or PyPI package.
- Does not applynpm package carries build provenance (attestation)PyPI packages have no npm-style attestation.
- Does not applyNo known critical or high advisory in the package or its dependenciesNot an npm or PyPI package.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-18 (security policy 2026-11-14). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral
Common questions about io.github.stackhands/eb-stack
Answered from the data aboveWho publishes io.github.stackhands/eb-stack?
The registry ties the namespace io.github.stackhands to the GitHub account stackhands; only its owner can publish under it. Its linked repository, github.com/stackhands/eb-stack, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.
Is io.github.stackhands/eb-stack safe to install?
We do not rate servers as safe or unsafe. 5 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.
Has io.github.stackhands/eb-stack been security tested?
No. It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's.
Does io.github.stackhands/eb-stack publish a security policy?
Yes: its repository has a public security policy (github.com/stackhands/eb-stack/blob/HEAD/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.
Where is the source code of io.github.stackhands/eb-stack?
In github.com/stackhands/eb-stack, which opens publicly.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
Has it been tested?
Feature #1It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's. — our limit
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “io.github.stackhands/eb-stack: MCP server record.” Data checked 2026-11-18. https://protocolprobe.com/mcp/servers/io.github.stackhands/eb-stack
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/io.github.stackhands/eb-stack)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).
Write to hello@protocolprobe.com · corrections log · methodology