@muqsitnawaz/notifications-mcp
BMCP server package notifications-mcp
Install
agr install @muqsitnawaz/notifications-mcp --target claudeThis artifact does not publish files for Claude.
Document
{ "name": "notifications-mcp", "version": "0.1.0", "description": "MCP server for macOS native notifications with action buttons", "main": "dist/index.js", "types": "dist/index.d.ts", "bin": { "notifications-mcp": "./dist/index.js" }, "files": [ "dist" ], "type": "module", "scripts": { "build": "tsc", "start": "node dist/index.js" }, "dependencies": { "@modelcontextprotocol/sdk": "^1.0.0" }, "devDependencies": { "@types/node": "^20.x", "typescript": "^5.3.0" }, "author": "Muqsit Nawaz dev@muqsitnawaz.com", "license": "MIT" }
Trustgrade B
- passBody integrity
Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.
- warnType matchbest-effort: server code not analyzed
Whether the artifact is really the kind of thing its metadata claims it is.
- passFreshness
How long since the source repository was last pushed to.
- passPrompt injection
Scans the artifact's own text for instructions aimed at your agent rather than at you.
- warnLicenseno SPDX license detected
Whether the source repository declares an SPDX license permissive enough to redistribute.
How the grade is calculated
Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:
- Aevery check passed
- Bone warning
- Ctwo warnings
- Dprompt injection or body integrity failed, or three warnings
- Fone of those failed, and something else is wrong
These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.
Versions
git-34e6de3001882026-08-03