Tracked packageView full profile for terraform-mcp-server →

MCPSafe.io

Security pre-install checks for MCP servers.

Mostly safe — a couple of notes worth reading.

Compare to another server

github · terraform-mcp-serverHEAD

Item: terraform-mcp-server
Rating: 4
Author: MCPSafe

Scanned 5/3/2026, 6:27:21 PM·Cached result·Fast Scan·45 rules·How we decide ↗

AIVSS Score

3.2/ 10

Low

Severity Breakdown

critical

high

medium

low

MCP Server Information

Packageterraform-mcp-server

VersionHEAD

SourceGITHUB

LicenseMPL-2.0

Publisherhashicorp

Package age1y 0m

Stars1.4K

Downloads/wk—

Dependencies0

Repositoryhttps://github.com/hashicorp/terraform-mcp-server

Findings

5 of 5 findings

medium (5)

5 findings

medium (5)

AIVSS 3.2CVSS 4.4

Dockerfile never sets a non-root `USER` directive, so the CMD runs as root by default. Any RCE or library-level vulnerability exploited inside this container gets full privileges (MCP Top-10 R3). Add `USER <non-root>` before CMD / ENTRYPOINT in the final stage — e.g. `USER 1000`, `USER nobody`, or `USER nonroot` on distroless.

Evidence

# Copyright IBM Corp. 2025
# SPDX-License-Identifier: MPL-2.0

# This Dockerfile contains multiple targets.
# Use 'docker build --target=<name> .' to build one.

# ===================================
#
#   Non-release images.
#
# ===================================

# certbuild captures the ca-certificates
FROM docker.mirror.hashicorp.services/alpine:3.22@sha256:4b7ce07002c69e8f3d704a9c5d6fd3053be500b7f1c69fc0d80990c2ad8dd412 AS certbuild
RUN apk add --no-cache ca-certificates

# devbuild compil

Remediation

Create and switch to a non-root user before the CMD / ENTRYPOINT: RUN adduser --system --uid 1000 app USER 1000 Or reuse the base image's shipped non-root account (e.g. `USER nobody`, `USER nonroot` on distroless). Multi-stage builds only need the USER directive in the final stage.

Report false positive →

AIVSS 2.3CVSS 3.5

GitHub Actions `uses:` reference is not pinned to a 40-character commit SHA. Tags (`@v4`) and branches (`@main`) are mutable — a compromised maintainer or a tag rewrite can substitute malicious code into your CI pipeline silently. Pin to a SHA: `uses: actions/checkout@8e5e7e5ab8b370d6c329ec480221332ada57f0ab`. For readability, include the version as a trailing comment: `# v4.1.1`. Tools like `pinact` / `ratchet` automate this. Allowed unpinned forms (excluded by the rule): - Local actions `.

Evidence

uses: actions/checkout@93cb6efe18208431cddfb8368fd83d5badbf9bfd # v5.0.1
      - name: Generate metadata file
        id: generate-metadata-file
        uses: hashicorp/actions-generate-metadata@v1
        with:
          version: ${{ needs.set-product-version.outputs.product-version }}
          product: ${{ env.PKG_NAME }}

Remediation

Pin every `uses:` to a 40-character commit SHA. Trailing comment with the version helps reviewers: `uses: actions/checkout@8e5e7e5ab8b370d6c329ec480221332ada57f0ab # v4.1.1` Automate the migration with `pinact` (https://github.com/suzuki-shunsuke/pinact) or `ratchet` (https://github.com/sethvargo/ratchet). Add a `pinact run --check` pre-commit hook so future PRs stay pinned. Re-pin when the action releases a new version — Dependabot can do this automatically with `version-update-strategy: inc

Report false positive →

AIVSS 2.3CVSS 3.5

Evidence

- uses: actions/checkout@93cb6efe18208431cddfb8368fd83d5badbf9bfd # v5.0.1
      - name: Set Product version
        id: set-product-version
        uses: hashicorp/actions-set-product-version@v2

  generate-metadata-file:
    needs: set-product-version

