# io.github.stufently/yandex-s3-mcp-ai-cli (oci · ghcr.io/stufently/yandex-s3-mcp-ai-cli)

Yandex Cloud S3 MCP server and AI CLI with scoped access and human approval for destructive actions.

- Trust score: 39/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- oci · `ghcr.io/stufently/yandex-s3-mcp-ai-cli`: 39/100 (this document), [markdown](https://verifymcp.io/servers/stufently-yandex-s3-mcp-ai-cli/ghcr-io-stufently-yandex-s3-mcp-ai-cli.md), [page](https://verifymcp.io/servers/stufently-yandex-s3-mcp-ai-cli/ghcr-io-stufently-yandex-s3-mcp-ai-cli)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/stufently/yandex-s3-mcp-ai-cli`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-18.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 84/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to stufently/yandex-s3-mcp-ai-cli).
  - License check failed: no license is declared.
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 29/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (poor).
  - Tool/resource definitions use about 801 tokens (~47/item across 17 items; 14 tools + 3 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**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

### How do I install the io.github.stufently/yandex-s3-mcp-ai-cli server?

io.github.stufently/yandex-s3-mcp-ai-cli runs locally as a container image, launched with docker run --rm -i -e YANDEX_S3_ACCESS_KEY_ID -e YANDEX_S3_SECRET_ACCESS_KEY -e YANDEX_S3_POOL -e YANDEX_S3_ENDPOINT -e YANDEX_S3_ALLOW_INSECURE -e YANDEX_S3_ALLOW -e YANDEX_S3_DESTRUCTIVE_POLICY -e YANDEX_S3_ALLOWED_BUCKETS -e YANDEX_S3_ALLOWED_PREFIXES -e YANDEX_S3_FILE_ROOT -e YANDEX_S3_AUDIT_FILE ghcr.io/stufently/yandex-s3-mcp-ai-cli:0.1.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add stufently-yandex-s3-mcp-ai-cli -- docker run --rm -i -e YANDEX_S3_ACCESS_KEY_ID -e YANDEX_S3_SECRET_ACCESS_KEY -e YANDEX_S3_POOL -e YANDEX_S3_ENDPOINT -e YANDEX_S3_ALLOW_INSECURE -e YANDEX_S3_ALLOW -e YANDEX_S3_DESTRUCTIVE_POLICY -e YANDEX_S3_ALLOWED_BUCKETS -e YANDEX_S3_ALLOWED_PREFIXES -e YANDEX_S3_FILE_ROOT -e YANDEX_S3_AUDIT_FILE ghcr.io/stufently/yandex-s3-mcp-ai-cli:0.1.0
```

This image reads YANDEX_S3_ACCESS_KEY_ID, YANDEX_S3_SECRET_ACCESS_KEY, YANDEX_S3_POOL, YANDEX_S3_ENDPOINT, YANDEX_S3_ALLOW_INSECURE, YANDEX_S3_ALLOW, YANDEX_S3_DESTRUCTIVE_POLICY, YANDEX_S3_ALLOWED_BUCKETS, YANDEX_S3_ALLOWED_PREFIXES, YANDEX_S3_FILE_ROOT and YANDEX_S3_AUDIT_FILE. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Cursor

```json
{
  "mcpServers": {
    "stufently-yandex-s3-mcp-ai-cli": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "YANDEX_S3_ACCESS_KEY_ID",
        "-e",
        "YANDEX_S3_SECRET_ACCESS_KEY",
        "-e",
        "YANDEX_S3_POOL",
        "-e",
        "YANDEX_S3_ENDPOINT",
        "-e",
        "YANDEX_S3_ALLOW_INSECURE",
        "-e",
        "YANDEX_S3_ALLOW",
        "-e",
        "YANDEX_S3_DESTRUCTIVE_POLICY",
        "-e",
        "YANDEX_S3_ALLOWED_BUCKETS",
        "-e",
        "YANDEX_S3_ALLOWED_PREFIXES",
        "-e",
        "YANDEX_S3_FILE_ROOT",
        "-e",
        "YANDEX_S3_AUDIT_FILE",
        "ghcr.io/stufently/yandex-s3-mcp-ai-cli:0.1.0"
      ]
    }
  }
}
```

This image reads YANDEX_S3_ACCESS_KEY_ID, YANDEX_S3_SECRET_ACCESS_KEY, YANDEX_S3_POOL, YANDEX_S3_ENDPOINT, YANDEX_S3_ALLOW_INSECURE, YANDEX_S3_ALLOW, YANDEX_S3_DESTRUCTIVE_POLICY, YANDEX_S3_ALLOWED_BUCKETS, YANDEX_S3_ALLOWED_PREFIXES, YANDEX_S3_FILE_ROOT and YANDEX_S3_AUDIT_FILE. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### VS Code

```json
{
  "servers": {
    "stufently-yandex-s3-mcp-ai-cli": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "YANDEX_S3_ACCESS_KEY_ID",
        "-e",
        "YANDEX_S3_SECRET_ACCESS_KEY",
        "-e",
        "YANDEX_S3_POOL",
        "-e",
        "YANDEX_S3_ENDPOINT",
        "-e",
        "YANDEX_S3_ALLOW_INSECURE",
        "-e",
        "YANDEX_S3_ALLOW",
        "-e",
        "YANDEX_S3_DESTRUCTIVE_POLICY",
        "-e",
        "YANDEX_S3_ALLOWED_BUCKETS",
        "-e",
        "YANDEX_S3_ALLOWED_PREFIXES",
        "-e",
        "YANDEX_S3_FILE_ROOT",
        "-e",
        "YANDEX_S3_AUDIT_FILE",
        "ghcr.io/stufently/yandex-s3-mcp-ai-cli:0.1.0"
      ]
    }
  }
}
```

This image reads YANDEX_S3_ACCESS_KEY_ID, YANDEX_S3_SECRET_ACCESS_KEY, YANDEX_S3_POOL, YANDEX_S3_ENDPOINT, YANDEX_S3_ALLOW_INSECURE, YANDEX_S3_ALLOW, YANDEX_S3_DESTRUCTIVE_POLICY, YANDEX_S3_ALLOWED_BUCKETS, YANDEX_S3_ALLOWED_PREFIXES, YANDEX_S3_FILE_ROOT and YANDEX_S3_AUDIT_FILE. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Codex

```bash
codex mcp add stufently-yandex-s3-mcp-ai-cli -- docker run --rm -i -e YANDEX_S3_ACCESS_KEY_ID -e YANDEX_S3_SECRET_ACCESS_KEY -e YANDEX_S3_POOL -e YANDEX_S3_ENDPOINT -e YANDEX_S3_ALLOW_INSECURE -e YANDEX_S3_ALLOW -e YANDEX_S3_DESTRUCTIVE_POLICY -e YANDEX_S3_ALLOWED_BUCKETS -e YANDEX_S3_ALLOWED_PREFIXES -e YANDEX_S3_FILE_ROOT -e YANDEX_S3_AUDIT_FILE ghcr.io/stufently/yandex-s3-mcp-ai-cli:0.1.0
```

This image reads YANDEX_S3_ACCESS_KEY_ID, YANDEX_S3_SECRET_ACCESS_KEY, YANDEX_S3_POOL, YANDEX_S3_ENDPOINT, YANDEX_S3_ALLOW_INSECURE, YANDEX_S3_ALLOW, YANDEX_S3_DESTRUCTIVE_POLICY, YANDEX_S3_ALLOWED_BUCKETS, YANDEX_S3_ALLOWED_PREFIXES, YANDEX_S3_FILE_ROOT and YANDEX_S3_AUDIT_FILE. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "stufently-yandex-s3-mcp-ai-cli": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "-e",
        "YANDEX_S3_ACCESS_KEY_ID",
        "-e",
        "YANDEX_S3_SECRET_ACCESS_KEY",
        "-e",
        "YANDEX_S3_POOL",
        "-e",
        "YANDEX_S3_ENDPOINT",
        "-e",
        "YANDEX_S3_ALLOW_INSECURE",
        "-e",
        "YANDEX_S3_ALLOW",
        "-e",
        "YANDEX_S3_DESTRUCTIVE_POLICY",
        "-e",
        "YANDEX_S3_ALLOWED_BUCKETS",
        "-e",
        "YANDEX_S3_ALLOWED_PREFIXES",
        "-e",
        "YANDEX_S3_FILE_ROOT",
        "-e",
        "YANDEX_S3_AUDIT_FILE",
        "ghcr.io/stufently/yandex-s3-mcp-ai-cli:0.1.0"
      ],
      "enabled": true
    }
  }
}
```

