io.github.donovan-jasper/sl-mcp

MCPcommunity
v0.1.2io.github.donovan-jasperUnknownUpdated 6mo agonpmGitHub

MCP server for Sapling (sl) version control

MCP server for Sapling (). Gives LLMs structured access to Sapling repos with built-in safety guardrails. Sapling installed and on your PATH Restart Claude Code. Verify with — you should see the server listed. Add to your MCP config file (, , etc.): 22 tools across three tiers: Tier | Tools | Confirmation | ------|-------|-------------| Read | | None | Write | | Destructive ops warn LLM to…

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
6mo agoLast update
Package
Authorio.github.donovan-jasper
LicenseUnknown
Version0.1.2
Sourcemcp-registry
npmsl-mcp
GitHubdonovan-jasper/sl-mcp
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface22 tools · 1 privileged
Security scan✓ Cleanv0.1.2 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

22 tools · 1 privileged
Statically extracted from the published packagev0.1.2 · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

sl_gotoNo description published

This tool published no description. Forge does not invent one.

sl_commitNo description published

This tool published no description. Forge does not invent one.

sl_amendNo description published

This tool published no description. Forge does not invent one.

sl_rebaseNo description published

This tool published no description. Forge does not invent one.

sl_shelveNo description published

This tool published no description. Forge does not invent one.

sl_unshelveNo description published

This tool published no description. Forge does not invent one.

sl_addNo description published

This tool published no description. Forge does not invent one.

sl_removeprivilegedNo description published

This tool published no description. Forge does not invent one.

sl_forgetNo description published

This tool published no description. Forge does not invent one.

sl_revertNo description published

This tool published no description. Forge does not invent one.

sl_undoNo description published

This tool published no description. Forge does not invent one.

sl_statusNo description published

This tool published no description. Forge does not invent one.

sl_diffNo description published

This tool published no description. Forge does not invent one.

sl_logNo description published

This tool published no description. Forge does not invent one.

sl_showNo description published

This tool published no description. Forge does not invent one.

sl_blameNo description published

This tool published no description. Forge does not invent one.

sl_catNo description published

This tool published no description. Forge does not invent one.

sl_rootNo description published

This tool published no description. Forge does not invent one.

sl_smartlogNo description published

This tool published no description. Forge does not invent one.

sl_pullNo description published

This tool published no description. Forge does not invent one.

sl_pushNo description published

This tool published no description. Forge does not invent one.

sl_pr_submitNo description published

This tool published no description. Forge does not invent one.

0 of 22 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP server for Sapling (). Gives LLMs structured access to Sapling repos with built-in safety guardrails. Sapling installed and on your PATH Restart Claude Code. Verify with — you should see the server listed. Add to your MCP config file (, , etc.): 22 tools across three tiers: Tier | Tools | Confirmation | ------|-------|-------------| Read | | None | Write | | Destructive ops warn LLM to confirm | Remote | | Always confirm with user | Force push to / is blocked server-side (not just a…

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

22 tools · 1 privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.