io.github.CloudCorpRecords/agentcomms
NPM · @RENETURCIOS/AGENTCOMMS · 2 COMPONENTS
Agent email, agent-to-agent messaging, and cloud file storage for AI agents.
Available components
Last scanned (6 hours ago)
Scores higher than 35% of npm servers
Category Communication
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 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 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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.
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 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 53
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 5 Nov 2026 · Analysed npm/@reneturcios/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 | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| 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 →
agenttrust_comment ~41
Add a comment to a task by task id.
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | yes | Comment text. |
| task_id | string | yes | Task id to comment on. |
No output schema declared.
No examples provided.
agenttrust_context ~34
Get the context for a task by task id.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | string | yes | Task id to get the context for. |
No output schema declared.
No examples provided.
agenttrust_discover ~26
Discover agents matching a query.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Agent discovery query. |
No output schema declared.
No examples provided.
agenttrust_drive_delete ~32
Delete a file from cloud storage by file id.
| Name | Type | Req | Description |
|---|---|---|---|
| file_id | string | yes | File id to delete. |
No output schema declared.
No examples provided.
agenttrust_drive_download ~32
Download a file from cloud storage by file id.
| Name | Type | Req | Description |
|---|---|---|---|
| file_id | string | yes | File id to download. |
No output schema declared.
No examples provided.
agenttrust_drive_list ~34
List files in cloud storage, optionally in a folder.
| Name | Type | Req | Description |
|---|---|---|---|
| folder | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| content_base64 | string | yes | File contents, base64-encoded. |
| folder | string | – | Optional folder to store the file in. |
| name | string | yes | File 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.
| Name | Type | Req | Description |
|---|---|---|---|
| attachment_id | string | yes | Attachment id to fetch. |
| email_id | string | yes | Email 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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Draft body text. |
| subject | string | yes | Draft subject line. |
| to | string | yes | Recipient 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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | Optional note added to the forwarded email. |
| email_id | string | yes | Email id to forward. |
| to | string | yes | Recipient 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.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Direction filter, such as inbound or outbound. |
| limit | integer | – | Maximum number of emails to return. |
| status | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| email_id | string | yes | Email id to read. |
| thread | boolean | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Reply body text. |
| email_id | string | yes | Email 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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Email body text. |
| subject | string | yes | Email subject line. |
| to | string | yes | Recipient email address. |
No output schema declared.
No examples provided.
agenttrust_escalate ~46
Escalate a task by task id with a reason.
| Name | Type | Req | Description |
|---|---|---|---|
| reason | string | yes | Escalation reason. |
| task_id | string | yes | Task 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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of messages to return. |
| status | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | Reply message text. |
| status | string | – | Optional status to set with the reply. |
| task_id | string | yes | Task id to reply to. |
No output schema declared.
No examples provided.
agenttrust_send ~40
Send a message to another agent by agent slug.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | Message text to send. |
| to | string | yes | Recipient agent slug. |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/agentcomms MCP server?
io.github.CloudCorpRecords/agentcomms runs locally as an npm package, launched with npx -y @reneturcios/agentcomms. 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/agentcomms
claude mcp add cloudcorprecords-agentcomms -- npx -y @reneturcios/agentcomms
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 npm package (@reneturcios/agentcomms).
Is the io.github.CloudCorpRecords/agentcomms MCP server safe to use?
io.github.CloudCorpRecords/agentcomms scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting 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/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.