MCP Observatory
github not analyzable

Timwal78/SqueezeOS

github

SqueezeOS - Institutional Squeeze Detection Engine | ScriptMasterLabs

maintainer
Timwal78
license
MIT
first seen
2026-06-11
last seen
2026-06-17
releases · 30d
1
short id
risk 46/100 · heuristic grade
C elevated

Source not yet analyzed — this grade rests on attested signals (CVEs, supply-chain) only. It is a floor: reading the code could raise it, not lower it.

  • capability exposureinferred+35
  • tool safetyinferred+14
  • 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 15m ago · see ecosystem CVEs →

risk trajectory 1 movements
  • C · 43 → C · 46
capability exposure grade factor +35
Inferred surface — each links to servers holding it:
vulnerabilities 0 CVEs

No known CVEs for this server.

tool safety 3 findings · grade factor +14
  1. highdangerous code

    env-secret-flows-to-network-py: An environment value (often a secret/token) flows into a network call — possible credential exfiltration. (/tmp/obs-code-qzOHWC/Timwal78-SqueezeOS-9

  2. hightoxic flow (lethal trifecta)

    lethal trifecta reachable across this server's tools: private-data access + untrusted-content ingestion + network exfil

  3. lowexfiltration combo

    sensitive read and network capabilities split across this server's tools

skills & danger signals github-tarball
prompt-surface shipped agent-instruction files + hidden-content / dangerous-code findings — quoted from the analyzed source

analyzed analyzer v18 · 1h ago

skills & prompt files 15

embed badge readme-ready
live risk-grade badge preview [![MCP Observatory risk grade](https://mcpobservatory.com/servers/github:Timwal78/SqueezeOS/badge.svg)](https://mcpobservatory.com/servers/github:Timwal78/SqueezeOS/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 Timwal78.