hugging-bay-mcp
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Returns a result when called with no setup: 1 of 1 tool tried
Contacts while installing and starting: nothing
Its tool definitions changed since version 0.1.16. If you approved the earlier ones, read them again.
What it contacted
Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.
Starting it
npx -y hugging-bay-mcp@0.1.17
Installing a package runs its code. Use a sandbox for anything you have not read.
Calling its tools
1 tool that takes no input and looks read-only was called once with nothing. 1 returned a result.
search_artifacts | Returned a result 1.5 s · 219 characters |
During the calls (not necessarily because of them) it first contacted: huggingbay.xyz.
Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
find_runnable model, task, provenOnly, hardware, ramGb, commercial, ctx, os, detail
Models for a task and RAM or VRAM budget (estimated fit), not fine-tuning. provenOnly: tested commands and a signed receipt, only for an exact hardware class run in the last 24 hours. Download is not run proof; read no-match reasons. Example: {"task":"chat","hardware":"8gb-laptop"}.search_artifacts q, owner, limit, cursor, sort, type, license, task, framework, format, hosting, reviewStatus, source, commercial, semantic, explain, detail
Keyword search over model and dataset records with task, license and format filters, when you have no exact name. Returns ids and short summaries; detail=full adds the full record. Example: {"q":"embedding","limit":5}.get_model id, quant
One model by id: license, download readiness, main file, SHA-256, size, RAM estimate, and tested runKit commands when that exact file has run. If unavailable, follow the retry guidance.
get_download id, path
One exact file in one call: a signed link (at most 300 s), SHA-256, size, license, hb.lock text and run commands. Check the hash after download.
get_serve_decision id
Whether a model's listed files are offered to download now, with the recorded reason. Runtime evidence is separate.
hb_run_plan task, hardware
Best model with a fresh signed run on your exact hardware class: a recorded command and hb.lock, or an explicit no-match. Most hardware has no run yet; call find_runnable first. Never downloads or runs. Example: {"task":"chat","hardware":"apple-m2-16gb"}.ask_url q
Build a link locally for a human to ask their own AIs in Tug. Show the question and link to the person before sharing. Only a draft opens; the person presses Send. The question stays in the URL fragment. Does not contact Hugging Bay, post, send, or run anything.
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | MIT |
|---|---|
| Needs | node >=18.17 |
| Source | github.com/barneywohl/hugging-bay |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-VuoFWUxxkyOAZin2pv0Yqs9uUk0Ok+y/Fo2nPJrzRi29TS7f0eFt5X2t/DX86o+GfBpGS3nhSoBrMMb12+iUbQ== |
Versions reported
| Version | Run | Result | Tools |
|---|---|---|---|
| 0.1.17 | 2026-11-16 | Starts with no setup | 7 |
| 0.1.16 | 2026-11-12 | Starts with no setup | 6 |
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/hugging-bay-mcp)
New version out? Ask for a fresh report.