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

WhatsApp messaging via a GoWA REST service: send text, contacts, links, and locations.

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

## Components

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

## Channel facts

- Registry: `npm`
- Package: `@reneturcios/chatport`
- 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**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 92 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 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 188 tokens (~47/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "whatsapp_send_text" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 4 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/chatport MCP server?

io.github.CloudCorpRecords/chatport runs locally as an npm package, launched with npx -y @reneturcios/chatport. 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-chatport -- npx -y @reneturcios/chatport
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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-03 (score 67, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-02 (score 52)

First indexed and scored.

## MCP tools (4)

### `whatsapp_send_text` (~34 tokens)

Send text messages

Input parameters:

- `message` (string, required): Text message to send.
- `phone` (string, required): Recipient phone number.

### `whatsapp_send_contact` (~52 tokens)

Send contact cards

Input parameters:

- `contact_name` (string, required): Name of the contact to send.
- `contact_phone` (string, required): Phone number of the contact to send.
- `phone` (string, required): Recipient phone number.

### `whatsapp_send_link` (~47 tokens)

Send links with captions

Input parameters:

- `caption` (string): Optional caption for the link.
- `link` (string, required): Link URL to send.
- `phone` (string, required): Recipient phone number.

### `whatsapp_send_location` (~55 tokens)

Send location coordinates

Input parameters:

- `latitude` (number, required): Latitude coordinate, between -90 and 90.
- `longitude` (number, required): Longitude coordinate, between -180 and 180.
- `phone` (string, required): Recipient phone number.

## Diagnostics

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

## Score history

- 2026-11-05: 67
- 2026-11-04: 67
- 2026-11-03: 67
- 2026-11-02: 52

## Common questions

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

io.github.CloudCorpRecords/chatport is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/chatport. WhatsApp messaging via a GoWA REST service: send text, contacts, links, and locations. This page covers its npm package (@reneturcios/chatport).

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

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

io.github.CloudCorpRecords/chatport exposes 4 tools: whatsapp_send_text, whatsapp_send_contact, whatsapp_send_link, whatsapp_send_location. Their descriptions and schemas cost roughly 188 tokens of context every time the server is loaded.

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

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

io.github.CloudCorpRecords/chatport 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/chatport
- Socket report: https://socket.dev/npm/package/@reneturcios/chatport
- Repository: https://github.com/CloudCorpRecords/chatport
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-chatport/reneturcios-chatport.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-chatport/reneturcios-chatport.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-chatport/reneturcios-chatport