io.github.sairam0424/ag-bash

NPM · @AG-BASH/MCP-SERVER · SCANNED AUG 3

Sandboxed AI-native bash with 70 agentic tools: run_bash, code edit/diff, WASM Python/JS.

Available components

+13 this week 57 57 Trust /100

Trust breakdown (6 categories)

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 →

Supply Chain Security87

No malware found by supply-chain analysis.Pass
Only part of the dependency tree could be resolved (123 of 134), so this covers what we could see, not the whole tree.Partial
No install/post-install scripts declared.Pass
Only part of the dependency tree could be resolved (123 of 134), so this covers what we could see, not the whole tree. View diagnostics → Partial

Provenance & Transparency45

Source repository is publicly reachable at the declared URL. View diagnostics → Pass
Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
Clear OSI-approved license (Apache-2.0).Pass
Actively maintained (last published 48 days ago).Pass
Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail

Schema Quality & AI Usability45

2% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
AI-judged instruction clarity (good).Pass
Tool/resource definitions use about 5396 tokens (~16/item across 328 items; 70 tools + 258 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management0

Stability not yet verified: two runs of the same published version returned different tool surfaces, so we cannot tell a change in the package from a difference in our own sandbox run.Unverified

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
Structured output schemas are declared (11% of tools); any adoption earns full credit.Pass

Capabilities60

Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @ag-bash/mcp-server

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add sairam0424-ag-bash -- npx -y @ag-bash/mcp-server

# add to Codex CLI

codex mcp add sairam0424-ag-bash -- npx -y @ag-bash/mcp-server

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sairam0424-ag-bash": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@ag-bash/mcp-server"
      ],
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add sairam0424-ag-bash --command npx --arg -y --arg @ag-bash/mcp-server

# ~/.hermes/config.yaml

mcp_servers:
  sairam0424-ag-bash:
    command: "npx"
    args: ["-y", "@ag-bash/mcp-server"]

// mcp.json

{
  "mcpServers": {
    "sairam0424-ag-bash": {
      "command": "npx",
      "args": [
        "-y",
        "@ag-bash/mcp-server"
      ]
    }
  }
}

Changelog

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.

2 Aug 26 +37
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Stability: Stability not yet verified: two runs of the same published version returned different tool surfaces, so we cannot tell a change in the package from a difference in our own sandbox run. security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- Schema quality: unverified → 2 ▲ functional
- Schema quality: unverified → good ▲ functional
- Licence: Apache-2.0 functional
1 Aug 26 +1
- Malware scan: unverified → pass ▲ security
- Schema quality: 2 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
31 Jul 26 +13
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 −38
- Malware scan: pass → unverified ▼ security
- Schema quality: 2 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
27 Jul 26 44

First indexed and scored.

Show 2 earlier entries Hide earlier entries

Diagnostics

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 3 Aug 2026 · Analysed npm/@ag-bash/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 123 packages

123 packages in the resolved dependency tree · 115 deprecated · 41 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 70 exposed · ~3,444 tokens

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.

Tool Tokens

run_bash ~44

Run a bash script in a persistent sandboxed environment. State (cwd, variables, functions) persists between calls.

Input Output Examples

Name	Type	Req	Description
script	string	yes	The bash script to execute.

Name	Type	Req	Description
exitCode	number	yes	Process exit code (0 = success).
stderr	string	yes	Standard error captured from the script.
stdout	string	yes	Standard output captured from the script.

No examples provided.

run_command ~28

Execute a shell command in the sandbox.

Input Output Examples

Name	Type	Req	Description
command	string	yes	The shell command to execute.

No output schema declared.

No examples provided.

run_js ~37

Execute JavaScript code in the sandbox. For persistent state, use run_js_session.

Input Output Examples

Name	Type	Req	Description
code	string	yes	The JS code to execute.

No output schema declared.

No examples provided.

run_js_session ~62

Execute JavaScript code in a persistent session (stateful REPL). Maintains variables and modules between calls.

Input Output Examples

Name	Type	Req	Description
code	string	yes	The JS code to execute.
sessionId	string	yes	Session identifier (e.g., 'main', 'test').

No output schema declared.

No examples provided.

run_python ~36

