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.

GhostBus

NPM · GHOSTBUS

Agent-to-agent message bus and shared workspace, exposed as an MCP server.

Available components

71 Trust /100

Last scanned (6 hours ago)

Scores higher than 40% of npm servers

Category Communication

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 & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to littlestjames82-sys/ghostbus). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability55
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 1219 tokens (~42/item across 29 items; 29 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
  • Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "bus_send" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 29 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.

  • 4 Nov 26 71

    First indexed and scored.

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/ghostbus@0.5.11

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo littlestjames82-sys/ghostbus
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/littlestjames82-sys/ghostbus/.github/workflows/publish-npm.yml@refs/tags/v0.5.11
Rekor log index 3686801170
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:e0bae61a33ffa64a922c10cde4f8507053ac1e9c19ef55527ec76603a025ead498d06d5620393ac403e33d5edf377b2330019f2392cde9daf1ef1f06b

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 · 29 exposed · ~1,219 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
bus_agents ~22

List registered agents with roles, capabilities, and last-seen times.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

bus_approve_task ~42

Approve a task that is waiting in needs-approval, releasing it to the queue.

NameTypeReqDescription
agentstringyes–
idnumberyes–

No output schema declared.

No examples provided.

bus_cancel_task ~28

Cancel an open task.

NameTypeReqDescription
agentstringyes–
idnumberyes–

No output schema declared.

No examples provided.

bus_channels ~15

List message channels with message counts.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

bus_claim_task ~41

Claim a queued task exclusively (15-minute lease). Fails if another agent holds it.

NameTypeReqDescription
agentstringyes–
idnumberyes–

No output schema declared.

No examples provided.

bus_comment_task ~53

Comment on a task (discussion lives on the task, next to its history).

NameTypeReqDescription
agentstringyes–
bodystringyes–
idnumberyes–
tokenstring––

No output schema declared.

No examples provided.

bus_complete_task ~44

Complete a task you claimed, with a result summary for the sender.

NameTypeReqDescription
agentstringyes–
idnumberyes–
resultstring––

No output schema declared.

No examples provided.

bus_create_task ~87

Create a handoff task. Optionally assign it, mark urgent, or gate it behind human/agent approval (needsApproval).

NameTypeReqDescription
agentstringyes–
assigneestring––
blockedByarray––
bodystring––
needsApprovalboolean––
prioritystring––
titlestringyes–

No output schema declared.

No examples provided.

bus_events ~27

Read the provenance event log (who did what, when).

NameTypeReqDescription
limitnumber––

No output schema declared.

No examples provided.

bus_heartbeat ~40

Heartbeat: mark this agent present and get the live agent list with online status.

NameTypeReqDescription
agentstringyes–
tokenstring––

No output schema declared.

No examples provided.

bus_inbox ~62

Read messages visible to this agent (direct, broadcast, and its own). Marks them read unless markRead=false.

NameTypeReqDescription
agentstringyes–
limitnumber––
markReadboolean––
unreadOnlyboolean––

No output schema declared.

No examples provided.

bus_list_tasks ~37

List tasks, optionally filtered by status or assignee/claimer.

NameTypeReqDescription
assigneestring––
statusstring––

No output schema declared.

No examples provided.

bus_register ~84

Register (or rejoin) this agent on the bus with a role and capabilities. First registration returns a per-agent token ONCE — store it; on a token-enforced bus it must be passed as `token` on later calls.

NameTypeReqDescription
agentstringyes–
capabilitiesarray––
rolestring––
tokenstring––

No output schema declared.

No examples provided.

bus_rotate_token ~51

Rotate this agent's token (requires the current token on an enforced bus). The old token stops working; the new one is shown once.

NameTypeReqDescription
agentstringyes–
tokenstring––

No output schema declared.

No examples provided.

bus_search ~33

Search messages, tasks, and shared files by text.

NameTypeReqDescription
limitnumber––
querystringyes–

No output schema declared.

No examples provided.

bus_send ~72

Send a message to one agent (to = its name) or broadcast (to = "*"). Set threadId to reply in a thread.

NameTypeReqDescription
agentstringyes–
bodystringyes–
channelstring––
threadIdnumber––
tostring––

No output schema declared.

No examples provided.

bus_status ~20

Workspace status: agents, message/task/file counts, version.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

bus_sync ~57

Catch-up sync: all provenance events after a sequence number (an agent that was offline replays exactly what it missed). Returns headSeq to store as the next cursor.

NameTypeReqDescription
limitnumber––
sinceSeqnumber––

No output schema declared.

No examples provided.

bus_thread ~26

Read a message thread (root message + its replies).

NameTypeReqDescription
idnumberyes–

No output schema declared.

No examples provided.

workspace_board ~23

Render the shared board: agents, open tasks, files, recent activity.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

workspace_delete_file ~36

Delete a shared workspace file.

NameTypeReqDescription
agentstringyes–
pathstringyes–
tokenstring––

No output schema declared.

No examples provided.

workspace_file_history ~32

Version history of a shared file (current version + up to 10 previous).

NameTypeReqDescription
pathstringyes–

No output schema declared.

No examples provided.

workspace_get_capsule ~75

Read a project capsule (structured shared memory: State / Decisions (locked) / Next / Session log). Creates it from the template when create=true.

NameTypeReqDescription
agentstring––
createboolean––
slugstringyes–
titlestring––
tokenstring––

No output schema declared.

No examples provided.

workspace_get_context ~15

Read the shared context object.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

workspace_get_file ~22

Read a shared workspace file.

NameTypeReqDescription
pathstringyes–

No output schema declared.

No examples provided.

workspace_list_files ~19

List shared workspace files with size and last writer.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

workspace_put_context ~36

Publish the shared context object (project state every agent reads first).

NameTypeReqDescription
agentstringyes–
contextobjectyes–

No output schema declared.

No examples provided.

workspace_put_file ~50

Write a shared workspace file (capsule, note, deliverable). Path may not contain "..".

NameTypeReqDescription
agentstringyes–
pathstringyes–
textstringyes–

No output schema declared.

No examples provided.

workspace_update_capsule ~70

Update one capsule section (State, Decisions (locked), Next) or append a Session log entry. Other sections are preserved.

NameTypeReqDescription
agentstringyes–
sectionstringyes–
slugstringyes–
textstringyes–
tokenstring––

No output schema declared.

No examples provided.

Install

How do I install the GhostBus MCP server?

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

npm · ghostbus

# add to Claude Code
claude mcp add littlestjames82-sys-ghostbus -- npx -y ghostbus
Common questions

What is the GhostBus MCP server?

GhostBus is an MCP server listed in the public MCP registry as io.github.littlestjames82-sys/ghostbus. Agent-to-agent message bus and shared workspace, exposed as an MCP server. This page covers its npm package (ghostbus).

Is the GhostBus MCP server safe to use?

GhostBus scores 71 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. Its build provenance is signed and verified. 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 GhostBus MCP server expose?

GhostBus exposes 29 tools: bus_status, bus_register, bus_rotate_token, bus_heartbeat, bus_search, and 24 more. Their descriptions and schemas cost roughly 1,219 tokens of context every time the server is loaded.

Is the GhostBus MCP server still maintained?

GhostBus 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 GhostBus MCP server under?

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