# bussin-mcp

Model Context Protocol server for Azure Service Bus — peek, search, and inspect queues, topics, and dead-letter queues from any MCP-aware AI client.

- **Type:** MCP server
- **Trust:** 85/100 (A), scored on the package rubric
- **Verification:** verified (build provenance)
- **Version:** 0.1.4
- **Author:** Unknown
- **License:** BUSL-1.1
- **npm:** bussin-mcp
- **Source:** https://github.com/sgebb/bussin
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

85/100 (A), scored on the package rubric
- Publisher verified: no
- Build provenance: verified attestation
- npm trusted publishing (OIDC): yes
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 1 day

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-13T00:00:03.362Z
- **Version scanned:** 0.1.4
- **CVEs:** none found by OSV at scan time

## Tools

11 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `list_namespaces` — List the Azure Service Bus namespaces the signed-in identity can see, across all enabled subscriptions. Large tenants can hold dozens, so pass nameFilter whenev
- `list_queues` — 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.
- `list_topics` — 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
- `list_subscriptions` — 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.
- `peek_messages` — 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
- `search_messages` — 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
- `send_message` — Send a message to a queue or topic. This is a real send against the live namespace: consumers will pick it up. Sending to a topic delivers a copy to every subsc
- `resubmit_dead_letter`
- `delete_messages` — Permanently delete messages by sequence number from a queue or its dead-letter queue. This cannot be undone. Peek or search first to confirm the sequence number
- `dead_letter_messages` — Move active messages to the dead-letter queue by sequence number, with a reason. The messages stop being delivered to consumers and will not be retried, but the
- `purge_entity` — Delete EVERY message from a queue, a subscription, or their dead-letter queue. This is irreversible and unbounded. The confirm argument must be the exact entity

## Install

**Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"bussin\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"bussin-mcp\"\n      ],\n      \"env\": {\n        \"YOUR_API_KEY\": \"<YOUR_YOUR_API_KEY>\"\n      }\n    }\n  }\n}"
```
**Credentials it will ask for** (names only — Forge never holds a value):
- `YOUR_API_KEY` — Your API Key (required)
Placeholders only. Forge never holds, brokers, or transmits a credential value — replace each <YOUR_NAME> in your own config file. Do not send a value back to Forge; no Forge endpoint accepts one.
- This entry needs 1 credential (1 required). The generated config carries placeholders, so it will fail in the editor rather than at runtime if they are left unset.

## Blast radius

Extensive blast radius — deletes data; holds an api key.
- Floor 52, ceiling 52 (tier: extensive)
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/bussin-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/bussin-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/bussin-mcp
- HTML page: https://forgeregistry.com/registry/bussin-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.