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

Sandboxed file access: read, write, edit and search in allowed dirs.

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

## Components

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

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/cloudcorprecords/fileport`
- 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 8 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 718 tokens (~51/item across 14 items; 14 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 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 14 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 14 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/fileport MCP server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### Hermes

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

### Netclaw

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

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-fileport": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/fileport: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-05 (score 44, +1)

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

### 2026-11-03 (score 43, +1)

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

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

### 2026-10-27 (score 40)

First indexed and scored.

## MCP tools (14)

### `read_file` (~38 tokens)

Read the full contents of a file as text.

Input parameters:

- `path` (string, required): Path of the file to read, inside one of the allowed directories.

### `read_text_file` (~86 tokens)

Read a text file, optionally limited to its first or last lines.

Input parameters:

- `head` (number): Return only the first N lines of the file; mutually exclusive with tail.
- `path` (string, required): Path of the text file to read, inside one of the allowed directories.
- `tail` (number): Return only the last N lines of the file; mutually exclusive with head.

### `read_media_file` (~42 tokens)

Read a media file and return it as base64 content.

Input parameters:

- `path` (string, required): Path of the media file to read, inside one of the allowed directories.

### `read_multiple_files` (~43 tokens)

Read several files at once, reporting per-file failures in-band.

Input parameters:

- `paths` (array, required): Paths of the files to read, each inside one of the allowed directories.

### `write_file` (~55 tokens)

Write text content to a file, creating parent folders as needed.

Input parameters:

- `content` (string, required): Text content to write to the file.
- `path` (string, required): Path of the file to write, inside one of the allowed directories.

### `edit_file` (~84 tokens)

Apply exact-match text replacements to a file, with an optional dry run.

Input parameters:

- `dryRun` (boolean): When true, report the changes that would be made without writing the file.
- `edits` (array, required): Exact-match text replacements to apply to the file, in order.
- `path` (string, required): Path of the file to edit, inside one of the allowed directories.

### `create_directory` (~37 tokens)

Create a directory, including any missing parents.

Input parameters:

- `path` (string, required): Path of the directory to create, inside one of the allowed directories.

### `list_directory` (~35 tokens)

List the entries of a directory.

Input parameters:

- `path` (string, required): Path of the directory to list, inside one of the allowed directories.

### `list_directory_with_sizes` (~54 tokens)

List directory entries together with their sizes.

Input parameters:

- `path` (string, required): Path of the directory to list, inside one of the allowed directories.
- `sortBy` (string): Sort the entries by name or by size.

### `directory_tree` (~57 tokens)

Return a directory as a nested JSON tree.

Input parameters:

- `excludePatterns` (array): Glob patterns for paths to exclude from the tree.
- `path` (string, required): Path of the directory to return as a tree, inside one of the allowed directories.

### `move_file` (~60 tokens)

Move or rename a file or directory.

Input parameters:

- `destination` (string, required): New path for the file or directory, inside one of the allowed directories.
- `source` (string, required): Current path of the file or directory to move, inside one of the allowed directories.

### `search_files` (~68 tokens)

Recursively search for files whose names match a glob pattern.

Input parameters:

- `excludePatterns` (array): Glob patterns for paths to exclude from the search.
- `path` (string, required): Directory to search recursively, inside one of the allowed directories.
- `pattern` (string, required): Glob pattern matched against file names.

### `get_file_info` (~39 tokens)

Return metadata about a file or directory.

Input parameters:

- `path` (string, required): Path of the file or directory to inspect, inside one of the allowed directories.

### `list_allowed_directories` (~20 tokens)

List the directories this server is allowed to access.

## Diagnostics

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

## Score history

- 2026-11-05: 44
- 2026-11-04: 43
- 2026-11-03: 43
- 2026-11-02: 42
- 2026-11-01: 42
- 2026-10-31: 41
- 2026-10-30: 41
- 2026-10-29: 41
- 2026-10-28: 40
- 2026-10-27: 40

## Common questions

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

io.github.CloudCorpRecords/fileport is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/fileport. Sandboxed file access: read, write, edit and search in allowed dirs. This page covers its container image (ghcr.io/cloudcorprecords/fileport).

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

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

io.github.CloudCorpRecords/fileport exposes 14 tools: read_file, read_text_file, read_media_file, read_multiple_files, write_file, and 9 more. Their descriptions and schemas cost roughly 718 tokens of context every time the server is loaded.

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

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

io.github.CloudCorpRecords/fileport 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/cloudcorprecords/fileport
- Repository: https://github.com/CloudCorpRecords/fileport
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-fileport/ghcr-io-cloudcorprecords-fileport.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-fileport/ghcr-io-cloudcorprecords-fileport.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-fileport/ghcr-io-cloudcorprecords-fileport