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

Intercom conversations, contacts, tags and articles as MCP tools.

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

## Components

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

## Channel facts

- Registry: `npm`
- Package: `@reneturcios/supportchat`
- 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 3 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 551 tokens (~45/item across 12 items; 12 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**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - 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.

**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/supportchat MCP server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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-05 (score 64, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-11-03 (score 64, +15)

- [security improvement] Malware scan: unverified → pass

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

First indexed and scored.

## MCP tools (12)

### `list_conversations` (~51 tokens)

List Intercom conversations.

Input parameters:

- `per_page` (number): Optional maximum number of conversations to return per page.
- `state` (string): Optional conversation state to filter by, passed as the state query parameter.

### `get_conversation` (~36 tokens)

Retrieve a single Intercom conversation by ID.

Input parameters:

- `conversation_id` (string, required): The unique identifier of the Intercom conversation to retrieve.

### `reply_to_conversation` (~73 tokens)

Reply to an Intercom conversation as an admin.

Input parameters:

- `admin_id` (string, required): The unique identifier of the admin sending the reply.
- `conversation_id` (string, required): The unique identifier of the Intercom conversation to reply to.
- `message` (string, required): The reply message text to send as the conversation body.

### `close_conversation` (~53 tokens)

Close an Intercom conversation as an admin.

Input parameters:

- `admin_id` (string, required): The unique identifier of the admin closing the conversation.
- `conversation_id` (string, required): The unique identifier of the Intercom conversation to close.

### `search_conversations` (~49 tokens)

Search Intercom conversations matching a query.

Input parameters:

- `per_page` (number): Optional maximum number of conversations to return per page.
- `query` (string, required): The search text to match against conversation bodies.

### `list_contacts` (~30 tokens)

List Intercom contacts.

Input parameters:

- `per_page` (number): Optional maximum number of contacts to return per page.

### `get_contact` (~35 tokens)

Retrieve a single Intercom contact by ID.

Input parameters:

- `contact_id` (string, required): The unique identifier of the Intercom contact to retrieve.

### `create_contact` (~63 tokens)

Create an Intercom contact.

Input parameters:

- `email` (string, required): The email address of the new contact.
- `name` (string): Optional display name of the new contact.
- `role` (string): Optional role of the new contact (defaults to 'user' when omitted).

### `update_contact` (~62 tokens)

Update an Intercom contact by ID.

Input parameters:

- `contact_id` (string, required): The unique identifier of the Intercom contact to update.
- `email` (string): Optional new email address for the contact.
- `name` (string): Optional new display name for the contact.

### `list_tags` (~13 tokens)

List Intercom tags.

### `tag_contact` (~54 tokens)

Tag an Intercom contact with a tag name.

Input parameters:

- `contact_id` (string, required): The unique identifier of the Intercom contact to tag.
- `tag_name` (string, required): The name of the tag to apply to the contact.

### `list_articles` (~32 tokens)

List Intercom help center articles.

Input parameters:

- `per_page` (number): Optional maximum number of articles to return per page.

## Diagnostics

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

## Score history

- 2026-11-05: 64
- 2026-11-04: 64
- 2026-11-03: 64
- 2026-11-02: 49

## Common questions

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

io.github.CloudCorpRecords/supportchat is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/supportchat. Intercom conversations, contacts, tags and articles as MCP tools. This page covers its npm package (@reneturcios/supportchat).

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

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

io.github.CloudCorpRecords/supportchat exposes 12 tools: list_conversations, get_conversation, reply_to_conversation, close_conversation, search_conversations, and 7 more. Their descriptions and schemas cost roughly 551 tokens of context every time the server is loaded.

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

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

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