This image reads YANDEX_S3_ACCESS_KEY_ID, YANDEX_S3_SECRET_ACCESS_KEY, YANDEX_S3_POOL, YANDEX_S3_ENDPOINT, YANDEX_S3_ALLOW_INSECURE, YANDEX_S3_ALLOW, YANDEX_S3_DESTRUCTIVE_POLICY, YANDEX_S3_ALLOWED_BUCKETS, YANDEX_S3_ALLOWED_PREFIXES, YANDEX_S3_FILE_ROOT and YANDEX_S3_AUDIT_FILE. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Hermes

```yaml
mcp_servers:
  stufently-yandex-s3-mcp-ai-cli:
    command: "docker"
    args: ["run", "--rm", "-i", "-e", "YANDEX_S3_ACCESS_KEY_ID", "-e", "YANDEX_S3_SECRET_ACCESS_KEY", "-e", "YANDEX_S3_POOL", "-e", "YANDEX_S3_ENDPOINT", "-e", "YANDEX_S3_ALLOW_INSECURE", "-e", "YANDEX_S3_ALLOW", "-e", "YANDEX_S3_DESTRUCTIVE_POLICY", "-e", "YANDEX_S3_ALLOWED_BUCKETS", "-e", "YANDEX_S3_ALLOWED_PREFIXES", "-e", "YANDEX_S3_FILE_ROOT", "-e", "YANDEX_S3_AUDIT_FILE", "ghcr.io/stufently/yandex-s3-mcp-ai-cli:0.1.0"]
```