Remediation

Report false positive →

AIVSS 2.3CVSS 3.5

Evidence

steps:
      - uses: actions/checkout@93cb6efe18208431cddfb8368fd83d5badbf9bfd # v5.0.1

      - uses: hashicorp/actions-go-build@v1
        env:
          BASE_VERSION: ${{ needs.set-product-version.outputs.product-base-version }}
          PRERELEASE_VERSION: ${{ needs.set-product-version.outputs.product-prerelease-version}}

Remediation

Report false positive →

AIVSS 2.3CVSS 3.5

Evidence

steps:
      - uses: actions/checkout@93cb6efe18208431cddfb8368fd83d5badbf9bfd # v5.0.1
      - name: Docker Build (Action)
        uses: hashicorp/actions-docker-build@v2
        with:
        #   # Add smoke test here. Below is a sample smoke test that runs the built image
        #   # and validates the version.

Remediation

Report false positive →

LLM summary— terraform-mcp-server:HEAD

This package scores 94/100 on safety with a B security grade, but has 5 medium-severity issues split between an insecure container image and four server configuration problems that should be addressed before production use. The AIVSS score of 3.2/10 indicates moderate security concerns, primarily around how the server is configured and containerized rather than code vulnerabilities. You should review and remediate the container security and configuration issues before deploying this package in a production environment.

Signal scores

Static100

CVE check100

Publisher identity90

Permissions100

Supply chain60

Typosquat100

Package health85

Community82

Secrets & exfil100

Injection risks100

Destructive ops100

LLM judge panel

CVE check

No known CVEs found for this package or its dependencies.

Community trust

No community reports

Security policy: Not found
Advisories: 0

Scan details

Total findings: 5
Affected tools: 0 / 1
Scan type: Fast Scan
Rules run: 45
LLM consensus score: N/A
Scanned: 10d ago
Source: GITHUB

MCP Server Information

Source: GITHUB
Package: terraform-mcp-server
Version: HEAD
License: MPL-2.0
Publisher: hashicorp
Verified: Yes
Account age: 15y 0m
Added: 1y 0m ago
Versions: 1353
Repository: https://github.com/hashicorp/terraform-mcp-server
Ecosystem: GitHub
Stars: 1.4K
Forks: 153
Open issues: 40
Dependencies: 0

AIVSS Score

3.2/ 10Low

Internal score: 94/100

Severity breakdown

Scan Details

Total findings5

Affected tools0 / 1

Scanned10d ago

Scan modeFAST

SourceGITHUB

Scan IDpubfast055308984f960faa7d2e

Want deeper analysis?

Fast scan found 5 findings using rule-based analysis. Upgrade for LLM consensus across 5 judges, AI-generated remediation, and cross-file taint analysis.

View plans Scan another package

Building your own MCP server?

Run this exact engine on your private repo — before users see it on /scan.

Same rules, same LLM judges, same grade. Private scans stay isolated to your account and never appear in the public registry. Required for code your team hasn’t shipped yet.

See plans with Private scans How private scans stay private

5 of 5 findings

medium (5)

5 findings

medium (5)

AIVSS 3.2CVSS 4.4

Evidence

# Copyright IBM Corp. 2025
# SPDX-License-Identifier: MPL-2.0

# This Dockerfile contains multiple targets.
# Use 'docker build --target=<name> .' to build one.

# ===================================
#
#   Non-release images.
#
# ===================================

# certbuild captures the ca-certificates
FROM docker.mirror.hashicorp.services/alpine:3.22@sha256:4b7ce07002c69e8f3d704a9c5d6fd3053be500b7f1c69fc0d80990c2ad8dd412 AS certbuild
RUN apk add --no-cache ca-certificates

# devbuild compil

Remediation

Report false positive →

AIVSS 2.3CVSS 3.5

Evidence

