REPORT 01M7DBNPFHBJKH18TXSJMAJQYC · checks-v2
Memory Plugin MCP server: automated checks
What HostedMCP checked on 14 Nov 2026, 15:44 UTC for @lotargo/memory_plugin. Every result links to the public source it came from, so you can check it yourself.
Not verified
83/100
6 of 11 checks ran · 0 high findings · not a security audit
- Checked
- 14 Nov 2026, 15:44 UTC
- Commit
- —
- Package
- npm · latest
- Methodology
- checks-v2
Origin
20 / 20 points- PassSource repository linked and reachable10 pts
lotargo/memory_plugin is public and reachable
github.com/lotargo/memory_plugin ↗ - PassPackage names this repository as its source5 pts
@lotargo/memory_plugin names lotargo/memory_plugin as source
npmjs.com/package/@lotargo/memory_plugin ↗ - Not checkedBuild provenance (Sigstore attestation)10 pts
No build attestation published for this release
- Pass
Practices
5 / 5 points- PassCommit or release in the last year5 pts
Last commit or release 2026-10-21
github.com/lotargo/memory_plugin ↗ - Not checkedOpenSSF Scorecard15 pts
Supply chain
10 / 10 points- PassPackage name not close to a popular package10 pts
No popular package one edit away from @lotargo/memory_plugin
- Not checkedNo critical advisory in the package or its dependencies15 pts
Tool safety
15 / 15 points- PassNo hidden instructions to the model15 pts
0 tool descriptions and the README read; no override phrases, credential paths or hidden characters
- Not checkedDestructive tools are labelled5 pts
Endpoint
not checked- Not checkedRemote endpoint answers the MCP handshake5 pts
What these checks do not cover
- The server's code is not run and its logic is not audited.
- Results describe the state 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.