# onesignal-mcp

Query the OneSignal API (free tier; use a current v2 Organization API key for ONESIGNAL_USER_KEY and the app REST API key for ONESIGNAL_APP_KEY, Basic auth).

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.0.2
- **Author:** Unknown
- **License:** MIT
- **npm:** onesignal-mcp
- **Source:** https://github.com/mrfentmen/premium-mcps
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

60/100 (B), scored on the package rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 2 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-10-03T17:14:16.993Z
- **Version scanned:** 1.0.2
- **CVEs:** none found by OSV at scan time

## Tools

6 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `list_apps` — OneSignal apps the key can send to.
- `get_app` — One app by id, with platform and player count.
- `list_notifications` — Recent notifications for an app.
- `push_sdk_popularity` — Which OneSignal SDK people actually install: for each of the Node, React Native and Cordova packages, the latest version, how many versions exist, and last week
- `sdk_release_timeline` — The release train of one OneSignal SDK: first and latest publish dates, days since the last release, how many versions exist, the median gap between them, every
- `platform_status` — OneSignal's own reliability record: the headline status, every product area (push, email, SMS, in-app messages, integrations, analytics) with its current state,

## Install

**Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for.
**Cautions** (coverage gaps and advisories — never blocking)
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"onesignal\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"onesignal-mcp\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on your machine; read-only tool surface.
- Floor 13, ceiling 31 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- 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/onesignal-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/onesignal-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/onesignal-mcp
- HTML page: https://forgeregistry.com/registry/onesignal-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.