This image reads YANDEX_S3_ACCESS_KEY_ID, YANDEX_S3_SECRET_ACCESS_KEY, YANDEX_S3_POOL, YANDEX_S3_ENDPOINT, YANDEX_S3_ALLOW_INSECURE, YANDEX_S3_ALLOW, YANDEX_S3_DESTRUCTIVE_POLICY, YANDEX_S3_ALLOWED_BUCKETS, YANDEX_S3_ALLOWED_PREFIXES, YANDEX_S3_FILE_ROOT and YANDEX_S3_AUDIT_FILE. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Netclaw

```json
{
  "McpServers": {
    "stufently-yandex-s3-mcp-ai-cli": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "-e",
        "YANDEX_S3_ACCESS_KEY_ID",
        "-e",
        "YANDEX_S3_SECRET_ACCESS_KEY",
        "-e",
        "YANDEX_S3_POOL",
        "-e",
        "YANDEX_S3_ENDPOINT",
        "-e",
        "YANDEX_S3_ALLOW_INSECURE",
        "-e",
        "YANDEX_S3_ALLOW",
        "-e",
        "YANDEX_S3_DESTRUCTIVE_POLICY",
        "-e",
        "YANDEX_S3_ALLOWED_BUCKETS",
        "-e",
        "YANDEX_S3_ALLOWED_PREFIXES",
        "-e",
        "YANDEX_S3_FILE_ROOT",
        "-e",
        "YANDEX_S3_AUDIT_FILE",
        "ghcr.io/stufently/yandex-s3-mcp-ai-cli:0.1.0"
      ]
    }
  }
}
```

