MsgMesh MCP Server — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to MsgMesh event-stream watching and governance tools: Do admin governance scopes remain separate from producer and consumer data-plane keys?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Event-bus messaging for agents with topics, schemas, live event watching and webhooks.

What we know

Discovery evidence identifies an AI-agent event bus MCP for topic/schema/webhook management and long-polling live topic events.

Maintenance / activity evidence

@msgmesh/mcp-server 0.1.10 published 2026-10-05T09:28:43.915Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: low.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Likely event/topic/webhook read-write authority; exact scope unresolved. Reported action classes: Manage topics/schemas/webhooks (based on discovery description). Complete write authority is not verified.
Authentication not yet verified.
Sensitive access: Event payloads, Webhook destinations

Messaging infrastructure is potentially high-impact; insufficient first-party evidence for production claims.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do admin governance scopes remain separate from producer and consumer data-plane keys?

The bounded review of the publisher's documented MsgMesh event-stream watching and governance tools and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Messaging infrastructure is potentially high-impact; insufficient first-party evidence for production claims.
Likely event/topic/webhook read-write authority; exact scope unresolved.
Event payloads may contain sensitive application data; storage/retention unknown.
Reviewed write actions: Manage topics/schemas/webhooks (based on discovery description)
Sensitive access: Event payloads, Webhook destinations
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
official docs/repository
authentication
retention
delivery semantics
complete write actions
First-party docs/package content was not successfully retrieved in this pass.
Exact authentication, retention, delivery guarantees, replay semantics and mutation surface remain unresolved.

Original activity observations

@msgmesh/mcp-server 0.1.10 published 2026-10-05T09:28:43.915Z

Technical identity

npm/@msgmesh/mcp-server

Exact implementation source: https://www.npmjs.com/package/@msgmesh/mcp-server ↗
Reviewed resource type: Gateway
Package identity: npm:@msgmesh/mcp-server

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry ↗
@msgmesh/mcp-server
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.

Setup · Watchlist

Gateway setup

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
MQ_API_KEY required; placeholders rejected. Hosted messaging gateway; delivery/publish are writes.
publisher install or stdio launch · Publisher instructions
npx -y @msgmesh/mcp-server
Configure / authenticate
MCP100 setup guide
Use stdio npx @msgmesh/mcp-server with real MQ_API_KEY issued in MsgMesh dashboard. Placeholder-like values cause startup failure. Send/publish operations modify messaging state.
claude desktop or cursor mcpServers json · MCP100 composed guide
{ "mcpServers": { "msgmesh": { "args": [ "-y", "@msgmesh/mcp-server" ], "command": "npx", "env": { "MQ_API_KEY": "REPLACE_WITH_REAL_KEY" } } } }
Check connection
Suggested check
Configure MQ_API_KEY and inspect tools/read-only subscription metadata. Do not publish event messages.
Remove / uninstall / revoke
MCP100 setup guide
If you added this integration to Claude Code under the registration name `msgmesh`, run `claude mcp remove msgmesh` to unregister that client entry. In Claude Desktop, Cursor, VS Code or another host, delete/disable the corresponding named MCP registration in that host's settings and restart/reconnect. If you installed an npm package globally or operate a separate HTTP server, uninstall/stop it with its original deployment method. This does not delete user data or revoke service credentials.
MCP client unregister, stopping hosted processes, package uninstall, OAuth disconnect and token revocation are distinct actions.
A claude mcp remove command is only valid for Claude Code when the local registration actually has that name. Other MCP hosts require their own UI/config cleanup.
Separate provider credential revocation · publisher documented: MsgMesh publisher exposes `list_keys` and `delete_key` MCP tools for key management (`create_key` also available). `delete_key` mutates credentials; identify target key before invoking. This is not the same as deleting MCP client registration.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove msgmesh

Official Documentation & Sources

What it does

Discovery evidence identifies an AI-agent event bus MCP for topic/schema/webhook management and long-polling live topic events.

Capability: Communication
Resource type: Gateway
Best fit: Event-bus messaging for agents with topics, schemas, live event watching and webhooks.

Representative uses

Watch topic events
Manage topics
Manage schemas
Manage webhooks

Limitations

First-party docs/package content was not successfully retrieved in this pass.
Exact authentication, retention, delivery guarantees, replay semantics and mutation surface remain unresolved.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Not documented in the reviewed sources
Permissions: Likely event/topic/webhook read-write authority; exact scope unresolved.
Data handling: Event payloads may contain sensitive application data; storage/retention unknown.
Cost: unknown
Risk and cautions: Messaging infrastructure is potentially high-impact; insufficient first-party evidence for production claims.

Access scope and cautions

Write actions: Not verified Manage topics/schemas/webhooks (based on discovery description)
Sensitive access: Event payloads Webhook destinations
Risk level: high

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The available discovery description lists: Watch topic events; Manage topics; Manage schemas; Manage webhooks. These descriptions do not establish a fully verified tool inventory.

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. The partial inventory lists: Manage topics/schemas/webhooks (based on discovery description). Discovery-described permission context (not independently verified): Likely event/topic/webhook read-write authority; exact scope unresolved.

What data-handling boundary should I consider?

Event payloads may contain sensitive application data; storage/retention unknown. Recorded sensitive-access context: Event payloads; Webhook destinations.

What limitations and risks should I check before use?

Messaging infrastructure is potentially high-impact; insufficient first-party evidence for production claims. First-party docs/package content was not successfully retrieved in this pass. Exact authentication, retention, delivery guarantees, replay semantics and mutation surface remain unresolved. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.