memdsl MCP server
Review-gated declarative long-term memory with bounded read-only MCP access.
A88/100grade A
Adoption
New
1 stars
Reviews
Write oneNobody has reviewed memdsl yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
memdsl tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-20 · same rubric, same numbers if you re-run it
no findings
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 18 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Install directly
The registry entry has no remote endpoint or installable package.
memdsl: common questions
- Is memdsl MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the memdsl safety report
- Does memdsl need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is memdsl maintained?
- The last commit was 18 days ago (2026-09-02). The latest release is v0.9.2.
- What can I use instead of memdsl?
- Servers from other publishers that do the same job: Nautilus Compass Memory MCP server.
Alternatives to memdsl
Same job from other publishers: the closest match first, then the best rated.
- Nautilus Compass MemoryLocal-first long-term memory for AI agents, with byte-recomputable signed verification receipts.not reviewedEstablishedB