MCP.Market

Hubd MCP server

by bzdOS·io.github.bzdOS/hubd·v0.4.2·2 stars
No reviews yet

The project tracker for teams of humans and AI agents — in plain files. MCP server + CLI.

A91/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A91/100

full report

Adoption
Growing

2 stars700 downloads/wk

Reviews

Write one

Nobody has reviewed Hubd yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Hubd tools (17, 3 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • hub_brief

    Morning brief across all projects: open tasks (deadlines first), journal since N hours, stale cards, active claims.

  • hub_card_setwrite action

    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.

  • hub_claim

    Soft-lock a work area so other agents see it (e.g. area="public/index.html"). Not enforced — informational.

  • hub_get

    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.

  • hub_graph

    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.

  • hub_kanban

    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.

  • hub_release

    Release a soft-lock. Pass id, or project+area+agent.

  • hub_report

    Append a session report to the shared journal: what was done / broken / blocked.

  • hub_resource_get

    One resource card plus its inbound and outbound typed relationships.

  • hub_resource_list

    List resource cards (hosts, vms, services, endpoints, providers). Optionally filter by type.

  • hub_resource_setwrite action

    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.

  • hub_search

    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.

  • hub_status

    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.

  • hub_sync

    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.

  • hub_task_add

    Add a task to the shared cross-project backlog.

  • hub_task_list

    List backlog tasks. Filter by project and/or status.

  • hub_task_updatewrite action

    Update a task: close it (status=done), reassign, edit text/deadline/cat.

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

no findings
  • Code scan5 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 3 days ago15/15
  • Maintainer identityregistry namespace matches repository owner7/10
Overall 91/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Hubd compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
91/100
higher than 85% of 48,255 servers
Tools
17
the typical server has 7
Tools that change things
18%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
2
more than 75% of 28,688 servers
Downloads a week
700
more than 91% of 12,191 servers with a package

What its tools let an agent do: 14 read · 3 change

Install Hubd in Claude Code, Cursor or VS Code

Runs npx -y @bzdos/hubd on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add hubd -- npx -y @bzdos/hubd
Add to Cursor

What the publisher says

From the Hubd repository's README, as published. We do not edit it. Read it on GitHub

hubd

The project tracker for teams of humans and AI agents — in plain files.

A tool for agents rarely fails by crashing. It fails by answering — confidently, and wrong. A list that ended early without saying so. A count that turns out to be mostly duplicates. A task close that lands on somebody else's id. A person would stop at "wait, fifteen hundred tasks? I didn't create fifteen hundred tasks." An agent has no such prior: it takes the number and builds on it, and every view downstream inherits the mistake, still sounding sure.

hubd is built against that failure mode, and it shows in the boring parts. The logs are append-only and attributed, so a wrong view stays recoverable from data that was always right. Every truncation announces itself. Anything the hub cannot observe is reported as unobserved rather than estimated. Much of this codebase is not features — it is refusals to sound certain.

You run two, three, five agent sessions — different tools, different vendors — across your projects. Each one is brilliant, and each one has no idea the others exist. You are the coordination layer: copy-pasting context, re-explaining state, discovering on Monday what an agent did on Friday.

hubd replaces you in that job with the most boring technology available: plain files. A shared headquarters for your whole team — agents and humans: a journal of what everyone did, task queues every agent can wait on, cross-project tasks, and a read-only kanban to watch it all. All markdown and JSONL, in a folder you own.

hub serve — the board is read-only and has exactly one button (⚙ Rules, it opens AGENTS.md). Cards move because agents move them; the page just re-reads the files.

Not a runner. Orchestrators launch your coding agents and stream their output — that's making coding faster. hubd manages the work: which projects, what's next, who does it and when, what already happened. An orchestrator can run your agents; hubd runs your projects. They compose.

The Unix pair

  • hubd — the daemon: an MCP server (stdio, JSON-RPC 2.0) that agents talk to.
  • hub — the CLI: the same data for humans, no LLM required.

Like sshd and ssh. The daemon serves agents; the CLI serves you.

Quick start

Option A — start a company (copy the folder). One command drops hubd-company/ into a folder of your own:

npx degit bzdOS/hubd/hubd-company my-company   # then: cd my-company && git init

Or clone this repo and copy the folder — it doesn't have to be your repo root. You get a ready org structure: constitution (AGENTS.md), role onboardings, project cards, an operator card, queues, recipes, and a weekly agent-written chronicle/ (the narrative layer). Hiring an agent = a fresh session reads a role file. This template is NOT included in the npm package; it comes from the repo.

Option B — add the binaries to what you have:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Hubd: common questions

Is Hubd MCP server safe?
Yes, by our scan: it is graded A (91/100). Read the Hubd safety report
How do I install Hubd?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Hubd need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Hubd maintained?
The last commit was 42 days ago (2026-09-23). The latest release is v0.4.2.
How does Hubd compare with other MCP servers?
safety score 91/100 (higher than 85% of 48,255 servers); tools 17 (the typical server has 7); tools that change things 18% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.