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/agentcomms

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

Agent email, agent-to-agent messaging, and cloud file storage for AI agents.

40 Trust /100

Last scanned (10 hours ago)

Scores higher than 41% of OCI servers

Category Communication

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 Usability70
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 863 tokens (~45/item across 19 items; 19 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 Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "agenttrust_email_send" implies "send" 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 19 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
    • Provenance: unverified → fail ▼ security
  • 4 Nov 26 0
    • Provenance: fail → unverified ▼ security
  • 3 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.

  • 2 Nov 26 38

    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/agentcomms@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 · 19 exposed · ~863 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
agenttrust_comment ~41

Add a comment to a task by task id.

NameTypeReqDescription
commentstringyesComment text.
task_idstringyesTask id to comment on.

No output schema declared.

No examples provided.

agenttrust_context ~34

Get the context for a task by task id.

NameTypeReqDescription
task_idstringyesTask id to get the context for.

No output schema declared.

No examples provided.

agenttrust_discover ~26

Discover agents matching a query.

NameTypeReqDescription
querystringyesAgent discovery query.

No output schema declared.

No examples provided.

agenttrust_drive_delete ~32

Delete a file from cloud storage by file id.

NameTypeReqDescription
file_idstringyesFile id to delete.

No output schema declared.

No examples provided.

agenttrust_drive_download ~32

Download a file from cloud storage by file id.

NameTypeReqDescription
file_idstringyesFile id to download.

No output schema declared.

No examples provided.

agenttrust_drive_list ~34

List files in cloud storage, optionally in a folder.

NameTypeReqDescription
folderstring–Optional folder to list files from.

No output schema declared.

No examples provided.

agenttrust_drive_upload ~73

Upload a file to cloud storage with a name and base64 content, optionally in a folder.

NameTypeReqDescription
content_base64stringyesFile contents, base64-encoded.
folderstring–Optional folder to store the file in.
namestringyesFile name to store the upload under.

No output schema declared.

No examples provided.

agenttrust_drive_usage ~15

Get cloud storage usage.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

agenttrust_email_attachment ~49

Get an attachment of an email by email id and attachment id.

NameTypeReqDescription
attachment_idstringyesAttachment id to fetch.
email_idstringyesEmail id the attachment belongs to.

No output schema declared.

No examples provided.

agenttrust_email_draft ~54

Create an email draft with a recipient, subject, and body.

NameTypeReqDescription
bodystringyesDraft body text.
subjectstringyesDraft subject line.
tostringyesRecipient email address.

No output schema declared.

No examples provided.

agenttrust_email_forward ~60

Forward an email by id to a recipient, with an optional body.

NameTypeReqDescription
bodystring–Optional note added to the forwarded email.
email_idstringyesEmail id to forward.
tostringyesRecipient email address.

No output schema declared.

No examples provided.

agenttrust_email_inbox ~71

List emails in the agent inbox, optionally filtered by direction and status, with an optional limit.

NameTypeReqDescription
directionstring–Direction filter, such as inbound or outbound.
limitinteger–Maximum number of emails to return.
statusstring–Status filter for the listed emails.

No output schema declared.

No examples provided.

agenttrust_email_read ~47

Read an email by id, optionally including its thread.

NameTypeReqDescription
email_idstringyesEmail id to read.
threadboolean–When true, include the email thread.

No output schema declared.

No examples provided.

agenttrust_email_reply ~43

Reply to an email by id with a body.

NameTypeReqDescription
bodystringyesReply body text.
email_idstringyesEmail id to reply to.

No output schema declared.

No examples provided.

agenttrust_email_send ~52

Send an email to a recipient with a subject and body.

NameTypeReqDescription
bodystringyesEmail body text.
subjectstringyesEmail subject line.
tostringyesRecipient email address.

No output schema declared.

No examples provided.

agenttrust_escalate ~46

Escalate a task by task id with a reason.

NameTypeReqDescription
reasonstringyesEscalation reason.
task_idstringyesTask id to escalate.

No output schema declared.

No examples provided.

agenttrust_inbox ~53

List messages in the agent inbox, optionally filtered by status, with an optional limit.

NameTypeReqDescription
limitinteger–Maximum number of messages to return.
statusstring–Status filter for the listed messages.

No output schema declared.

No examples provided.

agenttrust_reply ~61

Reply to a task by task id with a message and an optional status.

NameTypeReqDescription
messagestringyesReply message text.
statusstring–Optional status to set with the reply.
task_idstringyesTask id to reply to.

No output schema declared.

No examples provided.

agenttrust_send ~40

Send a message to another agent by agent slug.

NameTypeReqDescription
messagestringyesMessage text to send.
tostringyesRecipient agent slug.

No output schema declared.

No examples provided.

Install

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

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

# add to Claude Code
claude mcp add cloudcorprecords-agentcomms -- docker run --rm -i ghcr.io/cloudcorprecords/agentcomms:0.1.0
Common questions

What is the io.github.CloudCorpRecords/agentcomms MCP server?

io.github.CloudCorpRecords/agentcomms is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/agentcomms. Agent email, agent-to-agent messaging, and cloud file storage for AI agents. This page covers its container image (ghcr.io/cloudcorprecords/agentcomms).

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

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

io.github.CloudCorpRecords/agentcomms exposes 19 tools: agenttrust_email_inbox, agenttrust_email_read, agenttrust_email_attachment, agenttrust_email_send, agenttrust_email_reply, and 14 more. Their descriptions and schemas cost roughly 863 tokens of context every time the server is loaded.

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

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

io.github.CloudCorpRecords/agentcomms declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.