hashicorp/terraform-mcp-server
Canonical URL: https://github.com/hashicorp/terraform-mcp-server · Fetched from: https://raw.githubusercontent.com/hashicorp/terraform-mcp-server/HEAD/README.md · Machine form: /v1/resource-scans/github-com-hashicorp-terraform-mcp-server-c68d6ca07e · Markdown
Latest receipt: 4 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: be2a5f10f99c5482c5a76d021241589da8dc31d0ae85d3e66faede9e9b51f062 · 32316 bytes · scanned 2026-10-27T12:22:56.889Z · scanner resource-scan-v1 · ledger entry 1590.
Analysis is static only: the bytes were read as text and were never executed, installed or run. Nothing was fetched from behind a login.
Checks (latest receipt)
Outbound network references — flag
The scanned bytes reference outbound network activity to these domains: app.terraform.io, bob.ibm.com, code.visualstudio.com, cursor.com, developer.hashicorp.com, docs.aws.amazon.com, docs.claude.com, github.com, ide.company.com, img.shields.io, insiders.vscode.dev, kiro.dev, learn.chatgpt.com, modelcontextprotocol.io, tfe.company.com, vscode.dev, www.docker.com, www.hashicorp.com. Any resource that reaches the network can send data out as well as bring data in; the findings name what the bytes reference, and the reader decides whether that fits the resource's stated purpose.
Evidence: domain: app.terraform.io; domain: bob.ibm.com; domain: code.visualstudio.com; domain: cursor.com; domain: developer.hashicorp.com; domain: docs.aws.amazon.com; domain: docs.claude.com; domain: github.com; domain: ide.company.com; domain: img.shields.io; domain: insiders.vscode.dev; domain: kiro.dev; domain: learn.chatgpt.com; domain: modelcontextprotocol.io; domain: tfe.company.com; domain: vscode.dev; domain: www.docker.com; domain: www.hashicorp.com
Credential and environment access — flag
The scanned bytes contain credential or environment access patterns: secret-named variables (API_KEY, SECRET, TOKEN, PASSWORD and similar names); credential file paths (.env, .ssh, credential stores); authorization headers and bearer values. The receipt names the pattern kinds only; no credential value is reproduced here.
Evidence: secret-named variables (API_KEY, SECRET, TOKEN, PASSWORD and similar names); credential file paths (.env, .ssh, credential stores); authorization headers and bearer values
Install and postinstall hooks — pass
No install or postinstall hooks were found in the scanned bytes.
Obfuscation and encoded payloads — pass
No obfuscation or encoded-payload signs were found in the scanned bytes.
Shell-outs and download-and-execute — flag
The scanned bytes contain shell-out or download patterns: shell command tools named in the bytes (curl, wget, powershell). Code that runs shell commands acts with the full permissions of whoever runs it.
Evidence: shell command tools named in the bytes (curl, wget, powershell)
Permission declarations vs behavior — flag
The bytes show network, credentials behavior, and no permissions declaration was found in the scanned bytes to compare it against.
Evidence: behavior: network; behavior: credentials
Known-bad indicators — pass
None of the scanner's published known-bad indicator patterns matched the scanned bytes.
Provenance facts (weak signals) — pass
Provenance facts, labeled weak signals — they say where the bytes sit, not what the bytes do: source host: github.com; repository: hashicorp/terraform-mcp-server; bytes scanned: 32316; fetched from: https://raw.githubusercontent.com/hashicorp/terraform-mcp-server/HEAD/README.md.
Evidence: source host: github.com; repository: hashicorp/terraform-mcp-server; bytes scanned: 32316; fetched from: https://raw.githubusercontent.com/hashicorp/terraform-mcp-server/HEAD/README.md
History
Every receipt for this artifact so far names the same SHA-256: the bytes have not changed between scans.
- 2026-10-27 — 4 of 8 checks flagged · SHA-256 be2a5f10f99c5482… · 32316 bytes · scanner resource-scan-v1 · ledger entry 1590
