io.github.CloudCorpRecords/cloudinfra
OCI · GHCR.IO/CLOUDCORPRECORDS/CLOUDINFRA · 2 COMPONENTS
Terraform Registry docs, module search and AWS plan policy scans as MCP tools.
Available components
Last scanned (3 hours ago)
Scores higher than 54% of OCI servers
Category CI/CD and DevOps
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. How we score → Why this is hard to score →
Supply Chain Security0
- 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.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 499 tokens (~49/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 1 Nov 26 40
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed oci/ghcr.io/cloudcorprecords/cloudinfra@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
explain_resource ~40
Explain a common AWS Terraform resource type in plain language.
| Name | Type | Req | Description |
|---|---|---|---|
| resource_type | string | yes | Terraform resource type to explain, for example 'aws_s3_bucket'. |
No output schema declared.
No examples provided.
get_latest_provider_version ~59
Get the latest published version of a Terraform provider.
| Name | Type | Req | Description |
|---|---|---|---|
| namespace | string | yes | Registry namespace that publishes the provider, for example 'hashicorp'. |
| type | string | yes | Provider type (name) within the namespace, for example 'aws'. |
No output schema declared.
No examples provided.
get_module_details ~39
Get details for one Terraform Registry module.
| Name | Type | Req | Description |
|---|---|---|---|
| module_id | string | yes | Full Registry module identifier in namespace/name/provider format identifying the module to fetch. |
No output schema declared.
No examples provided.
get_provider_doc_details ~82
Get details for one Terraform provider from the Registry.
| Name | Type | Req | Description |
|---|---|---|---|
| namespace | string | yes | Registry namespace that publishes the provider, for example 'hashicorp'. |
| type | string | yes | Provider type (name) within the namespace, for example 'aws'. |
| version | string | – | Optional specific provider version to fetch details for; omit to get the current release details. |
No output schema declared.
No examples provided.
list_provider_resources ~57
List the documented resources for a Terraform provider.
| Name | Type | Req | Description |
|---|---|---|---|
| namespace | string | yes | Registry namespace that publishes the provider, for example 'hashicorp'. |
| type | string | yes | Provider type (name) within the namespace, for example 'aws'. |
No output schema declared.
No examples provided.
run_policy_scan ~48
Run deterministic policy checks over a Terraform plan JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| plan | object | yes | Terraform plan JSON object to scan, as produced by 'terraform show -json', using planned_values or resource_changes. |
No output schema declared.
No examples provided.
search_cc_provider_docs ~36
Search AWS Cloud Control provider documentation topics.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search text to match against AWS Cloud Control provider documentation topics. |
No output schema declared.
No examples provided.
search_modules ~47
Search Terraform Registry modules.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Optional maximum number of module search results to return. |
| query | string | yes | Search text to match against Terraform Registry module names and descriptions. |
No output schema declared.
No examples provided.
search_provider_docs ~49
Search Terraform provider documentation topics.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | – | Optional provider name to restrict the documentation search to one provider. |
| query | string | yes | Search text to match against Terraform provider documentation topics. |
No output schema declared.
No examples provided.
search_user_guide ~42
Search Terraform user guide and AWS IaC guidance topics.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search text to match against Terraform user guide and AWS IaC guidance topics. |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/cloudinfra MCP server?
io.github.CloudCorpRecords/cloudinfra runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/cloudinfra: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.
oci · ghcr.io/cloudcorprecords/cloudinfra
claude mcp add cloudcorprecords-cloudinfra -- docker run --rm -i ghcr.io/cloudcorprecords/cloudinfra:0.1.0
What is the io.github.CloudCorpRecords/cloudinfra MCP server?
io.github.CloudCorpRecords/cloudinfra is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/cloudinfra. Terraform Registry docs, module search and AWS plan policy scans as MCP tools. This page covers its container image (ghcr.io/cloudcorprecords/cloudinfra).
Is the io.github.CloudCorpRecords/cloudinfra MCP server safe to use?
io.github.CloudCorpRecords/cloudinfra 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/cloudinfra MCP server expose?
io.github.CloudCorpRecords/cloudinfra exposes 10 tools: search_provider_docs, get_provider_doc_details, search_cc_provider_docs, list_provider_resources, search_modules, and 5 more. Their descriptions and schemas cost roughly 499 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/cloudinfra MCP server still maintained?
io.github.CloudCorpRecords/cloudinfra 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/cloudinfra MCP server under?
io.github.CloudCorpRecords/cloudinfra declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.