io.github.sgebb/bussin-mcp
NPM · BUSSIN-MCP
MCP server for Azure Service Bus. Peek, search and replay dead-letter messages from any MCP client.
Available components
Last scanned (3 hours ago)
Scores higher than 95% of npm servers
Category Cloud Infrastructure
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 Security98
- 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
- 42 of 136 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency84
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to sgebb/bussin). View diagnostics → Pass
- License check failed: the license (BUSL-1.1) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 872 tokens (~145/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 1 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 −16
- Malware scan: pass → unverified ▼ security
- Schema quality: 119 → 145 ▼ functional
- Package version: 0.1.2 → 0.2.0 functional
- 30 Oct 26 +2
- CVE-2026-109461 no longer affects this package ▲ security
- Known CVEs: fail → pass ▲ security
- 26 Oct 26 +1
- Stability: 0.97 → pass security
- 24 Oct 26 −3
- CVE-2026-109461 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- Stability: pass → 0.93 functional
- 18 Oct 26 0
- Stability: 0.97 → pass security
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
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/bussin-mcp@0.2.0
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 | sgebb/bussin |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/sgebb/bussin/.github/workflows/mcp-server-publish.yml@refs/tags/mcp-v0.2.0 |
| Rekor log index | 3614513634 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:4aaaa872b18c71c1d22ffb172057595fbe869fffcd58d12e3b69855e3f9da1a566d6f2279dd4f782e623368938b23788d446463dda88841fd12bf7c3b |
Background: How many MCP packages publish verified provenance →
Dependencies 136 packages
| Packages resolved | 136 |
|---|---|
| Stale | 42 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
list_namespaces List Service Bus namespaces ~125
List the Azure Service Bus namespaces the signed-in identity can see, across all enabled subscriptions. Large tenants can hold dozens, so pass nameFilter whenever you already know roughly what you are looking for. Requires Entra ID sign-in (not available with a connection string).
| Name | Type | Req | Description |
|---|---|---|---|
| nameFilter | string | – | Case-insensitive substring, or a glob when it contains "*". Examples: "payments" matches any name containing it; "billing-*" matches names starting with it; "*-prod" matches names ending with it. |
| subscriptionId | string | – | Limit to one subscription. |
No output schema declared.
No examples provided.
list_queues List queues ~55
List queues in a namespace with active, dead-letter and scheduled message counts. Use this before peeking so you know which queues have a backlog.
| Name | Type | Req | Description |
|---|---|---|---|
| namespace | string | – | Service Bus namespace name. Defaults to the server namespace. |
No output schema declared.
No examples provided.
list_subscriptions List topic subscriptions ~64
List the subscriptions under a topic, with active and dead-letter counts. Use this to pick the subscription to pass to peek_messages or search_messages.
| Name | Type | Req | Description |
|---|---|---|---|
| namespace | string | – | Service Bus namespace name. Defaults to the server namespace. |
| topic | string | yes | Topic name. |
No output schema declared.
No examples provided.
list_topics List topics ~63
List topics in a namespace with their message counts. Messages sit on a topic's subscriptions rather than the topic itself, so follow up with list_subscriptions to find where a backlog actually is.
| Name | Type | Req | Description |
|---|---|---|---|
| namespace | string | – | Service Bus namespace name. Defaults to the server namespace. |
No output schema declared.
No examples provided.
peek_messages Peek messages ~223
Peek messages from a queue, or from a topic subscription when topic and subscription are given. Peek is non-destructive: it does not lock, consume, or increment delivery count. Set fromDeadLetter to read the dead-letter queue instead of the main entity. This reads from the head of the entity outwards, so it is the right tool for "what is in this queue"; to find particular messages in a backlog, use search_messages instead of paging through peek. Needs the Azure Service Bus Data Receiver role (or Data Owner).
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | How many messages to return. |
| fromDeadLetter | boolean | – | Read the dead-letter queue. |
| fromSequence | integer | – | Start at this sequence number. 0 starts from the oldest available message. |
| namespace | string | – | Service Bus namespace name. Defaults to the server namespace. |
| queue | string | – | Queue name. Omit when using topic + subscription. |
| subscription | string | – | Subscription name, requires topic. |
| topic | string | – | Topic name, when reading a subscription. |
No output schema declared.
No examples provided.
search_messages Search messages ~255
Scan a queue or subscription for messages matching a body substring, message id, or subject. Non-destructive. Scanning is bounded by maxMessages and by a server-side timeout, so on a deep backlog prefer a narrow filter. Returns matching messages with their sequence numbers. Prefer this over repeated peek_messages calls whenever you know something about the messages you want. The sequence numbers it returns are what delete_messages, resubmit_dead_letter and dead_letter_messages take as input. Needs the Data Receiver role (or Data Owner).
| Name | Type | Req | Description |
|---|---|---|---|
| bodyFilter | string | – | Case-insensitive substring to find in the body. |
| fromDeadLetter | boolean | – | Search the dead-letter queue. |
| maxMatches | integer | – | Stop after this many matches. |
| maxMessages | integer | – | Cap on messages scanned. |
| messageIdFilter | string | – | Exact message id to match. |
| namespace | string | – | Service Bus namespace name. Defaults to the server namespace. |
| queue | string | – | Queue name. Omit when using topic + subscription. |
| subjectFilter | string | – | Subject (label) to match. |
| subscription | string | – | Subscription name, requires topic. |
| topic | string | – | Topic name, when searching a subscription. |
No output schema declared.
No examples provided.
How do I install the io.github.sgebb/bussin-mcp server?
io.github.sgebb/bussin-mcp runs locally as an npm package, launched with npx -y bussin-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 · bussin-mcp
claude mcp add sgebb-bussin-mcp -- npx -y bussin-mcp
What is the io.github.sgebb/bussin-mcp server?
io.github.sgebb/bussin-mcp is listed in the public MCP registry as io.github.sgebb/bussin-mcp. MCP server for Azure Service Bus. Peek, search and replay dead-letter messages from any MCP client. This page covers its npm package (bussin-mcp).
Is the io.github.sgebb/bussin-mcp server safe to use?
io.github.sgebb/bussin-mcp scores 92 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 io.github.sgebb/bussin-mcp server expose?
io.github.sgebb/bussin-mcp exposes 6 tools: list_namespaces, list_queues, list_topics, list_subscriptions, peek_messages, search_messages. Their descriptions and schemas cost roughly 785 tokens of context every time the server is loaded.
Is the io.github.sgebb/bussin-mcp server still maintained?
io.github.sgebb/bussin-mcp 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 io.github.sgebb/bussin-mcp server under?
io.github.sgebb/bussin-mcp declares the BUSL-1.1 licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.