# OpenTofu Test (oci · ghcr.io/ogormans-deptstack/opentofu-test-mcp)

MCP server for the OpenTofu/Terraform native test framework: scaffold, mock, validate, run tests

- Trust score: 49/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- oci · `ghcr.io/ogormans-deptstack/opentofu-test-mcp`: 49/100 (this document), [markdown](https://verifymcp.io/servers/ogormans-deptstack-opentofu-test/ghcr-io-ogormans-deptstack-opentofu-test-mcp.md), [page](https://verifymcp.io/servers/ogormans-deptstack-opentofu-test/ghcr-io-ogormans-deptstack-opentofu-test-mcp)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/ogormans-deptstack/opentofu-test-mcp`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 16 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 538 tokens (~107/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the OpenTofu Test MCP server?

OpenTofu Test runs locally as a container image, launched with docker run --rm -i ghcr.io/ogormans-deptstack/opentofu-test-mcp:0.1.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add ogormans-deptstack-opentofu-test -- docker run --rm -i ghcr.io/ogormans-deptstack/opentofu-test-mcp:0.1.0
```

### Cursor

```json
{
  "mcpServers": {
    "ogormans-deptstack-opentofu-test": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/ogormans-deptstack/opentofu-test-mcp:0.1.0"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ogormans-deptstack-opentofu-test": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/ogormans-deptstack/opentofu-test-mcp:0.1.0"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add ogormans-deptstack-opentofu-test -- docker run --rm -i ghcr.io/ogormans-deptstack/opentofu-test-mcp:0.1.0
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ogormans-deptstack-opentofu-test": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/ogormans-deptstack/opentofu-test-mcp:0.1.0"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  ogormans-deptstack-opentofu-test:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/ogormans-deptstack/opentofu-test-mcp:0.1.0"]
```

### Netclaw

```json
{
  "McpServers": {
    "ogormans-deptstack-opentofu-test": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/ogormans-deptstack/opentofu-test-mcp:0.1.0"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "ogormans-deptstack-opentofu-test": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/ogormans-deptstack/opentofu-test-mcp:0.1.0"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 49, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 48, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 47, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 46, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 45, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 44, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 43, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-20 (score 42, +1)

No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (5)

### `tf_explain_test_schema` (~110 tokens)

Explain the OpenTofu/Terraform native test framework grammar (.tftest.hcl / .tfmock.hcl). Call with an empty topic for an overview, or a topic like 'run', 'assert', 'mock_provider', 'expect_failures' for its block reference and an example.

Input parameters:

- `topic` (string): a test-framework topic such as run, assert, mock_provider, mock_resource, expect_failures, tftest, tfmock; empty returns an overview

Output parameters:

- `reference` (string)
- `topics` (null|array)

### `tf_gen_mock_provider` (~114 tokens)

Generate a mock_provider block for an initialized module directory by reading 'providers schema -json'. Pre-fills mock_resource defaults for computed attributes. The directory must have been initialized first.

Input parameters:

- `binary` (string): override the CLI binary (tofu or terraform, or an absolute path)
- `dir` (string, required): path to an initialized module directory
- `provider` (string): restrict output to this provider source or local name; empty emits all providers
- `resource` (string): restrict output to this resource type

Output parameters:

- `content` (string)

### `tf_run_tests` (~112 tokens)

Run 'tofu test -json' in a module directory and return a condensed pass/fail summary with per-run status. Optionally filter to a single test file. Requires the directory to be initialized.

Input parameters:

- `binary` (string): override the CLI binary (tofu or terraform, or an absolute path)
- `dir` (string, required): path to an initialized module directory containing tests
- `filter` (string): restrict the run to a single test file, e.g. tests/main.tftest.hcl

Output parameters:

- `errored` (integer)
- `failed` (integer)
- `passed` (integer)
- `problems` (null|array)
- `runs` (null|array)
- `skipped` (integer)

### `tf_scaffold_test` (~102 tokens)

Generate a .tftest.hcl starter test for a module directory by reading its input variables and outputs. Produces a run block with assertions for each output and placeholders for required variables.

Input parameters:

- `command` (string): the run command to use: plan (default) or apply
- `dir` (string, required): path to the module directory to scaffold a test for
- `mock` (boolean): also emit empty mock_provider blocks for the module's providers

Output parameters:

- `content` (string)
- `module` (null|object)

### `tf_validate_test` (~100 tokens)

Statically validate a .tftest.hcl file (by path or raw content) and report structural problems such as an invalid command, assert blocks missing condition/error_message, duplicate run names, or no run blocks. Does not run OpenTofu.

Input parameters:

- `content` (string): raw .tftest.hcl content to validate instead of a path
- `path` (string): path to a .tftest.hcl file to validate

Output parameters:

- `findings` (null|array)
- `runs` (integer)
- `valid` (boolean)

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/ogormans-deptstack-opentofu-test/ghcr-io-ogormans-deptstack-opentofu-test-mcp#diagnostics

## Score history

- 2026-11-05: 49
- 2026-11-04: 49
- 2026-11-03: 48
- 2026-11-02: 48
- 2026-11-01: 47
- 2026-10-31: 47
- 2026-10-30: 46
- 2026-10-29: 46
- 2026-10-28: 45
- 2026-10-27: 45
- 2026-10-26: 44
- 2026-10-25: 44
- 2026-10-24: 44
- 2026-10-23: 43
- 2026-10-22: 43
- 2026-10-21: 42
- 2026-10-20: 42
- 2026-10-19: 41

## Common questions

### What is the OpenTofu Test MCP server?

OpenTofu Test is an MCP server listed in the public MCP registry as io.github.ogormans-deptstack/opentofu-test. MCP server for the OpenTofu/Terraform native test framework: scaffold, mock, validate, run tests. This page covers its container image (ghcr.io/ogormans-deptstack/opentofu-test-mcp).

### Is the OpenTofu Test MCP server safe to use?

OpenTofu Test scores 49 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the OpenTofu Test MCP server expose?

OpenTofu Test exposes 5 tools: tf_explain_test_schema, tf_gen_mock_provider, tf_run_tests, tf_scaffold_test, tf_validate_test. Their descriptions and schemas cost roughly 538 tokens of context every time the server is loaded.

### Is the OpenTofu Test MCP server still maintained?

OpenTofu Test is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the OpenTofu Test MCP server under?

OpenTofu Test declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- GitHub Container Registry: https://ghcr.io/ogormans-deptstack/opentofu-test-mcp
- Repository: https://github.com/ogormans-deptstack/opentofu-test-mcp
- Changelog RSS feed: https://verifymcp.io/servers/ogormans-deptstack-opentofu-test/ghcr-io-ogormans-deptstack-opentofu-test-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ogormans-deptstack-opentofu-test/ghcr-io-ogormans-deptstack-opentofu-test-mcp.json
- HTML version of this page: https://verifymcp.io/servers/ogormans-deptstack-opentofu-test/ghcr-io-ogormans-deptstack-opentofu-test-mcp