slivingdoc MCP server
Share ordinary text files between concurrent agents without silently overwriting edits.
A92/100grade A
Adoption
Growing
2 stars172 downloads/wk
Reviews
Write oneNobody has reviewed slivingdoc yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
slivingdoc tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.5 · 2026-09-19 · same rubric, same numbers if you re-run it
no findings
- Code scan8 source files scanned25/25
- –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 0 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Install directly
Runs npx -y slivingdoc on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add slivingdoc -- npx -y slivingdoc
slivingdoc: common questions
- Is slivingdoc MCP server safe?
- Yes, by our scan: it is graded A (92/100). Read the slivingdoc safety report
- How do I install slivingdoc?
- It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
- Does slivingdoc need an API key?
- No secret keys are declared. It reads 5 settings from the environment.
- Is slivingdoc maintained?
- The last commit was 2 days ago (2026-09-19). The latest release is v0.1.19.