# agent-intercom (npm · agent-intercom)

Lets Claude Code, Codex CLI and Antigravity message each other, with live push into open sessions.

- Trust score: 88/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- npm · `agent-intercom`: 88/100 (this document), [markdown](https://verifymcp.io/servers/iambashar-agent-intercom/agent-intercom.md), [page](https://verifymcp.io/servers/iambashar-agent-intercom/agent-intercom)

## Channel facts

- Registry: `npm`
- Package: `agent-intercom`
- Version: `0.2.5`
- 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-04.

- **Supply Chain Security**: 100/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.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to iambashar/agent-intercom).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 16 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 552 tokens (~184/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - 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.

## Install

### How do I install the agent-intercom MCP server?

agent-intercom runs locally as an npm package, launched with npx -y agent-intercom. 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 iambashar-agent-intercom -- npx -y agent-intercom
```

### Cursor

```json
{
  "mcpServers": {
    "iambashar-agent-intercom": {
      "command": "npx",
      "args": [
        "-y",
        "agent-intercom"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "iambashar-agent-intercom": {
      "command": "npx",
      "args": [
        "-y",
        "agent-intercom"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add iambashar-agent-intercom -- npx -y agent-intercom
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add iambashar-agent-intercom --command npx --arg -y --arg agent-intercom
```

### Hermes

```yaml
mcp_servers:
  iambashar-agent-intercom:
    command: "npx"
    args: ["-y", "agent-intercom"]
```

### Netclaw

```json
{
  "McpServers": {
    "iambashar-agent-intercom": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "agent-intercom"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add iambashar-agent-intercom -t stdio -c npx -a -y agent-intercom
```

### Other

```json
{
  "mcpServers": {
    "iambashar-agent-intercom": {
      "command": "npx",
      "args": [
        "-y",
        "agent-intercom"
      ]
    }
  }
}
```

## 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-04 (score 88, +1)

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

### 2026-11-02 (score 87, +1)

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

### 2026-10-30 (score 86, +1)

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

### 2026-10-28 (score 85, +1)

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

### 2026-10-26 (score 84, +1)

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

### 2026-10-24 (score 83, +1)

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

### 2026-10-22 (score 82, +1)

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

### 2026-10-20 (score 81, +1)

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

## MCP tools (3)

### `mail_send` (~236 tokens)

Send a message to another agent

Deliver a text message from you ("claude") to another coding agent's inbox, for example to hand off a task, ask a question or report a result. Call mail_peers first if you are unsure of the recipient name. To answer a message you received from mail_check, pass its id as reply_to. Each call writes one new message and never edits or removes existing mail. If the recipient has not started yet, the message waits in its inbox. Returns "sent <id> to <name>"; keep the id if you expect a reply that references it.

Input parameters:

- `body` (string, required): Message text, in plain text or Markdown. Include everything the recipient needs, since it cannot see your conversation.
- `reply_to` (string): Optional. The id of the message you are answering (the value in [brackets] from mail_check), so the recipient can match the reply to its question.
- `to` (string, required): Recipient agent name as listed by mail_peers, e.g. "codex", "claude" or "gemini". Letters, digits, _ and -, with optional .suffix segments.

### `mail_check` (~174 tokens)

Read new messages

Fetch the unread messages addressed to you ("claude"), oldest first. Use it when you expect a reply or want to see if another agent wrote to you. Reading consumes the messages: each one is moved to your read folder and is not returned again, so act on or note what you need. With wait_seconds above 0 the call blocks until at least one message arrives or the time runs out. Returns each message as "[<id>] from <sender> (re <id>) at <time>:" followed by its body, or "no new messages". When live push is installed, new mail may already appear in your session without calling this tool.

Input parameters:

- `wait_seconds` (number): How long to wait for a message if the inbox is empty, in seconds (0 to 300). 0 returns immediately.

### `mail_peers` (~100 tokens)

List agents on the mailbox

List every agent name that has a mailbox here, so you know valid recipients for mail_send. Read-only: it changes nothing. Returns one line per agent: "<name> - last started <ISO time>", or "never started" for an agent that has mail waiting but has not run yet. Your own name is marked "(you)". A recent start time suggests the agent is active, but it does not guarantee a session is open right now.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/iambashar-agent-intercom/agent-intercom#diagnostics

## Score history

- 2026-11-04: 88
- 2026-11-03: 87
- 2026-11-02: 87
- 2026-11-01: 86
- 2026-10-31: 86
- 2026-10-30: 86
- 2026-10-29: 85
- 2026-10-28: 85
- 2026-10-27: 84
- 2026-10-26: 84
- 2026-10-25: 83
- 2026-10-24: 83
- 2026-10-23: 82
- 2026-10-22: 82
- 2026-10-21: 81
- 2026-10-20: 81
- 2026-10-19: 80

## Common questions

### What is the agent-intercom MCP server?

agent-intercom is an MCP server listed in the public MCP registry as io.github.iambashar/agent-intercom. Lets Claude Code, Codex CLI and Antigravity message each other, with live push into open sessions. This page covers its npm package (agent-intercom).

### Is the agent-intercom MCP server safe to use?

agent-intercom scores 88 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 agent-intercom MCP server expose?

agent-intercom exposes 3 tools: mail_send, mail_check, mail_peers. Their descriptions and schemas cost roughly 510 tokens of context every time the server is loaded.

### Is the agent-intercom MCP server still maintained?

agent-intercom is still listed as active in the MCP registry. We last reached this channel on 4 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 agent-intercom MCP server under?

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