Report 01M786V21XDNRH1VRQ4W9TSA04 · static-2
Memory Engine MCP MCP server: automated checks
What HostedMCP checked on 12 Nov 2026, 15:43 UTC. Every result links to the public source it came from, so you can check it yourself.
Passed HostedMCP checks
100/100
5 of 8 checks ran · 0 high findings · not a security audit
- Checked
- 12 Nov 2026, 15:43 UTC
- Commit
- —
- Package
- ghcr.io/simoneb79/memory-engine-mcp:1.5.3 · latest
- Methodology
- static-2
Origin
25 / 25 points- PassSource repository linked and reachable15 pts
- PassOpen source license (OSI)10 pts
Practices
10 / 10 points- PassCommit or release in the last year10 pts
Supply chain
not checked- Not checkedPackage name not close to a popular package15 pts
- Not checkedNo critical advisory in the package or its dependencies10 pts
Tool safety
30 / 30 points- PassDestructive tools are labelled10 pts
- PassNo hidden instructions to the model20 pts
Endpoint
not checked- Not checkedRemote endpoint uses HTTPS10 pts
Starting the package
Not a stdio serverWe installed ghcr.io/simoneb79/memory-engine-mcp:1.5.3 1.5.3 in an isolated container that could reach only the package registry, started it with no network and no credentials, and asked for its tools on 16 Nov 2026.
It looks like an HTTP server rather than a stdio MCP server.
What these checks do not cover
- Tools are listed but never called, and the server's logic is not audited.
- Results describe the repository and package on the date above; a later release can differ.
- A pass is not a guarantee of safety. Give every server the narrowest token or role it needs.