Model Context Protocol server for Azure Service Bus — peek, search, and inspect queues, topics, and dead-letter queues from any MCP-aware AI client.
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
YOUR_API_KEYAPI keyrequiredYour API key for the service
Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
list_namespacesList 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).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).
No input schema was published for this tool.
list_queuesList 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 queues in a namespace with active, dead-letter and scheduled message counts. Use this before peeking so you know which queues have a backlog.
No input schema was published for this tool.
list_topicsList 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.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.
No input schema was published for this tool.
list_subscriptionsList 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.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.
No input schema was published for this tool.
peek_messagesPeek 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 outwar…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 outwar…
No input schema was published for this tool.
search_messagesScan 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 repeate…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 repeate…
No input schema was published for this tool.
send_messageSend 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 subscription whose filter matches, so one send can fan out to many consumers. Needs the Azure Service Bus Data Sender role (or Data Owner), and…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 subscription whose filter matches, so one send can fan out to many consumers. Needs the Azure Service Bus Data Sender role (or Data Owner), and…
No input schema was published for this tool.
resubmit_dead_letterNo description publishedThis tool published no description. Forge does not invent one.
delete_messagesprivilegedPermanently 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 numbers. Requires --allow-destructive.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 numbers. Requires --allow-destructive.
No input schema was published for this tool.
dead_letter_messagesMove 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 they are not destroyed: they can be read with peek_messages using fromDeadLetter, and put back with resubmit_dead_letter. Use this to quaranti…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 they are not destroyed: they can be read with peek_messages using fromDeadLetter, and put back with resubmit_dead_letter. Use this to quaranti…
No input schema was published for this tool.
purge_entityDelete 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 name, as a deliberate second step. Requires --allow-destructive.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 name, as a deliberate second step. Requires --allow-destructive.
No input schema was published for this tool.
10 of 11 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Model Context Protocol server for Azure Service Bus — peek, search, and inspect queues, topics, and dead-letter queues from any MCP-aware AI client.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
The crawl stopped at the 60-package limit. The rest of the tree was never resolved.
36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)
66 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.
+54 more not listed. The counts by reason above cover all of them.
Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.