io.github.donovan-jasper/sl-mcp
NPM · SL-MCP · SCANNED SEP 25
MCP server for Sapling (sl) version control
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 195 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 997 tokens (~45/item across 22 items; 22 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "sl_remove" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.donovan-jasper/sl-mcp server?
io.github.donovan-jasper/sl-mcp runs locally as an npm package, launched with npx -y sl-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · sl-mcp
claude mcp add donovan-jasper-sl-mcp -- npx -y sl-mcp
{
"mcpServers": {
"donovan-jasper-sl-mcp": {
"command": "npx",
"args": [
"-y",
"sl-mcp"
]
}
}
} {
"servers": {
"donovan-jasper-sl-mcp": {
"command": "npx",
"args": [
"-y",
"sl-mcp"
]
}
}
} codex mcp add donovan-jasper-sl-mcp -- npx -y sl-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"donovan-jasper-sl-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"sl-mcp"
],
"enabled": true
}
}
} openclaw mcp add donovan-jasper-sl-mcp --command npx --arg -y --arg sl-mcp
mcp_servers:
donovan-jasper-sl-mcp:
command: "npx"
args: ["-y", "sl-mcp"] {
"McpServers": {
"donovan-jasper-sl-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"sl-mcp"
]
}
}
} assistant mcp add donovan-jasper-sl-mcp -t stdio -c npx -a -y sl-mcp
{
"mcpServers": {
"donovan-jasper-sl-mcp": {
"command": "npx",
"args": [
"-y",
"sl-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 −3
- Stability: pass → 0.80 functional
- 23 Sept 26 +1
- Stability: 0.97 → pass security
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.77 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Analysed npm/sl-mcp@0.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
sl_add ~33
Start tracking the specified files.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Repository path |
| paths | array | yes | Files to add |
No output schema declared.
No examples provided.
sl_amend ~44
Amend the current commit.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Repository path |
| message | string | – | New commit message |
| paths | array | – | Specific paths to amend |
No output schema declared.
No examples provided.
sl_blame ~49
Show line-by-line annotation of a file
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Repository path |
| path | string | yes | File path to annotate |
| rev | string | – | Revision to blame at |
No output schema declared.
No examples provided.
sl_cat ~47
Print file contents at a given revision
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Repository path |
| path | string | yes | File path to read |
| rev | string | – | Revision to read from |
No output schema declared.
No examples provided.
sl_commit ~46
Create a new commit with the given message.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Repository path |
| message | string | yes | Commit message |
| paths | array | – | Specific paths to commit |
No output schema declared.
No examples provided.
sl_diff ~64
Show differences in working copy or between revisions
| Name | Type | Req | Description |
|---|---|---|---|
| change | string | – | Show diff for a specific changeset |
| cwd | string | – | Repository path |
| path | string | – | Limit diff to a specific path |
| rev | string | – | Revision to diff against |
No output schema declared.
No examples provided.
sl_forget ~37
Stop tracking the specified files without deleting them.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Repository path |
| paths | array | yes | Files to forget |
No output schema declared.
No examples provided.
sl_goto ~72
Update working copy to a given revision. Caution: --clean discards uncommitted changes. Confirm with user before using --clean.
| Name | Type | Req | Description |
|---|---|---|---|
| clean | boolean | – | Discard uncommitted changes (--clean) |
| cwd | string | – | Repository path |
| rev | string | yes | Revision to go to |
No output schema declared.
No examples provided.
sl_log ~52
Show commit history
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Repository path |
| limit | number | – | Maximum number of commits to show (default 10) |
| revs | string | – | Revset expression to filter commits |
No output schema declared.
No examples provided.
sl_pr_submit ~57
Creates or updates a pull request. Always confirm with user before running.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Repository path |
| draft | boolean | – | Create as draft PR (--draft) |
| rev | string | – | Revision to submit (-r) |
No output schema declared.
No examples provided.
sl_pull ~30
Fetches commits from remote. Always confirm with user before running.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Repository path |
No output schema declared.
No examples provided.
sl_push ~70
Pushes commits to remote. Always confirm with user. Force push to main/master is blocked.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Repository path |
| force | boolean | – | Force push (--force) |
| rev | string | – | Revision to push (-r) |
| to | string | – | Destination bookmark (--to) |
No output schema declared.
No examples provided.
sl_rebase ~63
Rebase a revision onto a new destination. Caution: moves commits to a new base. Confirm with user before running.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Repository path |
| dest | string | yes | Destination revision |
| rev | string | yes | Revision to rebase |
No output schema declared.
No examples provided.
sl_remove ~51
Remove files from the working copy and mark them for deletion. Caution: this is destructive and deletes files from disk.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Repository path |
| paths | array | yes | Files to remove |
No output schema declared.
No examples provided.
sl_revert ~65
Revert specified files to their committed state. Caution: discards uncommitted changes to specified files. Confirm with user.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Repository path |
| paths | array | yes | Files to revert |
| rev | string | – | Revision to revert to |
No output schema declared.
No examples provided.
sl_root ~25
Show the root directory of the repository
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Repository path |
No output schema declared.
No examples provided.
sl_shelve ~39
Shelve uncommitted changes.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Repository path |
| name | string | – | Name for the shelved changes |
No output schema declared.
No examples provided.
sl_show ~34
Show details of a specific commit
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Repository path |
| rev | string | – | Revision to show |
No output schema declared.
No examples provided.
sl_smartlog ~27
Show the smartlog graph of commits
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Repository path |
No output schema declared.
No examples provided.
sl_status ~29
Show working copy status (modified, added, removed files)
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Repository path |
No output schema declared.
No examples provided.
sl_undo ~23
Undo the last operation.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Repository path |
No output schema declared.
No examples provided.
sl_unshelve ~40
Restore previously shelved changes.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Repository path |
| name | string | – | Name of the shelved changes to restore |
No output schema declared.
No examples provided.
What is the io.github.donovan-jasper/sl-mcp server?
io.github.donovan-jasper/sl-mcp is listed in the public MCP registry as io.github.donovan-jasper/sl-mcp. MCP server for Sapling (sl) version control. This page covers its npm package (sl-mcp).
Is the io.github.donovan-jasper/sl-mcp server safe to use?
io.github.donovan-jasper/sl-mcp scores 73 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.donovan-jasper/sl-mcp server expose?
io.github.donovan-jasper/sl-mcp exposes 22 tools: sl_status, sl_diff, sl_log, sl_show, sl_blame, and 17 more. Their descriptions and schemas cost roughly 997 tokens of context every time the server is loaded.
Is the io.github.donovan-jasper/sl-mcp server still maintained?
io.github.donovan-jasper/sl-mcp is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.donovan-jasper/sl-mcp server under?
io.github.donovan-jasper/sl-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.