io.github.awesomemotive/pushengage-mcp
PushEngage
Send push notifications, build audiences, and view campaign analytics from PushEngage.
alive probed 2026-10-19
27tools
≈ 11ktokens, estimate
≈ 5.4 %of Claude's 200k window
7.5×the median server
351 msto initialize
21 msto list tools
- Run it
- npx -y @pushengage/mcp@1.0.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- pushengage 1.0.0
- Capabilities
- tools
- Instructions
- none
- Of a 1M window
- ≈ 1.1 % of a 1M context window, estimate
- Claude count
- The count_tokens endpoint refused the tool schemas: invalid x-api-key. The estimate stands in.
- Repository
- https://github.com/awesomemotive/pushengage-mcp
- Website
- https://www.pushengage.com
- Registry
- active, updated 2026-08-05 · registry entry
- Reachable
- 1 of the last 1 probe
Most expensive tools
Estimates with the o200k_base tokenizer.
| Tool | o200k estimate | Share of this server |
|---|---|---|
| pushengage_send_ab_notification | 1 725 | 16 % |
| pushengage_send_notification | 1 708 | 16 % |
| pushengage_create_audience_group | 1 006 | 9 % |
| pushengage_update_campaign_defaults | 673 | 6 % |
| pushengage_list_notifications | 624 | 6 % |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- This server is in the heaviest 10 % of the registry. Its 5 most expensive tools are 54 % of the cost. Shorter descriptions, fewer optional parameters and fewer tools cut the cost. The command npx mcpcost --url <endpoint> --tools 50 lists every tool with its cost.
- The Anthropic count_tokens endpoint refused the tool schemas (invalid x-api-key). A client that validates schemas can refuse them too.