Mmcp.market

Sl MCP server

by donovan-jasper·io.github.donovan-jasper/sl-mcp·v0.1.2

MCP server for Sapling (sl) version control

C65/100grade C
What users say
No reviews yet
Be the first
Safety scan
C65/100

full report

Adoption
Not measured yet

Usage numbers are collected on the next scan

Reviews

Write one

Nobody has reviewed Sl yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Sl 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-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan11 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
  • Maintenancerepository not readable: repo not found3/15
  • Maintainer identityno repository or website to verify2/10
Overall 65/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

Install Sl in Claude Code, Cursor or VS Code

Runs npx -y sl-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add sl-mcp -- npx -y sl-mcp
Add to Cursor

Sl: common questions

Is Sl MCP server safe?
With care: it is graded C, so read the findings first (65/100). Read the Sl safety report
How do I install Sl?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Sl need an API key?
No secret keys are declared. It reads 2 settings from the environment.
Is Sl maintained?
The latest release is v0.1.2.

More from donovan-jasper →