@trusty-squire/mcp
It needs code that is built by install scripts, which this runner does not run. Run 2026-11-16.
Needs to start: unclear. Its error said: ve binding failed for Node v24.22.2 (NODE_MODULE_VERSION 137) in /app/node_modules/better-sqlite3. The published package has no prebuilt .node; npx will not rebuild an already-extracted version. Run:
Contacts while installing and starting: github.com, release-assets.githubusercontent.com
What it contacted
github.comrelease-assets.githubusercontent.com: a release file downloaded from GitHub
Hosts it looked up or connected to while installing and starting with no input, watched from outside its sandbox. The npm registry is left out. Says nothing about what its tools contact when called.
Starting it
npx -y @trusty-squire/mcp@1.1.43
Installing a package runs its code. Use a sandbox for anything you have not read.
What it said when it did not start
ve binding failed for Node v24.22.2 (NODE_MODULE_VERSION 137) in /app/node_modules/better-sqlite3. The published package has no prebuilt .node; npx will not rebuild an already-extracted version. Run: npm rebuild better-sqlite3 --prefix /app Rebuild output: prebuild-install: (node:67) [DEP0176] DeprecationWarning: fs.R_OK is deprecated, use fs.constants.R_OK instead (Use `node --trace-deprecation ...` to show where the warning was created) prebuild-install warn install EACCES: permission denied, mkdir '/app/node_modules/better-sqlite3/build' exit 1 npm rebuild: spawnSync npm ENOENT Could not locate the bindings file. Tried: → /app/node_modules/better-sqlite3/build/better_sqlite3.node → /app/node_modules/better-sqlite3/build/Debug/better_sqlite3.node → /app/node_modules/better-sqlite3/build/Release/better_sqlite3.node → /app/node_modules/better-sqlite3/out/Debug/better_sqlite3.node → /app/node_modules/better-sqlite3/Debug/better_sqlite3.node → /app/node_modules/better-sqlite3/out/Release/better_sqlite3.node → /app/node_modules/better-sqlite3/Release/better_sqlite3.node → /app/node_modules/better-sqlite3/build/default/better_sqlite3.node → /app/node_modules/better-sqlite3/compiled/24.22.2/linux/x64/better_sqlite3.node → /app/node_modules/better-sqlite3/addon-build/release/install-root/better_sqlite3.node → /app/node_modules/better-sqlite3/addon-build/debug/install-root/better_sqlite3.node → /app/node_modules/better-sqlite3/addon-build/default/install-root/better_sqlite3.node → /app/node_modules/better-sqlite3/lib/binding/node-v137-linux-x64/better_sqlite3.node
Written by the package or by npm, not by this site.
Files it wrote
/tmp/ .npm/ _prebuilds/ d463a5-better-sqlite3-v12.11.1-node-v137-linux-x64.tar.gz
Paths inside its sandbox, where its home folder is /tmp and its own folder cannot be written to.
Install facts
| License | MIT |
|---|---|
| Needs | node >=20 |
| Source | github.com/Trusty-Squire/trusty-squire |
| Install scripts | better-sqlite3, sharp declare them. This runner does not run them. |
| Tarball | sha512-IUCEOniI+Kb897Mo1SdDyCxzQN+60TsOFjkv+hGF0OwH8LcchDoFslSYGkRPG5HfIm0nfLxU6voMWdw1aIv26Q== |
Versions reported
| Version | Run | Result | Tools |
|---|---|---|---|
| 1.1.43 | 2026-11-16 | Needs a build step at install | 0 |
| 1.1.39 | 2026-11-12 | Needs a build step at install | 0 |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/%40trusty-squire/mcp)
New version out? Ask for a fresh report.