MCP Observatory
github analyzed beb9dd3

IgorGanapolsky/mcp-memory-gateway

github

Pre-action gates that block AI agents from repeating known mistakes.

maintainer
IgorGanapolsky
license
—
first seen
2026-06-03
last seen
2026-06-03
releases · 30d
0
short id
risk71/100 · heuristic grade
D high
  • capability exposureinferred+35
  • recent driftinferred+20
  • tool safetyinferred+24
  • trust mitigatorsmixed−8

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 7m ago · see ecosystem CVEs →

risk trajectory1 movements
  • D · 63 → D · 71
capability exposuregrade factor +35
Inferred surface — each links to servers holding it:
vulnerabilities0 CVEs

no known CVEs for this server.

tool safety3 findings · grade factor +24
  1. highdangerous code

    env-secret-flows-to-network-js: A process environment value (often a secret/token) flows into a network call — possible credential exfiltration. (/tmp/obs-code-Cbto3t/IgorGanapolsk

  2. highdangerous code

    suspicious bundled script in 1 file(s)

  3. highhidden prompt content

    1 file(s) with hidden prompt content: IgorGanapolsky-ThumbGate-beb9dd3/skills/verify-pricing-surfaces/SKILL.md (skill-exfil): "secret→sink: for event in "pricing_cta_click" "Check…

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

analyzed commit beb9dd3 · analyzer v17 · 2d ago

skills & prompt files 45

danger signals1

other grade factorsevidence elsewhere
embed badgereadme-ready
live risk-grade badge preview [![MCP Observatory risk grade](https://mcpobservatory.com/servers/github:IgorGanapolsky/mcp-memory-gateway/badge.svg)](https://mcpobservatory.com/servers/github:IgorGanapolsky/mcp-memory-gateway/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 IgorGanapolsky.