Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search
Nothing to run from here
Steadfast Repository Governance 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.
94/100
trust score
12
downloads a day
local
runs on your machine
129
downloads in 30d
What it does
Local-first repository governance and verification tools for AI coding agents.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user steadfast-repository-governance-mcp '--' uvx --from steadfast-governance steadfast
# 2 — ask your agent for something these tools do
# steadfast, steadfast_ecosystem, steadfast_skill_route and 12 more
Steadfast Repository Governance costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publisher
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 Steadfast Repository Governance 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.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need uv (docs.astral.sh/uv): uvx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user steadfast-repository-governance-mcp '--' uvx --from steadfast-governance steadfastReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
15 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
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.
Return Steadfast entrypoints, installed agent integrations, skills and cost constraints.
No parameter schema on file.
Inventory repository skills and MCP server declarations; apply owner-configured trust labels without executing integrations.
No parameter schema on file.
Rank repository SKILL.md files for a natural-language task. Reads skill content but never executes it or claims an agent ran.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task | string | yes | — |
| limit | integer | no | — |
Evaluate owner-approved permissions for a skill, plugin, or MCP server. This reports policy only and never executes the component.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kind | string | yes | — |
| name | string | yes | — |
| permissions | array | no | — |
Run the read-only governance report and return structured JSON findings.
No parameter schema on file.
Classify changed paths, identify likely test/documentation gaps, and recommend review gates. Path heuristics are advisory, not proof of coverage.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| changed_paths | array | no | Optional explicit repository-relative paths. Omit to inspect the current Git change set. |
| base | string | no | Optional Git base ref for comparison. |
Return the dependency-aware local execution plan, optionally explaining one goal.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| goal | string | no | — |
Show which supported local coding-agent integrations are installed.
No parameter schema on file.
List issued agent work orders and their expiry/status without mutating repository state.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | — |
Read and integrity-check one scoped agent work-order contract.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | string | yes | — |
Render a copy-ready, scope-bounded execution instruction for a live work order. Does not execute an agent.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | string | yes | — |
Issue a bounded work contract for a configured, dependency-ready goal. This writes a work-order record but does not execute an agent.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| goal_id | string | yes | — |
| owner | string | no | — |
| ttl_minutes | integer | no | — |
| scope_paths | array | no | — |
Verify a work order's scope and integrity and run the repository's configured validation pipeline. May execute commands from the validated pipeline manifest.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | string | yes | — |
Close a work order only after successful verification.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | string | yes | — |
Return a repository inventory and implementation-budget summary.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- 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 Steadfast Repository Governance 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 94 / 100
Release 0.4.1 · scanned 28 Oct 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 score94
Findings5 threat · 0 capability
Capabilityhigh
Coveragesource
Verificationsource
Surface digest3effa780e6e3d201362515474d72c94b0b632d843b14aa40c1914d8d3b1a0859
Score vectorthreat 100 → client 94
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
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 sourceread
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>".
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. high 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. | ||
can start a fixed program (a process-spawning capability, not arbitrary code execution)
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 digest3effa780e6e3d201
Scanned2026-10-28
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
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.4.1. Pin a release below and the command asks for exactly that one.
0.4.1
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 Steadfast Repository Governance 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.