Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search
Nothing to run from here
Skipper is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
91/100
trust score
20
tools declared
local
runs on your machine
—
calls last 7d
What it does
Git and forge ops: local git via gitoxide, plus GitHub, GitLab, Gitea and Forgejo
Quickstart
Install it the way its author documents:
1. cargo install skipper --version 0.10.3
The full guide: https://crates.io/crates/skipper
Publishernot claimed
SEAll 2 servers
seuros2 servers
2 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Skipper as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Install it the way its author documents:
1. cargo install skipper --version 0.10.3
The full guide: https://crates.io/crates/skipper
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Inspect tracked changes by scope, returning structured patches, statistics, or changed paths with optional whitespace checks.
No parameter schema on file.
List recent commits with sha, author, date, and subject.
No parameter schema on file.
Show full commit details including subject, body, author, and trailers.
No parameter schema on file.
Show a tracked file at a revision, with optional line range. Untracked worktree edits are ignored.
No parameter schema on file.
Show per-line author attribution for a file, with optional line range.
No parameter schema on file.
List staged, unstaged, and untracked files in the worktree.
No parameter schema on file.
Stage explicit repository-relative files or deletions. Directories, ignored new files, conflicts, and submodules are rejected.
No parameter schema on file.
Create or amend a commit, with optional structured trailers. Signed when commit.gpgsign is set; git hooks are not run.
No parameter schema on file.
Create or delete a local branch. Creation does not check out the branch; deletion rejects checked-out or unmerged branches unless force is set.
No parameter schema on file.
Recent CI runs for this repo, or one by id. Non-blocking
No parameter schema on file.
Wait for a CI run's status to change, or with commit= for every run of a commit to finish, up to wait_secs. Returns the status either way; call again while terminal is false
No parameter schema on file.
List the account's GitHub repos. Account-wide, not this repo
No parameter schema on file.
Fetch a remote's branches and tags, pruning deleted branches. Updates remote-tracking refs only
No parameter schema on file.
Fast-forward the checked-out branch to its upstream. Never merges or rebases; a diverged branch fails
No parameter schema on file.
Push branches and tags to remotes. Never forces or deletes. Asks the user to approve unless confirm is off; check ok per remote
No parameter schema on file.
List the account's GitLab projects. Account-wide, not this repo
No parameter schema on file.
Block until a PR's checks conclude. Long-running; prefer task execution. Unregistered checks count as pending; network blips are retried; times out to a pending snapshot
No parameter schema on file.
Merge a GitHub PR at the head sha it was checked at. Refuses drafts, conflicts, and failing or running checks unless require_checks=false. Asks the user to approve unless confirm is off
No parameter schema on file.
Watch GitHub PRs: merge, close, comments, reviews, checks, pushes. One call blocks until an event on any watched PR; calling while one blocks just adds the PR. Non-blocking state: skipper://watch. Polls with ETags and backoff. Long-running; prefer task execution
No parameter schema on file.
Search Gitea/Forgejo repos by name, paginated. For this repo use skipper://repo
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under BSD-2-Clause
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Skipper or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 91 / 100
Release 0.10.3 · scanned 10 Nov 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score91
Findings1 threat · 0 capability
Capabilityminimal
Coveragemetadata
Verificationrepo
Surface digest2dc22d3bf39daa3966da07121ef3ae7218597d0cc75600bd6ac9471b4c82a657
Score vectorthreat 100 → client 91
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | metadata | inspection depth (metadata) — how much of the target the scan could see | −8 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfacenot available
Implementation sourcenot available
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
The implementation source was not read — the published package was fetched but contains no source files the scanner reads.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
No tool surface was enumerated, so there is nothing to attribute a capability to.
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest2dc22d3bf39daa39
Scanned2026-11-10
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
It installs from its repository rather than from a versioned package, so the command cannot be pinned to a release. The history below is for reading; the current release on file is 0.10.3.
0.10.3
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Skipper can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.