uses: actions/checkout@93cb6efe18208431cddfb8368fd83d5badbf9bfd # v5.0.1
      - name: Generate metadata file
        id: generate-metadata-file
        uses: hashicorp/actions-generate-metadata@v1
        with:
          version: ${{ needs.set-product-version.outputs.product-version }}
          product: ${{ env.PKG_NAME }}

Remediation

Report false positive →

AIVSS 2.3CVSS 3.5

Evidence

- uses: actions/checkout@93cb6efe18208431cddfb8368fd83d5badbf9bfd # v5.0.1
      - name: Set Product version
        id: set-product-version
        uses: hashicorp/actions-set-product-version@v2

  generate-metadata-file:
    needs: set-product-version

Remediation

Report false positive →

AIVSS 2.3CVSS 3.5

Evidence

steps:
      - uses: actions/checkout@93cb6efe18208431cddfb8368fd83d5badbf9bfd # v5.0.1

      - uses: hashicorp/actions-go-build@v1
        env:
          BASE_VERSION: ${{ needs.set-product-version.outputs.product-base-version }}
          PRERELEASE_VERSION: ${{ needs.set-product-version.outputs.product-prerelease-version}}

Remediation

Report false positive →

AIVSS 2.3CVSS 3.5

Evidence

steps:
      - uses: actions/checkout@93cb6efe18208431cddfb8368fd83d5badbf9bfd # v5.0.1
      - name: Docker Build (Action)
        uses: hashicorp/actions-docker-build@v2
        with:
        #   # Add smoke test here. Below is a sample smoke test that runs the built image
        #   # and validates the version.

Remediation

Report false positive →

116	steps:
117	- uses: actions/checkout@93cb6efe18208431cddfb8368fd83d5badbf9bfd # v5.0.1
118
119	- uses: hashicorp/actions-go-build@v1
120	env:
121	BASE_VERSION: ${{ needs.set-product-version.outputs.product-base-version }}
122	PRERELEASE_VERSION: ${{ needs.set-product-version.outputs.product-prerelease-version}}

116	steps:
117	- uses: actions/checkout@93cb6efe18208431cddfb8368fd83d5badbf9bfd # v5.0.1
118
119	- uses: hashicorp/actions-go-build@v1
120	env:
121	BASE_VERSION: ${{ needs.set-product-version.outputs.product-base-version }}
122	PRERELEASE_VERSION: ${{ needs.set-product-version.outputs.product-prerelease-version}}

1	# Copyright IBM Corp. 2025
2	# SPDX-License-Identifier: MPL-2.0
3
4	# This Dockerfile contains multiple targets.
5	# Use 'docker build --target=<name> .' to build one.
6
7	# ===================================
8	#
9	# Non-release images.
10	#
11	# ===================================
12
13	# certbuild captures the ca-certificates
14	FROM docker.mirror.hashicorp.services/alpine:3.22@sha256:4b7ce07002c69e8f3d704a9c5d6fd3053be500b7f1c69fc0d80990c2ad8dd412 AS certbuild
15	RUN apk add --no-cache ca-certificates
16
17	# devbuild compil

80	uses: actions/checkout@93cb6efe18208431cddfb8368fd83d5badbf9bfd # v5.0.1
81	- name: Generate metadata file
82	id: generate-metadata-file
83	uses: hashicorp/actions-generate-metadata@v1
84	with:
85	version: ${{ needs.set-product-version.outputs.product-version }}
86	product: ${{ env.PKG_NAME }}

68	- uses: actions/checkout@93cb6efe18208431cddfb8368fd83d5badbf9bfd # v5.0.1
69	- name: Set Product version
70	id: set-product-version
71	uses: hashicorp/actions-set-product-version@v2
72
73	generate-metadata-file:
74	needs: set-product-version

154	steps:
155	- uses: actions/checkout@93cb6efe18208431cddfb8368fd83d5badbf9bfd # v5.0.1
156	- name: Docker Build (Action)
157	uses: hashicorp/actions-docker-build@v2
158	with:
159	# # Add smoke test here. Below is a sample smoke test that runs the built image
160	# # and validates the version.