Pusher Channels
NPM · @CRASHBYTES/PUSHER-MCP-SERVER · SCANNED AUG 4
Trigger events, query channels, and manage realtime messaging on Pusher Channels.
Available components
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 →
Supply Chain Security88
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (116 of 117), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (116 of 117), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 33 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 465 tokens (~66/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @crashbytes/pusher-mcp-server
claude mcp add crashbytes-pusher-mcp-server -- npx -y @crashbytes/pusher-mcp-server
codex mcp add crashbytes-pusher-mcp-server -- npx -y @crashbytes/pusher-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"crashbytes-pusher-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"@crashbytes/pusher-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add crashbytes-pusher-mcp-server --command npx --arg -y --arg @crashbytes/pusher-mcp-server
mcp_servers:
crashbytes-pusher-mcp-server:
command: "npx"
args: ["-y", "@crashbytes/pusher-mcp-server"] {
"mcpServers": {
"crashbytes-pusher-mcp-server": {
"command": "npx",
"args": [
"-y",
"@crashbytes/pusher-mcp-server"
]
}
}
} 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.
- 3 Aug 26 +4
- Stability: unverified → 0.27 ▲ functional
- 2 Aug 26 +45
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → excellent ▲ functional
- Licence: MIT functional
- 1 Aug 26 −7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 46
First indexed and scored.
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 4 Aug 2026 · Analysed npm/@crashbytes/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 116 packages
116 packages in the resolved dependency tree · 113 deprecated · 38 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
authorize_channel ~85
Generate an authorization token for a private or presence channel. Useful when building auth endpoints for Pusher client connections.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | Private or presence channel name (must start with 'private-' or 'presence-') |
| presenceData | object | — | Required for presence channels — identifies the connecting user |
| socketId | string | yes | The socket ID from the client connection |
No output schema declared.
No examples provided.
get_channel_info ~53
Get detailed information about a specific Pusher channel, including whether it is occupied and optional subscription/user counts.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | The channel name to query |
| info | array | — | Additional attributes to request |
No output schema declared.
No examples provided.
get_presence_users ~47
List all users currently connected to a presence channel. Only works with channels that start with 'presence-'.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | Presence channel name (must start with 'presence-') |
No output schema declared.
No examples provided.
list_channels ~78
List all active channels in your Pusher app. Optionally filter by prefix (e.g. 'presence-' or 'private-') and request subscription or user counts.
| Name | Type | Req | Description |
|---|---|---|---|
| info | array | — | Additional attributes to include for each channel |
| prefix | string | — | Filter channels by prefix (e.g. 'presence-', 'private-chat-') |
No output schema declared.
No examples provided.
terminate_user_connections ~47
Disconnect all connections for a specific user. Useful for moderation or security — forces a user offline across all channels.
| Name | Type | Req | Description |
|---|---|---|---|
| userId | string | yes | The user ID to disconnect from all channels |
No output schema declared.
No examples provided.
trigger_batch_events ~51
Send up to 10 events in a single API call. More efficient than triggering events individually when you need to notify multiple channels.
| Name | Type | Req | Description |
|---|---|---|---|
| events | array | yes | Array of events to send (max 10) |
No output schema declared.
No examples provided.
trigger_event ~104
Send an event to one or more Pusher channels. Use this to push realtime messages to connected clients.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | — | yes | Channel name or array of channel names (max 100) |
| data | — | yes | Event payload — string or JSON object (max 10KB) |
| event | string | yes | Event name to trigger (e.g. 'new-message', 'update') |
| socketId | string | — | Optional socket ID to exclude from receiving the event (prevents echo) |
No output schema declared.
No examples provided.