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.
Available components
Last scanned (4 hours ago)
Scores higher than 53% of OCI servers
Category Documents and Files
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 → Why this is hard to score →
Supply Chain Security0
- 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.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency84
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to stufently/yandex-s3-mcp-ai-cli). View diagnostics → Pass
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability29
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (poor).Fail
- Tool/resource definitions use about 801 tokens (~47/item across 17 items; 14 tools + 3 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
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.
- 18 Oct 26 +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.
- 17 Oct 26 +1
- Stability: unverified → 0.07 ▲ functional
- 15 Oct 26 37
First indexed and scored.
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 18 Oct 2026 · Analysed oci/ghcr.io/stufently/yandex-s3-mcp-ai-cli@0.1.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | oci |
| Reason | Verified |
| Discovered via | OCI referrers API |
| Source repo | stufently/yandex-s3-mcp-ai-cli |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/stufently/yandex-s3-mcp-ai-cli/.github/workflows/release.yml@refs/tags/v0.1.0 |
| Rekor log index | 3265615274 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha256:53ffda3fc5d5b3782442beb873bae1b739ca215ff9f1feb6e56e9d0205e18f2b |
Background: How many MCP packages publish verified provenance →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
s3_get_bucket_config ~38
Read location, versioning, CORS, policy and Object Lock; report absent/unsupported configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket | string | yes | – |
No output schema declared.
No examples provided.
s3_get_object ~67
Read at most 262144 bytes inline as text/base64; use presign for larger objects.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket | string | yes | – |
| encoding | string | – | – |
| key | string | yes | – |
| max_bytes | integer | – | – |
| version_id | string | – | – |
No output schema declared.
No examples provided.
s3_get_object_tagging ~38
Get object tags.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket | string | yes | – |
| key | string | yes | – |
| version_id | string | – | – |
No output schema declared.
No examples provided.
s3_head_object ~36
Read object metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket | string | yes | – |
| key | string | yes | – |
| version_id | string | – | – |
No output schema declared.
No examples provided.
s3_largest_objects ~67
Bounded largest objects scan, default max_scan 10000; partial results carry continuation token.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket | string | yes | – |
| continuation_token | string | – | – |
| limit | integer | – | – |
| max_scan | integer | – | – |
| prefix | string | – | – |
No output schema declared.
No examples provided.
s3_list_buckets ~33
List visible buckets with pagination.
| Name | Type | Req | Description |
|---|---|---|---|
| continuation_token | string | – | – |
| max_keys | integer | – | – |
No output schema declared.
No examples provided.
s3_list_multipart_uploads ~60
List unfinished uploads; pass both returned markers.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket | string | yes | – |
| continuation_token | string | – | – |
| max_keys | integer | – | – |
| prefix | string | – | – |
| upload_id | string | – | – |
No output schema declared.
No examples provided.
s3_list_object_versions ~59
List versions and delete markers with both pagination markers.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket | string | yes | – |
| continuation_token | string | – | – |
| max_keys | integer | – | – |
| prefix | string | – | – |
| version_marker | string | – | – |
No output schema declared.
No examples provided.
s3_list_objects ~54
List a scoped prefix, at most 1000 objects per page.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket | string | yes | – |
| continuation_token | string | – | – |
| max_keys | integer | – | – |
| prefix | string | – | – |
No output schema declared.
No examples provided.
s3_list_parts ~52
List multipart parts.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket | string | yes | – |
| continuation_token | string | – | – |
| key | string | yes | – |
| max_keys | integer | – | – |
| upload_id | string | yes | – |
No output schema declared.
No examples provided.
s3_prefix_usage ~64
Bounded usage by first-level prefixes; paginate aggregate rows with next_result_offset.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket | string | yes | – |
| continuation_token | string | – | – |
| max_scan | integer | – | – |
| prefix | string | – | – |
| result_offset | integer | – | – |
No output schema declared.
No examples provided.
s3_presign_get ~58
Create signed GET URL; default 3600 seconds, provider maximum is unverified.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket | string | yes | – |
| expires_seconds | integer | – | – |
| key | string | yes | – |
| version_id | string | – | – |
No output schema declared.
No examples provided.
s3_preview_object ~62
Preview first at most 65536 bytes, detected type and CSV header.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket | string | yes | – |
| encoding | string | – | – |
| key | string | yes | – |
| max_bytes | integer | – | – |
| version_id | string | – | – |
No output schema declared.
No examples provided.
s3_unfinished_uploads ~75
Find uploads older than N hours (default 24), bounded by max_scan.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket | string | yes | – |
| continuation_token | string | – | – |
| max_scan | integer | – | – |
| older_than_hours | number | – | – |
| prefix | string | – | – |
| upload_id | string | – | – |
No output schema declared.
No examples provided.
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.
oci · ghcr.io/stufently/yandex-s3-mcp-ai-cli
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.
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.