Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.CloudCorpRecords/edgeport

OCI · GHCR.IO/CLOUDCORPRECORDS/EDGEPORT · 2 COMPONENTS

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

41 Trust /100

Last scanned (7 hours ago)

Scores higher than 46% of OCI servers

Category Cloud Infrastructure

Trust breakdown (7 categories)

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
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 960 tokens (~80/item across 12 items; 12 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 Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 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. See how to fix → Fail
  • An AI judge read all 12 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.

Changelog

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.

  • 5 Nov 26 +1

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

  • 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 39

    First indexed and scored.

Diagnostics

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/edgeport@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 →

MCP tools · 12 exposed · ~960 tokens

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 →

Tool Tokens
create_dns_record ~157

Create a DNS record in a zone.

NameTypeReqDescription
commentstring–Optional comment describing the DNS record.
contentstringyesContent of the DNS record, such as an IP address or target hostname.
namestringyesName of the DNS record, such as a hostname within the zone.
proxiedboolean–Whether Cloudflare should proxy traffic through its network for this record.
ttlinteger–Time to live in seconds for the DNS record, where 1 means automatic.
typestringyesDNS record type to create, such as A, AAAA, CNAME, or MX.
zone_idstringyesIdentifier of the zone in which to create the DNS record.

No output schema declared.

No examples provided.

delete_dns_record ~50

Delete a DNS record from a zone.

NameTypeReqDescription
record_idstringyesIdentifier of the DNS record to delete.
zone_idstringyesIdentifier of the zone containing the DNS record to delete.

No output schema declared.

No examples provided.

get_worker_script ~67

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

NameTypeReqDescription
account_idstring–Identifier of the account containing the Worker script, falling back to CLOUDFLARE_ACCOUNT_ID when omitted.
script_namestringyesName of the Worker script to inspect.

No output schema declared.

No examples provided.

get_zone ~31

Get one zone by its id.

NameTypeReqDescription
zone_idstringyesIdentifier of the Cloudflare zone to retrieve.

No output schema declared.

No examples provided.

list_accounts ~36

List Cloudflare accounts accessible with the API token.

NameTypeReqDescription
per_pageinteger–Maximum number of accounts to return per page of results.

No output schema declared.

No examples provided.

list_dns_records ~102

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

NameTypeReqDescription
namestring–DNS record name to filter records by.
per_pageinteger–Maximum number of DNS records to return per page of results.
typestring–DNS record type (such as A, AAAA, CNAME, or MX) to filter records by.
zone_idstringyesIdentifier of the zone whose DNS records should be listed.

No output schema declared.

No examples provided.

list_kv_namespaces ~50

List Workers KV namespaces in an account.

NameTypeReqDescription
account_idstring–Identifier of the account whose KV namespaces should be listed, falling back to CLOUDFLARE_ACCOUNT_ID when omitted.

No output schema declared.

No examples provided.

list_r2_buckets ~51

List R2 buckets in an account.

NameTypeReqDescription
account_idstring–Identifier of the account whose R2 buckets should be listed, falling back to CLOUDFLARE_ACCOUNT_ID when omitted.

No output schema declared.

No examples provided.

list_workers_scripts ~47

List Worker scripts in an account.

NameTypeReqDescription
account_idstring–Identifier of the account whose Worker scripts should be listed, falling back to CLOUDFLARE_ACCOUNT_ID when omitted.

No output schema declared.

No examples provided.

list_zones ~80

List zones, optionally filtered by account or name.

NameTypeReqDescription
account_idstring–Cloudflare account identifier to restrict the zone list to zones in that account.
namestring–Zone (domain) name to filter the zone list by exact name match.
per_pageinteger–Maximum number of zones to return per page of results.

No output schema declared.

No examples provided.

purge_cache ~116

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

NameTypeReqDescription
filesarray–List of URLs whose cached content should be purged.
hostsarray–List of hostnames whose cached content should be purged.
purge_everythingboolean–Whether to purge all cached content for the zone.
tagsarray–List of cache tags whose associated cached content should be purged.
zone_idstringyesIdentifier of the zone whose cache should be purged.

No output schema declared.

No examples provided.

update_dns_record ~173

Update a DNS record in a zone.

NameTypeReqDescription
commentstring–New comment describing the DNS record.
contentstring–New content for the DNS record, such as an IP address or target hostname.
namestring–New name for the DNS record, such as a hostname within the zone.
proxiedboolean–Whether Cloudflare should proxy traffic through its network for this record.
record_idstringyesIdentifier of the DNS record to update.
ttlinteger–New time to live in seconds for the DNS record, where 1 means automatic.
typestring–New DNS record type, such as A, AAAA, CNAME, or MX.
zone_idstringyesIdentifier of the zone containing the DNS record to update.

No output schema declared.

No examples provided.

Install

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

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

# add to Claude Code
claude mcp add cloudcorprecords-edgeport -- docker run --rm -i ghcr.io/cloudcorprecords/edgeport:0.1.0
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 container image (ghcr.io/cloudcorprecords/edgeport).

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

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