Is AWS MCP Servers safe to use?

AWS MCP Servers has an HVTrust score of 71.6/100 (Grade B), ranked #117 of 1204 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for AWS MCP Servers?

AWS MCP Servers scores 71.6/100 on HVTracker's evidence-weighted HVTrust scale. It has 9.6k GitHub stars and is categorized under MCP Servers.

AWS MCP Servers

awslabs/mcp

Open source MCP Servers for AWS

MCP Servers Python Grade B Listed Apache-2.0

71.6/100

Rank #117 of 1204

Compare AWS MCP Servers

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-08-08 · 1d ago

Recent change

Tool Surface Changed +3

Is AWS MCP Servers safe? AWS MCP Servers scores 71.6/100 (Grade B), ranked #117 of 1204 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 8.5/10; 100% of recent commits are signed; last pushed 2026-08-08. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#18 Touchdesigner MCP — 72.0 (B) → #19 Safari MCP — 71.9 (B) → #21 Sentry MCP — 71.5 (B) → #22 Supabase MCP Server — 71.1 (B) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-08-09

Tool Surface Changed

Detected tool/plugin surface changed: none → marketplace

2026-08-08

Rank Moved

Rank rose 37 spots (#141 → #104)

2026-08-08

HVTrust Changed

HVTrust up 5.0pts (67.7 → 72.7)

Maintainer Checklist

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Compare with another agent Get email alerts for AWS MCP Servers View MCP Servers Report missing data

88.8

Activity sub-score · out of 100

#20

In MCP Servers

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 →

Activity & Reach

Stars

9.6k

Forks

1.7k

Last Push

2026-08-08

yesterday

Commits (4 wk)

116

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

188

Rank Change

▼13

was #104

Analysis

HVTrust Dimensions vs MCP Servers

71.6 / 100 · 100.0% confidence

AWS MCP Servers MCP Servers average (718 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

15.6 / 25

10.5 above avg 5.1

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.5 below avg 13.3

Transparency50% declared license · 50% OSSF Scorecard

15.7 / 17

6.9 above avg 8.8

Maintenance60% last-push freshness · 40% commit activity

19.9 / 20

7.4 above avg 12.5

AdoptionLog-scaled stars · package downloads

9.6 / 20

4.1 above avg 5.5

Activity Inputs

88.8 / 100

StarsRepository reach

23.9 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

15.0 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

8.5 / 10

OpenSSF Scorecard · scanned Aug 8, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 10

CI-Tests 10

CII-Best-Practices 5

Code-Review 10

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 10

SAST 8

Security-Policy 10

Signed-Releases -1

Token-Permissions 10

Vulnerabilities 0

Is AWS MCP Servers safe?

AWS MCP Servers has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does AWS MCP Servers publish package provenance?

No published build provenance is currently detected for AWS MCP Servers. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does AWS MCP Servers have an OpenSSF Scorecard?

AWS MCP Servers has an OpenSSF Scorecard score of 8.5/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is AWS MCP Servers actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does AWS MCP Servers use?

AWS MCP Servers ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are AWS MCP Servers's commits signed?

100% of the last 100 commits to AWS MCP Servers are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

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

Scored in HVTrust

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 Server Support

high confidence

Implemented

AWS MCP Servers appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

1 detected

Public provider/service dependencies detected.

Amazon Bedrock

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

medium confidence

Marketplace

Marketplace plugin/integration surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

N/A

No package source configured

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

How this surface has changed

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.

2026-08-09

Tool Surface Changed

Detected tool/plugin surface changed: none → marketplace

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: marketplace → none

2026-07-13

Tool Surface Changed

Detected tool/plugin surface changed: none → marketplace

2026-07-13

Provider Added

Runtime surface grew — new detected provider dependency: Amazon Bedrock

2026-07-13

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-07-13

Activity Resumed

Activity resumed

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-08-09

Tool Surface Changed

Detected tool/plugin surface changed: none → marketplace

2026-08-08

Rank Moved

Rank rose 37 spots (#141 → #104)

2026-08-08

HVTrust Changed

HVTrust up 5.0pts (67.7 → 72.7)

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: marketplace → none

2026-07-13

Tool Surface Changed

Detected tool/plugin surface changed: none → marketplace

2026-07-13

Provider Added

Runtime surface grew — new detected provider dependency: Amazon Bedrock

2026-07-13

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-07-13

Activity Resumed

Activity resumed

2026-07-13

Grade Changed

Trust grade D → B

2026-07-13

Rank Moved

Rank rose 231 spots (#321 → #90)

2026-07-13

HVTrust Changed

HVTrust up 45.0pts (25.8 → 70.8)

2026-07-13

Activity Score Changed

Activity score up 86pts (0 → 86)

2026-07-12

Newly Listed

First tracked at rank #321

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/aws-mcp-servers.svg)](https://hvtracker.net/agents/aws-mcp-servers)
            
HTML:
            <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

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.2 · Raw JSON