This image reads YANDEX_S3_ACCESS_KEY_ID, YANDEX_S3_SECRET_ACCESS_KEY, YANDEX_S3_POOL, YANDEX_S3_ENDPOINT, YANDEX_S3_ALLOW_INSECURE, YANDEX_S3_ALLOW, YANDEX_S3_DESTRUCTIVE_POLICY, YANDEX_S3_ALLOWED_BUCKETS, YANDEX_S3_ALLOWED_PREFIXES, YANDEX_S3_FILE_ROOT and YANDEX_S3_AUDIT_FILE. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Other

```json
{
  "mcpServers": {
    "stufently-yandex-s3-mcp-ai-cli": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "YANDEX_S3_ACCESS_KEY_ID",
        "-e",
        "YANDEX_S3_SECRET_ACCESS_KEY",
        "-e",
        "YANDEX_S3_POOL",
        "-e",
        "YANDEX_S3_ENDPOINT",
        "-e",
        "YANDEX_S3_ALLOW_INSECURE",
        "-e",
        "YANDEX_S3_ALLOW",
        "-e",
        "YANDEX_S3_DESTRUCTIVE_POLICY",
        "-e",
        "YANDEX_S3_ALLOWED_BUCKETS",
        "-e",
        "YANDEX_S3_ALLOWED_PREFIXES",
        "-e",
        "YANDEX_S3_FILE_ROOT",
        "-e",
        "YANDEX_S3_AUDIT_FILE",
        "ghcr.io/stufently/yandex-s3-mcp-ai-cli:0.1.0"
      ]
    }
  }
}
```

This image reads YANDEX_S3_ACCESS_KEY_ID, YANDEX_S3_SECRET_ACCESS_KEY, YANDEX_S3_POOL, YANDEX_S3_ENDPOINT, YANDEX_S3_ALLOW_INSECURE, YANDEX_S3_ALLOW, YANDEX_S3_DESTRUCTIVE_POLICY, YANDEX_S3_ALLOWED_BUCKETS, YANDEX_S3_ALLOWED_PREFIXES, YANDEX_S3_FILE_ROOT and YANDEX_S3_AUDIT_FILE. Set them in your client's env block for this server; docker run -e passes each one through to the container.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-18 (score 39, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-17 (score 38, +1)

- [functional improvement] Stability: unverified → 0.07

### 2026-10-15 (score 37)

First indexed and scored.

## MCP tools (14)

### `s3_get_bucket_config` (~38 tokens)

Read location, versioning, CORS, policy and Object Lock; report absent/unsupported configuration.

Input parameters:

- `bucket` (string, required)

### `s3_get_object` (~67 tokens)

Read at most 262144 bytes inline as text/base64; use presign for larger objects.

Input parameters:

- `bucket` (string, required)
- `encoding` (string)
- `key` (string, required)
- `max_bytes` (integer)
- `version_id` (string)

### `s3_get_object_tagging` (~38 tokens)

Get object tags.

Input parameters:

- `bucket` (string, required)
- `key` (string, required)
- `version_id` (string)

### `s3_head_object` (~36 tokens)

Read object metadata.

Input parameters:

- `bucket` (string, required)
- `key` (string, required)
- `version_id` (string)

### `s3_largest_objects` (~67 tokens)

Bounded largest objects scan, default max_scan 10000; partial results carry continuation token.

Input parameters:

- `bucket` (string, required)
- `continuation_token` (string)
- `limit` (integer)
- `max_scan` (integer)
- `prefix` (string)

### `s3_list_buckets` (~33 tokens)

List visible buckets with pagination.

Input parameters:

- `continuation_token` (string)
- `max_keys` (integer)

### `s3_list_multipart_uploads` (~60 tokens)

List unfinished uploads; pass both returned markers.

Input parameters:

- `bucket` (string, required)
- `continuation_token` (string)
- `max_keys` (integer)
- `prefix` (string)
- `upload_id` (string)

### `s3_list_object_versions` (~59 tokens)

List versions and delete markers with both pagination markers.

