MCP server for AWS S3 with fine-grained tool control and S3-compatible endpoint support.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"com-pulsemcp-s3": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
MCP server for AWS S3 with fine-grained tool control and S3-compatible endpoint support.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationBe the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in cloud
MCP Server for GCP environment for interacting with various Observability APIs.
Yunxiao MCP Server provides AI assistants with the ability to interact with the Yunxiao platform. It provides a set of tools that interact with Yunxiao's API, allowing AI assistants to manage Codeup repository, Project, Pipeline, Packages etc.
MCP server for Datto SaaS Protection — M365/GWS backups, restores, seats.
IAM Policy Autopilot is an open source static code analysis tool that helps you quickly create baseline AWS IAM policies that you can refine as your application evolves. This tool is available as a command-line utility and MCP server for use within AI coding assistants for quickly building IAM policies.
MCP Security Weekly
Get CVE alerts and security updates for com.pulsemcp/s3 and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
We build reliable servers thoughtfully designed for MCP Client-powered workflows.
You can have confidence that any Pulse-branded MCP server was built with these north stars in mind:
These are PulseMCP-branded servers that we intend to maintain indefinitely as our own offerings.
The MCP Registry column controls whether the server is published to the official MCP Registry (com.pulsemcp/<server-name>) by the publish-mcp-registry.yml workflow.
| Name | Description | Local Status | Remote Status | MCP Registry | Target Audience | Notes |
|---|---|---|---|---|---|---|
| pulse-fetch | Pull internet resources into context | 0.3.2 | Not Started | Yes | Agent-building frameworks (e.g. fast-agent, Mastra, PydanticAI) and MCP clients without built-in fetch | Supports Firecrawl and BrightData integrations; HTML noise stripping; Resource caching; LLM extraction |
| pulse-subregistry | Browse the PulseMCP Sub-Registry | 0.0.7 | Not Started | Yes | Developers discovering MCP servers from the PulseMCP Sub-Registry | Search and pagination; Version selection; Integrates with PulseMCP Sub-Registry API |
| image-diff | Programmatic image comparison | 0.1.2 | Not Started | Yes | Developers comparing design mocks against UI implementations | Pixel-level diff with clustering; Heatmap visualization; Anti-aliasing detection; Auto-alignment for different-sized images |
| svg-tracer | Bitmap-to-SVG vect |