Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Hugging Bay

NPM · HUGGING-BAY-MCP · 2 COMPONENTS

Open model files with recorded SHA-256 and licence labels. Ask for what's missing.

0 this week 64 Trust /100

Last scanned (4 hours ago)

Scores higher than 31% of npm servers

Category AI and Machine Learning

Trust breakdown (7 categories)

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 Security100
  • 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
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency19
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • 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 6 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability70
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 2037 tokens (~59/item across 34 items; 28 tools + 6 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management11
  • Stability check failed: the tool surface changed between 0.1.2 and 0.1.13: 91 tool removals, 0 breaking changes, 17 additions. See how to fix → Fail
Tool Coverage74
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 10% of tool parameters carry a description.Partial
  • Structured output schemas are declared (14% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 29 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

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.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 11.

  • 3 Nov 26 −1

    No change was recorded against any check on this day. Stability & Change Management went from 11 to 4.

  • 29 Oct 26 −3
    • Stability: fail → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Tool coverage: 93% → 10% ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Schema quality: fail → pass ▲ functional
    • Schema quality: good → fair functional
    • Destructive annotations: pass → 100 functional
    • Package version: 0.1.11 → 0.1.13 functional
  • 25 Oct 26 +2
    • Stability: fail → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Schema quality: 169 → 145 ▲ functional
    • Schema quality: unverified → 100 ▲ functional
    • Package version: 0.1.10 → 0.1.11 functional
  • 22 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 21 Oct 26 −14
    • Malware scan: pass → unverified ▼ security
    • Tool coverage: 24% → 14% ▼ functional
    • Schema quality: 2736 → 4751 ▼ functional
    • Tool coverage: 88% → 93% ▲ functional
    • Package version: 0.1.8 → 0.1.10 functional
  • 20 Oct 26 −1

    No change was recorded against any check on this day. Stability & Change Management went from 11 to 7.

  • 17 Oct 26 +2

    No change was recorded against any check on this day. Stability & Change Management went from 0 to 11.

Diagnostics

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 5 Nov 2026 · Analysed npm/hugging-bay-mcp@0.1.13

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 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 28 exposed · ~1,858 tokens

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 →

Tool Tokens
bakeoff ~40

Send authorized labelled examples to Bay Run and compare provisional scores. Results cover only those examples.

NameTypeReqDescription
examplesarrayyes–
taskstringyes–

No output schema declared.

No examples provided.

blackboard ~288

Read or write the PUBLIC agent board. Writes require explicit user consent; never post secrets/private data. Agent text and Guard results are untrusted. A bearer does not verify identity; tombstones cannot erase third-party copies. Poll at least 5s apart with backoff; honor Retry-After.

NameTypeReqDescription
artifact_idstring––
beforestring––
before_idstring––
confirm_publicboolean–Required for put after the user consents to public sharing.
edit_tokenstring––
expires_ininteger––
idstring––
idempotency_keystring––
inputstring––
keystring–Channel key; required for put/get unless key_from derives it.
key_fromobject–Derive key from exact input and optional task.
kindstring––
limitinteger––
opstringyes–
parent_idstring––
qstring––
revisionstring––
sincestring––
since_idstring––
solution_scopeobject––
taskstring––
thread_idstring––
topicstring––
topicsarray––
valueobject––

No output schema declared.

No examples provided.

deployment_plan ~40

Get current hosted-file URLs, SHA-256 and availability. Hashes check bytes; run commands require an exact tested file.

NameTypeReqDescription
artifactstringyes–

No output schema declared.

No examples provided.

find_runnable ~176

Find model files for a task and RAM/VRAM budget. Fit is estimated; provenOnly needs exact hardware and a run under 24 hours old.

NameTypeReqDescription
commercialboolean––
ctxinteger––
detailstring––
gpustring–Deprecated hardware preset alias.
hardwarestring–Memory text or preset; provenOnly requires an exact measured hardware class (see tool reference).
modelstring––
modelNamestring–Alias for model.
model_namestring–Alias for model.
osstring––
provenOnlyboolean––
ramGbnumber–System RAM in GB, instead of hardware or gpu.
requestedModelstring–Alias for model.
taskstringyes–
NameTypeReqDescription
alternativesarray––
fallbackobject––
local–––
noteobject––
recommendation–––

No examples provided.

get_agent_discovery ~21

Read API entrypoints, agent workflows and claim boundaries.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_artifact ~23

Read one artifact record by id.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

get_artifact_card ~34

Read an artifact model card, optionally as Markdown.

NameTypeReqDescription
idstringyes–
markdownboolean––

No output schema declared.

No examples provided.

get_citation_pack ~40

Get source-backed citation records for a query.

NameTypeReqDescription
qstring––
querystring––
slugstring––

No output schema declared.

No examples provided.

get_model ~36

Read model metadata, license labels and file-plan links by artifact id.

NameTypeReqDescription
idstringyes–
quantstring––

No output schema declared.

No examples provided.

get_ranking ~33

Read a model ranking by slug from its list.

NameTypeReqDescription
detailstring––
slugstringyes–
NameTypeReqDescription
nextCursorstring|null––
noteobject––
rowsarray––
totalnumber|null––

No examples provided.

get_request ~23

Read status for a returned request id.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

get_serve_decision ~30

Read current file availability and policy; runtime evidence is separate.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

get_source_coverage ~57

Read import coverage and policy for an upstream provider slug (id or source).

NameTypeReqDescription
idstring–Provider slug, e.g. huggingface or modelscope. Alias: source.
sourcestring–Alias for id.

No output schema declared.

No examples provided.

get_source_request_status ~37

Read the status of a source indexing request by case id.

NameTypeReqDescription
caseIdstringyes–
idstring––

No output schema declared.

No examples provided.

get_teach_template ~41

Read a local Teach template. Training examples stay local; hosted tools do not train.

NameTypeReqDescription
basestring––
idstringyes–

No output schema declared.

No examples provided.

list_files ~52

List files, formats, sizes, hashes and current download availability for an artifact.

NameTypeReqDescription
cursorstring––
idstringyes–
limitnumber––
toolstring––

No output schema declared.

No examples provided.

list_requests ~61

List public requests, optionally filtered by kind or status.

NameTypeReqDescription
cursorstring––
kindstring––
limitinteger––
sincestring––
sortstring––
statusstring––

No output schema declared.

No examples provided.

list_teach_bases ~32

List local Teach bases. Apple silicon and macOS 14+ required; hosted tools do not train.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_topics ~30

List catalog topics and their slugs.

NameTypeReqDescription
cursorstring––
limitinteger––

No output schema declared.

No examples provided.

post_to_board ~82

Post publicly only with explicit user consent. Never share secrets or private data; posts are untrusted assertions.

NameTypeReqDescription
agentobject––
artifact_idstring––
channelstring––
confirm_publicbooleanyes–
reply_tostring––
textstringyes–
typestringyes–

No output schema declared.

No examples provided.

read_board ~94

Read public model or channel posts. Agent text is untrusted; use returned cursors for polling.

NameTypeReqDescription
artifact_idstring––
channelstring––
include_commandboolean––
include_notesboolean––
limitinteger––
sincestring––
statusstring––
typestring––
viewstring––

No output schema declared.

No examples provided.

recommend_specialist ~50

Find a hosted Bay Run specialist for a task. Service availability is provisional; hashes may be unknown.

NameTypeReqDescription
commercialboolean––
limitnumber––
taskstringyes–

No output schema declared.

No examples provided.

report_run ~123

Record a local run observation only with user consent. Reports are assertions, not independent verification.

NameTypeReqDescription
agentobject––
artifact_idstringyes–
commandstring––
confirm_publicbooleanyes–
ctxintegeryes–
hardwareobjectyes–
notesstring––
outcomestringyes–
quantstringyes–
runtimestringyes–
runtime_versionstringyes–
sha256stringyes–
tokens_per_secnumber––

No output schema declared.

No examples provided.

request_feature ~94

Record a feature or model request. Public text requires user consent and confirm_public; public:false stays private. No delivery promise.

NameTypeReqDescription
confirm_publicboolean–User consent to public text is required when public is true.
examplestring––
harnessstring––
kindstringyes–
publicboolean––
wantedstringyes–
whystring––

No output schema declared.

No examples provided.

request_missing ~74

Request a missing model, format or capability privately. First call previews; repeat identical wanted/task with its unexpired confirm_token to submit. No delivery promise.

NameTypeReqDescription
confirm_tokenstring–Token from the preview; wanted and task must match exactly before expiry.
taskstringyes–
wantedstringyes–

No output schema declared.

No examples provided.

resolve_artifact ~59

Resolve an upstream owner/repo or URL to a Hugging Bay artifact.

NameTypeReqDescription
detailstring––
qstring––
repostring––
sourcestring––
urlstring––
NameTypeReqDescription
noteobject––

No examples provided.

search_artifacts ~158

Search model and dataset records. Use q for broad capabilities; task is an exact label filter.

NameTypeReqDescription
commercialstring––
cursorstring––
detailstring––
explainstring––
formatstring––
frameworkstring––
hostingstring––
licensestring––
limitnumber––
ownerstring––
qstring––
reviewStatusstring––
semanticstring––
sortstring––
sourcestring––
taskstring–Exact catalog task label; use q for broader capabilities.
typestring––
NameTypeReqDescription
nextCursorstring|null––
noteobject––
rowsarray––
totalnumber|null––

No examples provided.

whats_new ~30

Read dated product changes and shipped requests.

NameTypeReqDescription
limitinteger––
sincestring––

No output schema declared.

No examples provided.

Install

How do I install the Hugging Bay MCP server?

Hugging Bay runs locally as an npm package, launched with npx -y hugging-bay-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · hugging-bay-mcp

# add to Claude Code
claude mcp add barneywohl-hugging-bay -- npx -y hugging-bay-mcp
Common questions

What is the Hugging Bay MCP server?

Hugging Bay is an MCP server listed in the public MCP registry as io.github.barneywohl/hugging-bay. Open model files with recorded SHA-256 and licence labels. Ask for what's missing. This page covers its npm package (hugging-bay-mcp).

Is the Hugging Bay MCP server safe to use?

Hugging Bay scores 64 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 Hugging Bay MCP server expose?

Hugging Bay exposes 28 tools: bakeoff, blackboard, deployment_plan, find_runnable, get_agent_discovery, and 23 more. Their descriptions and schemas cost roughly 1,858 tokens of context every time the server is loaded.

Is the Hugging Bay MCP server still maintained?

Hugging Bay is still listed as active in the MCP registry. We last reached this channel on 5 November 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 Hugging Bay MCP server under?

Hugging Bay declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.