AWS MCP Servers
Open source MCP Servers for AWS
Is AWS MCP Servers safe? Promising trust profile, but some evidence still deserves review.
Compare AWS MCP Servers
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: AWS MCP Servers scores 73.0/100 (Grade B), ranked #284 of 1371 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 9.1/10; 100% of recent commits are signed; last pushed 2026-10-09. Every point is earned from checkable signals — never paid placement. How scoring works →
Chain of custody
Scanners check what the code says. This traces who ships AWS MCP Servers and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Signed
github.com/awslabs/mcp, Apache-2.0, last pushed 2026-10-09. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.
-
Review and release Strong
OpenSSF Scorecard rates the repository's practices 9.1/10 (scanned Oct 11, 2026). The checks that decide who can get a change released:
- Code Review10
- Branch Protection10
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions10
- Pinned Dependencies10
All 14 Scorecard checks
Binary-Artifacts 10Branch-Protection 10CII-Best-Practices 5Code-Review 10Dangerous-Workflow 10Fuzzing 0License 10Maintained 10Packaging 10Pinned-Dependencies 10SAST 9Security-Policy 10Signed-Releases -1Token-Permissions 10 -
Published packages None
No registry package. AWS MCP Servers is used from its repository, so what you run is whatever you check out: pin a release tag or commit.
Changes to this chain
No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of AWS MCP Servers.
Evidence behind this score
Coverage C: 2 of 5 independent evidence types found.
- GitHub repository data
- Package downloads (missing)
- Supply-chain checks
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues AWS MCP Servers’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.
What this score doesn’t check
It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.
How AWS MCP Servers compares in MCP Servers
- #167 Dynatrace MCP 73.2 +0.2
- #168 Quicken Mac MCP 73.1 +0.1
- #169 AWS MCP Servers 73.0 this agent
- #170 Arm MCP Server 72.9 −0.1
- #171 Hound MCP 72.9 −0.1
Bars show each HVTrust score; the tick marks AWS MCP Servers’s 73.0.
Where the 73.0 comes from
HVTrust dimensions vs the MCP Servers average
73.0 / 100 · 100.0% confidenceAWS MCP Servers MCP Servers average (781 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
86.3 / 100Common questions about AWS MCP Servers
Does AWS MCP Servers publish package provenance?
Does AWS MCP Servers have an OpenSSF Scorecard?
Is AWS MCP Servers actively maintained?
What license does AWS MCP Servers use?
Are AWS MCP Servers's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to AWS MCP Servers's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain AWS MCP Servers?
For maintainers
HVTrust scores AWS MCP Servers from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/aws-mcp-servers)
<a href="https://hvtracker.net/agents/aws-mcp-servers"><img src="https://hvtracker.net/badge/aws-mcp-servers.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON