Multi-backend notification system (audio, Telegram, SMS, phone)
- capability exposureinferred+22
- trust mitigatorsmixed−3
inferredmixed
The A–E grade is our heuristic synthesis — a "review this" prompt, not a verdict. Each factor is tagged by what backs it: attested (a verifiable record), reported (a third party's claim), or inferred (our own heuristic, e.g. permissions). See methodology.
graded 14m ago · see ecosystem CVEs →
No known CVEs for this server.
No tool-safety findings — heuristic detectors run on the compute-risk cadence; a finding appears when a tool trips a rule.
analyzed commit 66705ba · analyzer v17 · 2d ago
skills & prompt files 1
danger signals2
- suspicious endpointapi.telegram.orgywatanabe1989-scitex-notification-66705ba/src/scitex_notification/_backends/_telegram.py:27
TELEGRAM_API_BASE = "https://api.telegram.org/bot{token}" - suspicious endpointapi.telegram.orgywatanabe1989-scitex-notification-66705ba/src/scitex_notification/telegram_channel.py:57
TELEGRAM_API_BASE = "https://api.telegram.org/bot{token}"
[](https://mcpobservatory.com/servers/github:ywatanabe1989/scitex-notification/security) Heuristic, inferred signals — false positives (legitimately powerful tools, forks, language ports) are expected. Treat each as "review this", not a verdict. See the ecosystem-wide picture on the security hub, or the fleet security of ywatanabe1989.