# io.github.CloudCorpRecords/infraport (oci · ghcr.io/cloudcorprecords/infraport)

Terraform Registry modules, providers and policies, plus HCP Terraform workspaces.

- Trust score: 42/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@reneturcios/infraport`: 67/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-infraport/reneturcios-infraport.md), [page](https://verifymcp.io/servers/cloudcorprecords-infraport/reneturcios-infraport)
- oci · `ghcr.io/cloudcorprecords/infraport`: 42/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-infraport/ghcr-io-cloudcorprecords-infraport.md), [page](https://verifymcp.io/servers/cloudcorprecords-infraport/ghcr-io-cloudcorprecords-infraport)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/cloudcorprecords/infraport`
- 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 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 619 tokens (~61/item across 10 items; 10 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 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 io.github.CloudCorpRecords/infraport MCP server?

io.github.CloudCorpRecords/infraport runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/infraport:0.1.0 mcp. 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 cloudcorprecords-infraport -- docker run --rm -i ghcr.io/cloudcorprecords/infraport:0.1.0 mcp
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-infraport": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/infraport:0.1.0",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-infraport": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/infraport:0.1.0",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-infraport -- docker run --rm -i ghcr.io/cloudcorprecords/infraport:0.1.0 mcp
```

### opencode

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

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-infraport:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/cloudcorprecords/infraport:0.1.0", "mcp"]
```

### Netclaw

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

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-infraport": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/infraport:0.1.0",
        "mcp"
      ]
    }
  }
}
```

## 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 42, +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-11-01 (score 41)

First indexed and scored.

## MCP tools (10)

### `search_modules` (~69 tokens)

Search the Terraform Registry for modules matching a query.

Input parameters:

- `offset` (number): Optional pagination offset for the module search results.
- `provider` (string): Optional provider name to filter the module search results to one provider.
- `query` (string, required): Search text used to find modules in the Terraform Registry.

### `get_module_details` (~91 tokens)

Fetch details for one registry module by namespace, name, and provider.

Input parameters:

- `name` (string, required): Name of the module in the Terraform Registry.
- `namespace` (string, required): Namespace of the module in the Terraform Registry.
- `provider` (string, required): Name of the provider the module targets.
- `version` (string): Optional specific module version to fetch; when omitted, details for the latest version are returned.

### `get_latest_module_version` (~64 tokens)

Get the latest published version of a registry module.

Input parameters:

- `name` (string, required): Name of the module in the Terraform Registry.
- `namespace` (string, required): Namespace of the module in the Terraform Registry.
- `provider` (string, required): Name of the provider the module targets.

### `search_providers` (~51 tokens)

Search the Terraform Registry for providers matching a query.

Input parameters:

- `offset` (number): Optional pagination offset for the provider search results.
- `query` (string, required): Search text used to find providers in the Terraform Registry.

### `get_provider_details` (~79 tokens)

Fetch details for one registry provider by namespace and type.

Input parameters:

- `namespace` (string, required): Namespace of the provider in the Terraform Registry.
- `type` (string, required): Provider type, the short name that identifies the provider within its namespace.
- `version` (string): Optional specific provider version to fetch; when omitted, details for the latest version are returned.

### `get_latest_provider_version` (~55 tokens)

Get the latest published version of a registry provider.

Input parameters:

- `namespace` (string, required): Namespace of the provider in the Terraform Registry.
- `type` (string, required): Provider type, the short name that identifies the provider within its namespace.

### `search_policies` (~54 tokens)

Search the Terraform Registry for Sentinel policies matching a query.

Input parameters:

- `offset` (number): Optional pagination offset for the policy search results.
- `query` (string, required): Search text used to find Sentinel policy sets in the Terraform Registry.

### `get_policy_details` (~53 tokens)

Fetch details for one registry policy set by namespace and name.

Input parameters:

- `name` (string, required): Name of the policy set in the Terraform Registry.
- `namespace` (string, required): Namespace of the policy set in the Terraform Registry.

### `list_workspaces` (~44 tokens)

List HCP Terraform workspaces in an organization. Requires TFE_TOKEN.

Input parameters:

- `organization` (string, required): Name of the HCP Terraform organization whose workspaces should be listed.

### `get_workspace` (~59 tokens)

Fetch one HCP Terraform workspace by organization and workspace name. Requires TFE_TOKEN.

Input parameters:

- `organization` (string, required): Name of the HCP Terraform organization that owns the workspace.
- `workspace` (string, required): Name of the HCP Terraform workspace to fetch.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-infraport/ghcr-io-cloudcorprecords-infraport#diagnostics

## Score history

- 2026-11-05: 42
- 2026-11-04: 42
- 2026-11-03: 41
- 2026-11-02: 41
- 2026-11-01: 41

## Common questions

### What is the io.github.CloudCorpRecords/infraport MCP server?

io.github.CloudCorpRecords/infraport is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/infraport. Terraform Registry modules, providers and policies, plus HCP Terraform workspaces. This page covers its container image (ghcr.io/cloudcorprecords/infraport).

### Is the io.github.CloudCorpRecords/infraport MCP server safe to use?

io.github.CloudCorpRecords/infraport scores 42 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 io.github.CloudCorpRecords/infraport MCP server expose?

io.github.CloudCorpRecords/infraport exposes 10 tools: search_modules, get_module_details, get_latest_module_version, search_providers, get_provider_details, and 5 more. Their descriptions and schemas cost roughly 619 tokens of context every time the server is loaded.

### Is the io.github.CloudCorpRecords/infraport MCP server still maintained?

io.github.CloudCorpRecords/infraport 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 io.github.CloudCorpRecords/infraport MCP server under?

io.github.CloudCorpRecords/infraport declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the io.github.CloudCorpRecords/infraport MCP server?

VerifyMCP ran 12 checks on io.github.CloudCorpRecords/infraport, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about io.github.CloudCorpRecords/infraport: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- GitHub Container Registry: https://ghcr.io/cloudcorprecords/infraport
- Repository: https://github.com/CloudCorpRecords/infraport
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-infraport/ghcr-io-cloudcorprecords-infraport.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-infraport/ghcr-io-cloudcorprecords-infraport/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/cloudcorprecords-infraport/ghcr-io-cloudcorprecords-infraport.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-infraport/ghcr-io-cloudcorprecords-infraport
