Awslabs Aws Location MCP Server

awslabs-aws-location-mcp-server PyPI v2.0.18

Published by awslabs — no publish provenance and no vendor-owned scope, so the publisher could not be verified. The repository link below is self-declared.

Trust grade
C
78/100
Last scanned
Trust
C · 78/100
How safe the published surface and source look. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
C Why this grade 100 − 22 = 78/100

Every server starts at 100. These are the exact deductions the deterministic engine applied — each one reproducible, none of it an opinion or an LLM's guess:

PointsWhat was foundCategory
−22 Hardcoded AWS access key id in server code MTC-SRC-008 exfiltration

Grade capped: 1 confirmed high finding → grade capped at C. A hard gate overrides the point total — no amount of clean surface buys back a confirmed catastrophe.

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind the deduction.

Findings 1

high Hardcoded AWS access key id in server code (tests/test_server.py)MTC-SRC-008

A live-looking AWS access key id is hardcoded in `tests/test_server.py:1032`. Secrets in source ship to everyone who installs the package and are a direct credential leak.

Evidence: AWS access key id: AKIA…(redacted)

Fix: Remove the secret, rotate it, and load credentials from the environment or a secret store.

Location: server tests/test_server.py

What this scan could not see

Versions

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v2.0.18 latest C 78/100 1 1.5.0 2026-07-22

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: C · 78/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/awslabs-aws-location-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/awslabs-aws-location-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/awslabs-aws-location-mcp-server"><img src="https://mcptrustchecker.com/registry/awslabs-aws-location-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/awslabs-aws-location-mcp-server/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan awslabs-aws-location-mcp-server --online --registry pypi

Use the free API → How scoring works

More in Cloud & DevOps