# co.instantreply/mcp (npm · @instantreply.co/mcp)

AI access to InstantReply WhatsApp, Instagram, and Messenger inboxes with browser pairing.

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

## Components

- remote · `api.instantreply.co`: 38/100, [markdown](https://verifymcp.io/servers/co-instantreply-mcp/api.md), [page](https://verifymcp.io/servers/co-instantreply-mcp/api)
- npm · `@instantreply.co/mcp`: 67/100 (this document), [markdown](https://verifymcp.io/servers/co-instantreply-mcp/instantreply-co-mcp.md), [page](https://verifymcp.io/servers/co-instantreply-mcp/instantreply-co-mcp)

## Channel facts

- Registry: `npm`
- Package: `@instantreply.co/mcp`
- Version: `0.2.2`
- 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-09-28.

- **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.
  - 31 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 88/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 334 tokens (~111/item across 3 items; 3 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 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 co.instantreply/mcp server?

co.instantreply/mcp runs locally as an npm package, launched with npx -y @instantreply.co/mcp. 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 co-instantreply-mcp -- npx -y @instantreply.co/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "co-instantreply-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@instantreply.co/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "co-instantreply-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@instantreply.co/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add co-instantreply-mcp -- npx -y @instantreply.co/mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add co-instantreply-mcp --command npx --arg -y --arg @instantreply.co/mcp
```

### Hermes

```yaml
mcp_servers:
  co-instantreply-mcp:
    command: "npx"
    args: ["-y", "@instantreply.co/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "co-instantreply-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@instantreply.co/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add co-instantreply-mcp -t stdio -c npx -a -y @instantreply.co/mcp
```

### Other

```json
{
  "mcpServers": {
    "co-instantreply-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@instantreply.co/mcp"
      ]
    }
  }
}
```

## 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-09-28 (score 67, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-26 (score 67)

First indexed and scored.

## MCP tools (3)

### `get_connection_guide` (~76 tokens)

Get how to connect each channel (Instagram, WhatsApp, Messenger, Telegram, Shopify, calendars): where the user clicks, what Meta requires first, and how long it really takes. Call this before advising anyone which channel to set up — Instagram works same-day, WhatsApp needs 2-6 weeks of Meta Business Verification.

### `start_setup` (~183 tokens)

Start connecting this AI agent to InstantReply. Call this first if no other tools are available. Returns a short code and a link — tell the user to open the link, sign up or log in (takes under a minute), and approve the code. Then call check_setup.

Input parameters:

- `persona` (string): Who the user is, if you know it: creator (personal brand / Instagram DMs), business (sells products or services, has a website or WhatsApp), developer (building it into their own product), agency (ru…
- `platform` (string): Which channel the user wants to connect. Instagram needs no Meta review and works same-day; WhatsApp needs Meta Business Verification, which takes 2-6 weeks, so prefer instagram unless the user speci…

### `check_setup` (~75 tokens)

Check whether the user has approved the setup link from start_setup, and wait a short while if not. Once approved, the AI agent has a live InstantReply connection — tell the user to restart or reconnect this MCP server so the rest of the tools load.

Input parameters:

- `device_code` (string, required): The device_code returned by start_setup

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/co-instantreply-mcp/instantreply-co-mcp#diagnostics

## Score history

- 2026-09-28: 67
- 2026-09-27: 67
- 2026-09-26: 67

## Common questions

### What is the co.instantreply/mcp server?

co.instantreply/mcp is listed in the public MCP registry as co.instantreply/mcp. AI access to InstantReply WhatsApp, Instagram, and Messenger inboxes with browser pairing. This page covers its npm package (@instantreply.co/mcp).

### Is the co.instantreply/mcp server safe to use?

co.instantreply/mcp scores 67 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 28 September 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 co.instantreply/mcp server expose?

co.instantreply/mcp exposes 3 tools: get_connection_guide, start_setup, check_setup. Their descriptions and schemas cost roughly 334 tokens of context every time the server is loaded.

### Is the co.instantreply/mcp server still maintained?

co.instantreply/mcp is still listed as active in the MCP registry. We last reached this channel on 28 September 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 co.instantreply/mcp server under?

co.instantreply/mcp 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/@instantreply.co/mcp
- Socket report: https://socket.dev/npm/package/@instantreply.co/mcp
- Website: https://www.instantreply.co/mcp
- Changelog RSS feed: https://verifymcp.io/servers/co-instantreply-mcp/instantreply-co-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/co-instantreply-mcp/instantreply-co-mcp.json
- HTML version of this page: https://verifymcp.io/servers/co-instantreply-mcp/instantreply-co-mcp