io.github.bzdOS/hubd
NPM · @BZDOS/HUBD · SCANNED AUG 4
The project tracker for teams of humans and AI agents — in plain files. MCP server + CLI.
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 →
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 & Transparency45
- 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 8 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1409 tokens (~82/item across 17 items; 17 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage85
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 56% of tool parameters carry a description.Partial
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @bzdos/hubd
claude mcp add bzdos-hubd -- npx -y @bzdos/hubd
codex mcp add bzdos-hubd -- npx -y @bzdos/hubd
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"bzdos-hubd": {
"type": "local",
"command": [
"npx",
"-y",
"@bzdos/hubd"
],
"enabled": true
}
}
} openclaw mcp add bzdos-hubd --command npx --arg -y --arg @bzdos/hubd
mcp_servers:
bzdos-hubd:
command: "npx"
args: ["-y", "@bzdos/hubd"] {
"mcpServers": {
"bzdos-hubd": {
"command": "npx",
"args": [
"-y",
"@bzdos/hubd"
]
}
}
} 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.
- 4 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Aug 26 +3
- Stability: unverified → 0.23 ▲ functional
- 1 Aug 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Jul 26 −11
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 +33
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 56 functional
- First check of Schema quality: good functional
- 26 Jul 26 47
First indexed and scored.
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 4 Aug 2026 · Analysed npm/@bzdos/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 0 packages
0 packages in the resolved dependency tree.
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.
hub_brief ~64
Morning brief across all projects: open tasks (deadlines first), journal since N hours, stale cards, active claims.
| Name | Type | Req | Description |
|---|---|---|---|
| hours | integer | — | journal window, default 48 |
| staleDays | integer | — | card considered stale after N days, default 7 |
No output schema declared.
No examples provided.
hub_card_set ~104
Create or update a project card from just a name and a digest — no folder needed (unlike hub_sync). Use it to capture a project that is not a local git checkout, e.g. when harvesting a dialog. Preserves any hand-written frontmatter and Facts.
| Name | Type | Req | Description |
|---|---|---|---|
| by | string | — | who is writing |
| digest | string | yes | the card digest: 3-6 lines of current state |
| project | string | yes | project name or slug |
No output schema declared.
No examples provided.
hub_claim ~72
Soft-lock a work area so other agents see it (e.g. area="public/index.html"). Not enforced — informational.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | yes | — |
| area | string | yes | — |
| note | string | — | — |
| project | string | yes | — |
| ttlMin | integer | — | default 240 |
No output schema declared.
No examples provided.
hub_get ~58
Everything about ONE project: its full card (digest + facts), recent journal entries for it, and any active soft-locks. Use after hub_status or hub_search points you at a project.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | yes | project slug or name |
No output schema declared.
No examples provided.
hub_graph ~105
The typed relationship graph across projects AND resources: who runs where, what depends on / deploys to / exposes what. Edges are frontmatter [[links]] keyed by relation (runs_on, depends_on, deploys_to, exposes, part_of, ...). Returns nodes, edges, and dangling links. Filter by project or type.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | — | only edges touching this project/resource slug |
| type | string | — | only edges touching a node of this type |
No output schema declared.
No examples provided.
hub_kanban ~59
The board as data: open tasks split into queued (unassigned) and in-progress (assigned), plus done-in-the-last-day and recent journal — the same view the read-only web kanban renders. Each task carries blocked and overdue flags.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
hub_release ~51
Release a soft-lock. Pass id, or project+area+agent.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | — | — |
| area | string | — | — |
| id | string | — | — |
| project | string | — | — |
No output schema declared.
No examples provided.
hub_report ~56
Append a session report to the shared journal: what was done / broken / blocked.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | yes | — |
| kind | string | — | default: note |
| project | string | yes | — |
| text | string | yes | — |
No output schema declared.
No examples provided.
hub_resource_get ~27
One resource card plus its inbound and outbound typed relationships.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | — |
No output schema declared.
No examples provided.
hub_resource_list ~37
List resource cards (hosts, vms, services, endpoints, providers). Optionally filter by type.
| Name | Type | Req | Description |
|---|---|---|---|
| type | string | — | — |
No output schema declared.
No examples provided.
hub_resource_set ~219
Create or update a resource — an infrastructure/topology entity: host, vm, service, endpoint, or provider. Structured attributes (type, address, os, provider, status) and typed relationships go in fields, NOT prose. Use this instead of describing infra inside a card digest.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | — | ip / hostname / url, optional |
| by | string | — | who is writing |
| digest | string | — | one-line description (keep prose minimal) |
| edges | object | — | typed relationships, merged with existing: {"runs_on":["hubd"],"depends_on":["postgres"]}. Values are target slugs. |
| os | string | — | — |
| provider | string | — | libvirt | cloudflare | bare-metal | ... |
| slug | string | yes | resource id, e.g. "myvm" or "board.hubd.net" |
| status | string | — | live | down | planned | retired |
| type | string | — | host | vm | service | endpoint | provider | ... (open vocabulary) |
No output schema declared.
No examples provided.
hub_search ~56
Full-text search across every project card and the entire journal, archived months included. Returns each matching line with its location. Use to find where something was discussed or decided.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | plain-text substring, case-insensitive |
No output schema declared.
No examples provided.
hub_status ~75
Snapshot of every project at once: the latest digest of each, when it was last synced, and its open-task count, plus the most recent shared-journal entries. Best for orienting at the start of a session. For a deadline-sorted to-do list use hub_brief; for one project in depth use hub_get.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
hub_sync ~110
Sync a project folder into the hub. Collects git facts automatically; pass digest (your own summary of state/next steps) and the card is rewritten.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | — | Who is syncing (e.g. claude-cowork, cursor, executor) |
| digest | string | — | Agent-written summary: status, recent work, next steps, blockers |
| name | string | — | Project name (default: folder name) |
| path | string | yes | Absolute path to the project folder |
No output schema declared.
No examples provided.
hub_task_add ~132
Add a task to the shared cross-project backlog.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee | string | — | agent name or owner, optional |
| by | string | — | who adds |
| cat | string | — | task category, optional |
| deadline | string | — | YYYY-MM-DD, optional |
| depends_on | array | — | task ids this task waits on |
| importance | string | — | default normal |
| project | string | yes | — |
| resources | array | — | resource slugs this task touches (host/vm/service/...) — a structured link task → resource, not prose |
| text | string | yes | — |
No output schema declared.
No examples provided.
hub_task_list ~34
List backlog tasks. Filter by project and/or status.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | — | — |
| status | string | — | — |
No output schema declared.
No examples provided.
hub_task_update ~108
Update a task: close it (status=done), reassign, edit text/deadline/cat.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee | string | — | — |
| by | string | — | — |
| cat | string | — | — |
| deadline | string | — | — |
| depends_on | array | — | task ids this task waits on |
| id | integer | yes | — |
| resources | array | — | resource slugs this task touches |
| status | string | — | — |
| text | string | — | — |
No output schema declared.
No examples provided.