Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add FerhatDundar/s3-mcp-connector/plugin install s3-connectorWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/ferhatdundar/s3-mcp-connector/s3)<a href="https://agentmods.dev/mcp/ferhatdundar/s3-mcp-connector/s3"><img src="https://agentmods.dev/badge/mcp/ferhatdundar/s3-mcp-connector/s3/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/ferhatdundar/s3-mcp-connector/s3"><img src="https://agentmods.dev/badge/mcp/ferhatdundar/s3-mcp-connector/s3.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
s3 scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"s3": {
"command": "${CLAUDE_PLUGIN_ROOT}/servers/go/s3-connector-server",
"env": {
"AWS_REGION": "us-east-1",
"AWS_ACCESS_KEY_ID": "PASTE_YOUR_AWS_ACCESS_KEY_ID_HERE",
"AWS_SECRET_ACCESS_KEY": "PASTE_YOUR_AWS_SECRET_ACCESS_KEY_HERE",
"S3_ENDPOINT_URL": "",
"S3_FORCE_PATH_STYLE": "false"
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 12 lines scan A d317e65cf4f7
s3 is an MCP server published in the GitHub repository FerhatDundar/s3-mcp-connector (0 stars, last pushed 6d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
pkg-go-dev
Go modules MCP — wraps proxy.golang.org. Remote server at gateway.pipeworx.io.
goproxy
Go module proxy — module info, versions, go.mod. Remote server at gateway.pipeworx.io.
unraid
Rust MCP server and CLI for Unraid GraphQL operations across NAS, Docker, VM, and storage workflows. Runs locally from the @dinglebear/unraid npm package. Needs 6 environment variables to run.
go
Structured Go tool output (build, test, vet) as typed JSON diagnostics. Runs locally from the @paretools/go npm package.
pare-go
Pare Go ג€” Structured Go tool output (build, test, vet, fmt, mod) as typed JSON diagnostics. Runs locally from the @paretools/go npm package.
unraid-mcp
MCP Server for Unraid API - provides tools to interact with an Unraid server's GraphQL API. Runs locally from the unraid-mcp Python package. Needs 3 environment variables to run.