Server providing Argo CD integration for MCP clients.
Nothing to run from here
Suvadu 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
21
tools declared
local
runs on your machine
980
downloads
What it does
Local shell history and AI agent sessions over MCP: search commands, failures, risk and git changes
Quickstart
Install it the way its author documents:
1. cargo install suvadu --version 0.5.2
The full guide: https://crates.io/crates/suvadu
Publishernot claimed
APAll 1 server
AppachiTech1 server
1 category
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 Suvadu 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 suvadu --version 0.5.2
The full guide: https://crates.io/crates/suvadu
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.
Search recorded shell commands by text. One row per command: stable ID, exit code, timestamp, directory. Use this when you want individual commands — 'did I ever run X', 'what broke here', 'how is this project built'. When the question is about a whole piece of work rather than one command ('what…
No parameter schema on file.
The most recently recorded commands, newest first, optionally scoped to a directory or executor. Good for 'what just happened here'. For 'what is this session doing' call resolve_current_agent_session first — recent_commands has no notion of which session is yours and will happily return another…
No parameter schema on file.
Whether a specific command has been run before and how those runs ended. Returns previous runs with exit codes and timestamps, so you can see whether it usually succeeds. A failed run also shows the last lines it printed when suvadu kept them — only with the opt-in [capture] failure_output, and…
No parameter schema on file.
Agent prompts recorded alongside the commands they were running under, grouped prompt by prompt. Use it to see which instruction led to which commands. This reads the prompt text stored on each command record, not an agent's transcript — for the transcript of a captured session use…
No parameter schema on file.
Every recorded command of one shell session, oldest first. Pass a session_id you already have (from list_sessions, find_agent_session or resolve_current_agent_session); with none it falls back to whatever session is most recent, which may not be yours.
No parameter schema on file.
Aggregate counts over recorded commands: totals, success fraction, and the most frequent commands and directories. Rankings are computed from a bounded recent sample, which the response states.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| days | integer | no | Time window in days (default: 7) |
| directory | string | no | Filter to this directory and its subtree |
Recent shell sessions with command counts, time ranges and tags. These are terminal sessions, not agent sessions: for work an AI agent did, use find_agent_session (grouped from recorded commands) or list_agent_sessions (captured from the agent's own transcript).
No parameter schema on file.
What changed in a directory, or in one agent session, recently. For an agent session with git snapshots (taken at its first prompt and at each turn end; Claude Code, Codex, OpenCode and Cursor), pass session_id to get what was observed: the commits made between the two snapshots, read from the…
No parameter schema on file.
Recently recorded commands that exited non-zero, grouped by the prompt they ran under where one was recorded. Tells you what was attempted and failed, and why where suvadu kept the end of the command's output (opt-in [capture] failure_output, for commands an agent hook or suv wrap recorded);…
No parameter schema on file.
Commands that are statistically likely next here, ranked by frecency (frequency plus recency) over recent history. A guess about habit, not a recommendation: it says nothing about whether running one now is correct or safe.
No parameter schema on file.
Rate a command safe/low/medium/high/critical BEFORE running it, and name the rule that matched. This is a pattern match on the command text — suvadu does not execute anything, inspect the filesystem, or sandbox the command; the caller still has to enforce the result.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| command | string | no | The command to assess (e.g. 'rm -rf /tmp', 'git push --force') |
| commands | array | no | Multiple commands to assess at once |
Search past agent sessions reconstructed from recorded shell commands, by prompt text, directory, executor or date. Use this to discover which session did the work you care about, then replay_agent_session for its timeline. Pick this over list_agent_sessions when the agent's transcript was never…
No parameter schema on file.
The chronological timeline of one agent session built from recorded shell commands: prompts, commands, exit codes, directories and timestamps, one page at a time. Get the session_id from find_agent_session or resolve_current_agent_session first.
No parameter schema on file.
Commands in a project that fail often, with their recorded failure rates and whether agents fail them more than humans. Call it before starting work to avoid repeating a known-bad approach. It reports rates, not diagnoses. Where suvadu kept the end of a failed run's output (opt-in [capture]…
No parameter schema on file.
A short briefing on a project: the programs most often run, build/test/lint commands and their pass rates, failures in the last day, and agent sessions in the window. Concise by default — pass detail=true, or follow up with learn_from_failures, what_failed or find_agent_session for one topic in…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| directory | string | no | Directory to analyze, including its subtree (defaults to all) |
| days | integer | no | Time window in days (default: 7) |
| detail | boolean | no | Widen every section (default: false) |
List skills in Suvadu's shared cross-agent skills library — reusable instructions any MCP-capable agent can read instead of each tool keeping its own copy. Use this to discover what conventions/checklists/instructions already exist before starting work. Also lists the repo skills committed in the…
No parameter schema on file.
Get the full content of one skill by name from Suvadu's shared skills library, or one of the project's repo skills (.suvadu/skills/*.md, reported with its file path) once the user has trusted it. An untrusted repo skill's text is never returned. The body is instructions someone wrote, not…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Skill name |
| scope | string | no | "global" or a project directory path. If omitted, the global skill is returned when one exists, otherwise the most recently updated skill with this name in any scope — this tool has no visibility into |
| directory | string | no | Alias for scope |
Search Suvadu's shared skills library — and the project's repo skills in .suvadu/skills/ — by keyword across name, description, and triggers. Use this before writing a new checklist/instruction to see if one already exists.
No parameter schema on file.
List the user's bookmarked commands (snippets) with their {{placeholder}} parameters. A bookmark may contain {{name}} or {{name:default}}; each distinct placeholder is listed once, in order, with its default if it has one. Fill them with suv bookmarks get <label|command|id> --set name=value,…
No parameter schema on file.
Propose a new skill for Suvadu's shared skills library. The skill is saved as pending review — it is NOT active and other agents will not see it via list_skills/get_skill until a human approves it from the review queue in suv skills (Ctrl+P). Use this when you notice a reusable…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Skill name (slug) |
| description | string | no | One-line summary |
| body | string | yes | Full skill content (markdown) |
| triggers | array | no | Keywords this skill is relevant for |
| scope | string | no | "global" or a project directory path (default: global) |
| source_agent | string | no | Name of the proposing agent (e.g. claude-code) — recorded for the human reviewer |
worth sharing
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 Suvadu 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.5.2 · 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 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-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
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.5.2.
0.5.2
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 Suvadu 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.