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.

co.instantreply/mcp

NPM · @INSTANTREPLY.CO/MCP · 2 COMPONENTS

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

0 this week 79 Trust /100

Last scanned (14 hours ago)

Scores higher than 63% of npm 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 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
  • 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
Schema Quality & AI Usability79
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 679 tokens (~226/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 19 Nov 26 0
    • Stability: 0.97 → pass security
  • 18 Nov 26 0
    • Stability: pass → 0.97 functional
  • 12 Nov 26 0
    • Stability: 0.97 → pass security
  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Nov 26 −1
    • Stability: pass → 0.87 functional
  • 4 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 3 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 2 Nov 26 0
    • Stability: 0.97 → pass security
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 21 Nov 2026 · Analysed npm/@instantreply.co/mcp@0.8.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 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~357 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
check_setup ~75

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.

NameTypeReqDescription
device_codestringyesThe device_code returned by start_setup

No output schema declared.

No examples provided.

get_connection_guide ~76

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

start_setup ~206

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), connect their Instagram, WhatsApp or Messenger there, and approve the code. Then call check_setup. Never ask the user to paste a key or token into chat.

NameTypeReqDescription
personastring–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…
platformstring–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…

No output schema declared.

No examples provided.

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.

npm · @instantreply.co/mcp

# add to Claude Code
claude mcp add co-instantreply-mcp -- npx -y @instantreply.co/mcp
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 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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 co.instantreply/mcp server expose?

co.instantreply/mcp exposes 3 tools: get_connection_guide, start_setup, check_setup. Their descriptions and schemas cost roughly 357 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 21 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 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.

What did VerifyMCP test on the co.instantreply/mcp server?

VerifyMCP ran 16 checks on co.instantreply/mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.