io.github.CloudCorpRecords/infraport
NPM · @RENETURCIOS/INFRAPORT · 2 COMPONENTS
Terraform Registry modules, providers and policies, plus HCP Terraform workspaces.
Available components
Last scanned (22 hours ago)
Scores higher than 34% of npm 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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
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 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 619 tokens (~61/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 Management10
- Stability observed for 3 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
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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 65
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 4 Nov 2026 · Analysed npm/@reneturcios/infraport@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 | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
get_latest_module_version ~64
Get the latest published version of a registry module.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Name of the module in the Terraform Registry. |
| namespace | string | yes | Namespace of the module in the Terraform Registry. |
| provider | string | yes | Name of the provider the module targets. |
No output schema declared.
No examples provided.
get_latest_provider_version ~55
Get the latest published version of a registry provider.
| Name | Type | Req | Description |
|---|---|---|---|
| namespace | string | yes | Namespace of the provider in the Terraform Registry. |
| type | string | yes | Provider type, the short name that identifies the provider within its namespace. |
No output schema declared.
No examples provided.
get_module_details ~91
Fetch details for one registry module by namespace, name, and provider.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Name of the module in the Terraform Registry. |
| namespace | string | yes | Namespace of the module in the Terraform Registry. |
| provider | string | yes | Name of the provider the module targets. |
| version | string | – | Optional specific module version to fetch; when omitted, details for the latest version are returned. |
No output schema declared.
No examples provided.
get_policy_details ~53
Fetch details for one registry policy set by namespace and name.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Name of the policy set in the Terraform Registry. |
| namespace | string | yes | Namespace of the policy set in the Terraform Registry. |
No output schema declared.
No examples provided.
get_provider_details ~79
Fetch details for one registry provider by namespace and type.
| Name | Type | Req | Description |
|---|---|---|---|
| namespace | string | yes | Namespace of the provider in the Terraform Registry. |
| type | string | yes | 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. |
No output schema declared.
No examples provided.
get_workspace ~59
Fetch one HCP Terraform workspace by organization and workspace name. Requires TFE_TOKEN.
| Name | Type | Req | Description |
|---|---|---|---|
| organization | string | yes | Name of the HCP Terraform organization that owns the workspace. |
| workspace | string | yes | Name of the HCP Terraform workspace to fetch. |
No output schema declared.
No examples provided.
list_workspaces ~44
List HCP Terraform workspaces in an organization. Requires TFE_TOKEN.
| Name | Type | Req | Description |
|---|---|---|---|
| organization | string | yes | Name of the HCP Terraform organization whose workspaces should be listed. |
No output schema declared.
No examples provided.
search_modules ~69
Search the Terraform Registry for modules matching a query.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Search text used to find modules in the Terraform Registry. |
No output schema declared.
No examples provided.
search_policies ~54
Search the Terraform Registry for Sentinel policies matching a query.
| Name | Type | Req | Description |
|---|---|---|---|
| offset | number | – | Optional pagination offset for the policy search results. |
| query | string | yes | Search text used to find Sentinel policy sets in the Terraform Registry. |
No output schema declared.
No examples provided.
search_providers ~51
Search the Terraform Registry for providers matching a query.
| Name | Type | Req | Description |
|---|---|---|---|
| offset | number | – | Optional pagination offset for the provider search results. |
| query | string | yes | Search text used to find providers in the Terraform Registry. |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/infraport MCP server?
io.github.CloudCorpRecords/infraport runs locally as an npm package, launched with npx -y @reneturcios/infraport. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @reneturcios/infraport
claude mcp add cloudcorprecords-infraport -- npx -y @reneturcios/infraport
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 npm package (@reneturcios/infraport).
Is the io.github.CloudCorpRecords/infraport MCP server safe to use?
io.github.CloudCorpRecords/infraport scores 66 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 November 2026. It declares no install or post-install scripts. 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 4 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.