memdsl MCP server
io.github.Liyuan1992/memdsl·v0.9.2·1 starsReview-gated declarative long-term memory with bounded read-only MCP access.
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.10 · 2026-10-16 · same rubric, same numbers if you re-run it
- –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 44 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How memdsl compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 80/100
- higher than 60% of 48,243 servers
- GitHub stars
- 1
- more than 65% of 28,706 servers
Install memdsl in Claude Code, Cursor or VS Code
The registry entry has no remote endpoint or installable package.
What the publisher says
From the memdsl repository's README, as published. We do not edit it. Read it on GitHub
memdsl
<!-- mcp-name: io.github.Liyuan1992/memdsl -->
English | 中文
English
Agent memory as source code the agent reads itself.
0.9 release line with experimental Edges
Version 0.9.0 adds an opt-in memdsl.workspace.v3 first-class explicit Edge experiment. It does not rewrite the frozen 0.8 contract: legacy relations and authority remain compatible, explicit Edge proposals always require a human, and explicit supersedes is graph-only. Source remains runtime authority; review/audit is a workflow contract, not a non-bypassable grant ledger. See the Phase 6 design and risk matrix and the release-scope evidence freeze.
Stable 0.8 compatibility contract
The 0.8 contract combines the previously unpublished navigation and View work now shipped by 0.9.0; neither 0.7.0 nor 0.8.0 was released separately. Stable public contracts include the v1 compatibility/authority surfaces, Catalog v1, Trace v1, indexed query/search trace, report diagnostics, public rebuildable CompiledWorkspace / compileworkspace, memdsl.workspace.v2, exact use, the generic dialectmapping capability, ViewContext/ResolvedView, and the explicit opt-in v2 read schemas. Map v1 remains supported throughout the 0.8 line and will not be reconsidered for removal before 1.0.
The software release is 0.9.2, anchored by tag v0.9.2. It adds official MCP Registry metadata and a UV-based MCPB installer for the default-read-only memdsl-mcp server. Parser, schema, review, query, authority, and MCP tool contracts are unchanged from 0.9.1. Neither patch nor package-level release promotes the opt-in Edge surface to stable or makes automatic Edge generation authoritative.
The real-world rollout quality of quarantine/strict, dialect-candidate learning, and host-attested principal integration is still experimental and opt-in. Their safety invariants are not experimental: authorization happens before aggregation, incomplete hard-rule evaluation never becomes ALLOW, non-authoritative edges never gain authority, and repair paths remain open. CompiledWorkspace is a public rebuildable handle; its cache/index layout, compiler contract strings, and synthetic timing constants remain implementation details. Workspace-v3 first-class Edges are experimental. Automatic dialect learning, automatic Edge candidates, inferred authority, and cold-history/ incremental compilation are not shipped. Host extraction/sanitization and private schemas/policies/samples remain outside memdsl and are not release gates.
memdsl started with a retrieval failure. A memory system built on RAG failed to recall a memory it certainly had; a coding agent pointed at the same raw memory files traced it down in a few steps. Same model — the difference was the context contract. The agent knew the memory existed and could keep reading toward it; the retriever got exactly one similarity guess, and a miss looked identical to absence.
memdsl turns that difference into the product. Long-term memory lives in readable, lintable, reviewable .mem source files, and every runtime surface is built for an agent that reads memory itself:
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Grade history
- 2026-10-16downgradeA → Bscore 80
memdsl: common questions
- Is memdsl MCP server safe?
- Mostly: it is graded B (80/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 64 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 and Front-End Checklist MCP server.
- How does memdsl compare with other MCP servers?
- safety score 80/100 (higher than 60% of 48,243 servers); github stars 1 (more than 65% of 28,706 servers). Full comparison.
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
- Front-End ChecklistReview frontend code and live pages against 386 quality-gated web development rules.not reviewedWidely usedA