# io.github.CloudCorpRecords/edgeport (npm · @reneturcios/edgeport)

Zones, DNS, cache purge, Workers, KV, and R2 through the Cloudflare API.

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

## Components

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

## Channel facts

- Registry: `npm`
- Package: `@reneturcios/edgeport`
- 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**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 30 of 93 dependencies flagged as unhealthy.
- **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 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 960 tokens (~80/item across 12 items; 12 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**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_dns_record" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 12 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.

## Install

### How do I install the io.github.CloudCorpRecords/edgeport MCP server?

io.github.CloudCorpRecords/edgeport runs locally as an npm package, launched with npx -y @reneturcios/edgeport. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add cloudcorprecords-edgeport -- npx -y @reneturcios/edgeport
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-edgeport": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/edgeport"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-edgeport": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/edgeport"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-edgeport -- npx -y @reneturcios/edgeport
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-edgeport": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@reneturcios/edgeport"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cloudcorprecords-edgeport --command npx --arg -y --arg @reneturcios/edgeport
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-edgeport:
    command: "npx"
    args: ["-y", "@reneturcios/edgeport"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-edgeport": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@reneturcios/edgeport"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add cloudcorprecords-edgeport -t stdio -c npx -a -y @reneturcios/edgeport
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-edgeport": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/edgeport"
      ]
    }
  }
}
```

## 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 65, +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-02 (score 64, +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.

### 2026-11-01 (score 63)

First indexed and scored.

## MCP tools (12)

### `list_accounts` (~36 tokens)

List Cloudflare accounts accessible with the API token.

Input parameters:

- `per_page` (integer): Maximum number of accounts to return per page of results.

### `list_zones` (~80 tokens)

List zones, optionally filtered by account or name.

Input parameters:

- `account_id` (string): Cloudflare account identifier to restrict the zone list to zones in that account.
- `name` (string): Zone (domain) name to filter the zone list by exact name match.
- `per_page` (integer): Maximum number of zones to return per page of results.

### `get_zone` (~31 tokens)

Get one zone by its id.

Input parameters:

- `zone_id` (string, required): Identifier of the Cloudflare zone to retrieve.

### `list_dns_records` (~102 tokens)

List DNS records in a zone, optionally filtered by type or name.

Input parameters:

- `name` (string): DNS record name to filter records by.
- `per_page` (integer): Maximum number of DNS records to return per page of results.
- `type` (string): DNS record type (such as A, AAAA, CNAME, or MX) to filter records by.
- `zone_id` (string, required): Identifier of the zone whose DNS records should be listed.

### `create_dns_record` (~157 tokens)

Create a DNS record in a zone.

Input parameters:

- `comment` (string): Optional comment describing the DNS record.
- `content` (string, required): Content of the DNS record, such as an IP address or target hostname.
- `name` (string, required): Name of the DNS record, such as a hostname within the zone.
- `proxied` (boolean): Whether Cloudflare should proxy traffic through its network for this record.
- `ttl` (integer): Time to live in seconds for the DNS record, where 1 means automatic.
- `type` (string, required): DNS record type to create, such as A, AAAA, CNAME, or MX.
- `zone_id` (string, required): Identifier of the zone in which to create the DNS record.

### `update_dns_record` (~173 tokens)

Update a DNS record in a zone.

Input parameters:

- `comment` (string): New comment describing the DNS record.
- `content` (string): New content for the DNS record, such as an IP address or target hostname.
- `name` (string): New name for the DNS record, such as a hostname within the zone.
- `proxied` (boolean): Whether Cloudflare should proxy traffic through its network for this record.
- `record_id` (string, required): Identifier of the DNS record to update.
- `ttl` (integer): New time to live in seconds for the DNS record, where 1 means automatic.
- `type` (string): New DNS record type, such as A, AAAA, CNAME, or MX.
- `zone_id` (string, required): Identifier of the zone containing the DNS record to update.

### `delete_dns_record` (~50 tokens)

Delete a DNS record from a zone.

Input parameters:

- `record_id` (string, required): Identifier of the DNS record to delete.
- `zone_id` (string, required): Identifier of the zone containing the DNS record to delete.

### `purge_cache` (~116 tokens)

Purge cached content for a zone, by file, tag, host, or everything.

Input parameters:

- `files` (array): List of URLs whose cached content should be purged.
- `hosts` (array): List of hostnames whose cached content should be purged.
- `purge_everything` (boolean): Whether to purge all cached content for the zone.
- `tags` (array): List of cache tags whose associated cached content should be purged.
- `zone_id` (string, required): Identifier of the zone whose cache should be purged.

### `list_workers_scripts` (~47 tokens)

List Worker scripts in an account.

Input parameters:

- `account_id` (string): Identifier of the account whose Worker scripts should be listed, falling back to CLOUDFLARE_ACCOUNT_ID when omitted.

### `get_worker_script` (~67 tokens)

Get a Worker script's metadata and shape only, without its body.

Input parameters:

- `account_id` (string): Identifier of the account containing the Worker script, falling back to CLOUDFLARE_ACCOUNT_ID when omitted.
- `script_name` (string, required): Name of the Worker script to inspect.

### `list_kv_namespaces` (~50 tokens)

List Workers KV namespaces in an account.

Input parameters:

- `account_id` (string): Identifier of the account whose KV namespaces should be listed, falling back to CLOUDFLARE_ACCOUNT_ID when omitted.

### `list_r2_buckets` (~51 tokens)

List R2 buckets in an account.

Input parameters:

- `account_id` (string): Identifier of the account whose R2 buckets should be listed, falling back to CLOUDFLARE_ACCOUNT_ID when omitted.

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-edgeport/reneturcios-edgeport#diagnostics

## Score history

- 2026-11-05: 65
- 2026-11-04: 65
- 2026-11-03: 64
- 2026-11-02: 64
- 2026-11-01: 63

## Common questions

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

io.github.CloudCorpRecords/edgeport is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/edgeport. Zones, DNS, cache purge, Workers, KV, and R2 through the Cloudflare API. This page covers its npm package (@reneturcios/edgeport).

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

io.github.CloudCorpRecords/edgeport scores 65 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 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/edgeport MCP server expose?

io.github.CloudCorpRecords/edgeport exposes 12 tools: list_accounts, list_zones, get_zone, list_dns_records, create_dns_record, and 7 more. Their descriptions and schemas cost roughly 960 tokens of context every time the server is loaded.

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

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

io.github.CloudCorpRecords/edgeport 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

- npm package: https://www.npmjs.com/package/@reneturcios/edgeport
- Socket report: https://socket.dev/npm/package/@reneturcios/edgeport
- Repository: https://github.com/CloudCorpRecords/edgeport
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-edgeport/reneturcios-edgeport.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-edgeport/reneturcios-edgeport.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-edgeport/reneturcios-edgeport