Localstack (giovane.martins) MCP Server

@giovane.martins/localstack npm v1.1.5

Published by @giovane.martins — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for LocalStack AWS services

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
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.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 93/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

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 a deduction.

Findings 3

critical Completed toxic-flow trifecta across toolsMTC-FLOW-002

This server (without client built-ins) exposes a complete data-exfiltration chain: s3_get_object → secretsmanager_get_secret → ses_send_email. Untrusted input is ingested, private data is read, and it can be sent to an external sink via the agent composing the tools (→). Static analysis proves the primitive exists, not that a specific run will occur.

Fix: Remove one leg of the trifecta: isolate untrusted-input tools from secret-reading tools and from egress tools, or require human approval between them.

Location: flow s3_get_object → secretsmanager_get_secret → ses_send_email

medium Tool "s3_put_object" can modify the filesystemMTC-CAP-002

Tool "s3_put_object" can write, overwrite or delete files (keyword "put_object" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool s3_put_object

low Mutating tool "s3_put_object" declares no destructiveHintMTC-CAP-005

Tool "s3_put_object" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool s3_put_object

Tools 73

Each tool and what it can reach — statically extracted from the published source.

  • s3_get_objectingests untrusted input
  • s3_put_objectwrites files
  • secretsmanager_get_secretreads sensitive data
  • secretsmanager_list_secretsreads sensitive data
  • ses_send_emailnetwork egress
  • sqs_send_messagenetwork egress
  • dynamodb_create_tableno sensitive capability
  • dynamodb_delete_itemno sensitive capability
  • dynamodb_delete_tableno sensitive capability
  • dynamodb_describe_tableno sensitive capability
Show 63 more tools ↓
  • dynamodb_get_itemno sensitive capability
  • dynamodb_list_tablesno sensitive capability
  • dynamodb_put_itemno sensitive capability
  • dynamodb_queryno sensitive capability
  • dynamodb_scanno sensitive capability
  • eventbridge_create_busno sensitive capability
  • eventbridge_delete_busno sensitive capability
  • eventbridge_delete_ruleno sensitive capability
  • eventbridge_describe_ruleno sensitive capability
  • eventbridge_disable_ruleno sensitive capability
  • eventbridge_enable_ruleno sensitive capability
  • eventbridge_list_busesno sensitive capability
  • eventbridge_list_rulesno sensitive capability
  • eventbridge_list_targetsno sensitive capability
  • eventbridge_put_eventsno sensitive capability
  • eventbridge_put_ruleno sensitive capability
  • eventbridge_put_targetsno sensitive capability
  • eventbridge_remove_targetsno sensitive capability
  • kinesis_create_streamno sensitive capability
  • kinesis_delete_streamno sensitive capability
  • kinesis_describe_streamno sensitive capability
  • kinesis_get_recordsno sensitive capability
  • kinesis_list_streamsno sensitive capability
  • kinesis_put_recordno sensitive capability
  • kinesis_put_recordsno sensitive capability
  • lambda_create_functionno sensitive capability
  • lambda_delete_functionno sensitive capability
  • lambda_get_functionno sensitive capability
  • lambda_invokeno sensitive capability
  • lambda_list_functionsno sensitive capability
  • s3_create_bucketno sensitive capability
  • s3_delete_bucketno sensitive capability
  • s3_delete_objectno sensitive capability
  • s3_list_bucketsno sensitive capability
  • s3_list_objectsno sensitive capability
  • secretsmanager_create_secretno sensitive capability
  • secretsmanager_delete_secretno sensitive capability
  • secretsmanager_describe_secretno sensitive capability
  • secretsmanager_restore_secretno sensitive capability
  • secretsmanager_update_secretno sensitive capability
  • ses_delete_identityno sensitive capability
  • ses_get_identity_verification_attributesno sensitive capability
  • ses_list_identitiesno sensitive capability
  • ses_verify_email_identityno sensitive capability
  • sns_create_topicno sensitive capability
  • sns_delete_topicno sensitive capability
  • sns_list_subscriptions_by_topicno sensitive capability
  • sns_list_topicsno sensitive capability
  • sns_publishno sensitive capability
  • sns_subscribeno sensitive capability
  • sns_unsubscribeno sensitive capability
  • sqs_create_queueno sensitive capability
  • sqs_delete_messageno sensitive capability
  • sqs_delete_queueno sensitive capability
  • sqs_list_queuesno sensitive capability
  • sqs_purge_queueno sensitive capability
  • sqs_receive_messagesno sensitive capability
  • ssm_delete_parameterno sensitive capability
  • ssm_delete_parametersno sensitive capability
  • ssm_describe_parametersno sensitive capability
  • ssm_get_parameterno sensitive capability
  • ssm_get_parameters_by_pathno sensitive capability
  • ssm_put_parameterno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 1

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
v1.1.5 latest A 93/100 3 1.13.0 2026-09-07

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: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/giovane-martins-localstack/badge.svg)](https://mcptrustchecker.com/registry/giovane-martins-localstack)
HTML
<a href="https://mcptrustchecker.com/registry/giovane-martins-localstack"><img src="https://mcptrustchecker.com/registry/giovane-martins-localstack/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/giovane-martins-localstack/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 @giovane.martins/localstack --online

Use the free API → How scoring works

Other implementations of Localstack 1

Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →

More in Developer Tools