Execute Python code in the sandbox. For persistent state, use run_python_session.

Input Output Examples

Name	Type	Req	Description
code	string	yes	The Python code to execute.

No output schema declared.

No examples provided.

run_python_session ~59

Execute Python code in a persistent session (stateful REPL). Maintains variables and imports between calls.

Input Output Examples

Name	Type	Req	Description
code	string	yes	The Python code to execute.
sessionId	string	yes	Session identifier (e.g., 'data-analysis').

No output schema declared.

No examples provided.

search_tools ~85

Discover which agentic tools are available for a free-text task description (Code Mode). Returns the best-matching tools by relevance so an agent can pick a tool without pre-loading the full catalog.

Input Output Examples

Name	Type	Req	Description
limit	number	—	Maximum number of matches to return (1-25, default 5).
query	string	yes	Free-text description of the task or capability you need.

Name	Type	Req	Description
matches	array	yes	Matching tools, best first.
query	string	yes	The query that was searched.

No examples provided.

search_tools ~66

Search for available tools by keyword, or select by exact name with 'select:Name1,Name2'.

Input Output Examples

Name	Type	Req	Description
limit	number	—	Max results (default: 10).
query	string	yes	Keyword query or "select:Name1,Name2" for exact lookup.

No output schema declared.

No examples provided.

send_message ~46

Send a message from one agent to another.

Input Output Examples

Name	Type	Req	Description
content	string	yes	Message content.
from	string	yes	Sender agent ID.
to	string	yes	Recipient agent ID.

No output schema declared.

No examples provided.

snapshot ~22

Capture a complete binary snapshot of the current shell state (filesystem + environment).

Input Output Examples

Input schema present but exposes no named parameters.

Name	Type	Req	Description
encoded	string	yes	Base64-encoded opaque state blob.

No examples provided.

sync_mcp_tools ~22

Synchronize and register all MCP tools into the central toolbox.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

task_create ~81

Create a new tracked task with subject, description, owner, and progress text.

Input Output Examples

Name	Type	Req	Description
activeForm	string	—	Spinner text when in_progress (e.g., "Running tests").
description	string	yes	What needs to be done.
owner	string	—	Agent ID that owns this task.
subject	string	yes	Brief title for the task.

No output schema declared.

No examples provided.

task_get ~29

Get full details of a specific task by ID.

Input Output Examples

Name	Type	Req	Description
taskId	string	yes	The task ID.

No output schema declared.

No examples provided.

task_list ~42

List all tracked tasks, optionally filtered by status or owner.

Input Output Examples

Name	Type	Req	Description
owner	string	—	Filter by owner agent ID.
status	string	—	Filter by status.

No output schema declared.

No examples provided.

task_stop ~29

Stop (fail) a running task.

Input Output Examples

Name	Type	Req	Description
taskId	string	yes	The task ID to stop.

No output schema declared.

No examples provided.

task_update ~114

Update a task's status, subject, description, owner, or dependencies.

Input Output Examples

Name	Type	Req	Description
addBlockedBy	string	—	Task IDs that block this task.
addBlocks	string	—	Task IDs that this task blocks.
description	string	—	New description.
owner	string	—	New owner agent ID.
status	string	—	New status: pending, in_progress, completed, failed, blocked.
subject	string	—	New subject.
taskId	string	yes	The task ID to update.

No output schema declared.

No examples provided.

team_create ~37

Create a new agent team for coordinated multi-agent work.

Input Output Examples

Name	Type	Req	Description
description	string	—	Team purpose.
name	string	yes	Team name.

No output schema declared.

No examples provided.

team_delete ~24

Delete an agent team.

Input Output Examples

Name	Type	Req	Description
name	string	yes	Team name or ID.

No output schema declared.

No examples provided.

update_todo ~40

Update the status of a todo item.

Input Output Examples

Name	Type	Req	Description
id	string	yes	The ID of the todo to update.
status	string	yes	New status.

No output schema declared.

No examples provided.

write_file ~46

Create or overwrite a file in the virtual filesystem.

Input Output Examples

Name	Type	Req	Description
content	string	yes	The content to write to the file.
path	string	yes	Absolute path to the file to write.

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

27 Jul 3 Aug