Input parameters:

- `bucket` (string, required)
- `continuation_token` (string)
- `max_keys` (integer)
- `prefix` (string)
- `version_marker` (string)

### `s3_list_objects` (~54 tokens)

List a scoped prefix, at most 1000 objects per page.

Input parameters:

- `bucket` (string, required)
- `continuation_token` (string)
- `max_keys` (integer)
- `prefix` (string)

### `s3_list_parts` (~52 tokens)

List multipart parts.

Input parameters:

- `bucket` (string, required)
- `continuation_token` (string)
- `key` (string, required)
- `max_keys` (integer)
- `upload_id` (string, required)

### `s3_prefix_usage` (~64 tokens)

Bounded usage by first-level prefixes; paginate aggregate rows with next_result_offset.

Input parameters:

- `bucket` (string, required)
- `continuation_token` (string)
- `max_scan` (integer)
- `prefix` (string)
- `result_offset` (integer)

### `s3_presign_get` (~58 tokens)

Create signed GET URL; default 3600 seconds, provider maximum is unverified.

Input parameters:

- `bucket` (string, required)
- `expires_seconds` (integer)
- `key` (string, required)
- `version_id` (string)

### `s3_preview_object` (~62 tokens)

Preview first at most 65536 bytes, detected type and CSV header.

Input parameters:

- `bucket` (string, required)
- `encoding` (string)
- `key` (string, required)
- `max_bytes` (integer)
- `version_id` (string)

### `s3_unfinished_uploads` (~75 tokens)

Find uploads older than N hours (default 24), bounded by max_scan.

Input parameters:

- `bucket` (string, required)
- `continuation_token` (string)
- `max_scan` (integer)
- `older_than_hours` (number)
- `prefix` (string)
- `upload_id` (string)

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/stufently-yandex-s3-mcp-ai-cli/ghcr-io-stufently-yandex-s3-mcp-ai-cli#diagnostics

## Score history

- 2026-10-18: 39
- 2026-10-17: 38
- 2026-10-16: 37
- 2026-10-15: 37

## Common questions

### What is the io.github.stufently/yandex-s3-mcp-ai-cli server?

io.github.stufently/yandex-s3-mcp-ai-cli is listed in the public MCP registry as io.github.stufently/yandex-s3-mcp-ai-cli. Yandex Cloud S3 MCP server and AI CLI with scoped access and human approval for destructive actions. This page covers its container image (ghcr.io/stufently/yandex-s3-mcp-ai-cli).

### Is the io.github.stufently/yandex-s3-mcp-ai-cli server safe to use?

io.github.stufently/yandex-s3-mcp-ai-cli scores 39 out of 100 on VerifyMCP. Its build provenance is signed and verified. 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.stufently/yandex-s3-mcp-ai-cli server expose?

io.github.stufently/yandex-s3-mcp-ai-cli exposes 14 tools: s3_get_bucket_config, s3_get_object, s3_get_object_tagging, s3_head_object, s3_largest_objects, and 9 more. Their descriptions and schemas cost roughly 763 tokens of context every time the server is loaded.

### Is the io.github.stufently/yandex-s3-mcp-ai-cli server still maintained?

io.github.stufently/yandex-s3-mcp-ai-cli is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- GitHub Container Registry: https://ghcr.io/stufently/yandex-s3-mcp-ai-cli
- Repository: https://github.com/stufently/yandex-s3-mcp-ai-cli
- Changelog RSS feed: https://verifymcp.io/servers/stufently-yandex-s3-mcp-ai-cli/ghcr-io-stufently-yandex-s3-mcp-ai-cli.xml
- Changelog JSON feed: https://verifymcp.io/servers/stufently-yandex-s3-mcp-ai-cli/ghcr-io-stufently-yandex-s3-mcp-ai-cli.json
- HTML version of this page: https://verifymcp.io/servers/stufently-yandex-s3-mcp-ai-cli/ghcr-io-stufently-yandex-s3-mcp-ai-cli