# com.machineinbox/machine-inbox (remote · machineinbox.com)

Task-scoped email inboxes for AI agents: read mail, extract verification codes, and reply.

- Trust score: 71/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `machineinbox.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/com-machineinbox-machine-inbox/machineinbox.md), [page](https://verifymcp.io/servers/com-machineinbox-machine-inbox/machineinbox)

## Channel facts

- Endpoint: `https://machineinbox.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-20.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 11 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 918 tokens (~83/item across 11 items; 11 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 86% 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 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "reply_to_message" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the com.machineinbox/machine-inbox MCP server?

com.machineinbox/machine-inbox is a hosted endpoint at https://machineinbox.com/mcp, so there is nothing to install locally. 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 --transport http com-machineinbox-machine-inbox 'https://machineinbox.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-machineinbox-machine-inbox": {
      "url": "https://machineinbox.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-machineinbox-machine-inbox": {
      "type": "http",
      "url": "https://machineinbox.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-machineinbox-machine-inbox]
url = "https://machineinbox.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-machineinbox-machine-inbox": {
      "type": "remote",
      "url": "https://machineinbox.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-machineinbox-machine-inbox --url 'https://machineinbox.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-machineinbox-machine-inbox:
    url: "https://machineinbox.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-machineinbox-machine-inbox": {
      "Transport": "http",
      "Url": "https://machineinbox.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-machineinbox-machine-inbox -t streamable-http -u 'https://machineinbox.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-machineinbox-machine-inbox": {
      "type": "http",
      "url": "https://machineinbox.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-17 (score 71, 0)

- [security] Stability: 0.97 → pass

### 2026-09-16 (score 71, +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.

### 2026-09-14 (score 70, +1)

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

### 2026-09-12 (score 69, +1)

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

### 2026-09-10 (score 68, +1)

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

### 2026-09-08 (score 67, +1)

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

### 2026-09-06 (score 66, +1)

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

### 2026-09-04 (score 65, +1)

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

## MCP tools (11)

### `get_service_info` (~26 tokens)

Read the Machine Inbox service instructions: pricing, payment rails, endpoints, and limits.

### `create_inbox` (~83 tokens)

Request a new paid inbox. Buying requires an out-of-band payment (Stripe MPP or x402 USDC on Base); this tool returns the live HTTP 402 payment challenge plus exact instructions to complete the purchase. Standard inbox: $2.00.

Input parameters:

- `idempotency_key` (string): High-entropy key to bind the eventual paid retry to this request.

### `get_inbox` (~68 tokens)

Read an inbox: address, status, expiry, limits, and usage.

Input parameters:

- `inbox_id` (string, required): Inbox UUID.
- `token` (string): Mailbox bearer token (mi_live_...) returned when the inbox was purchased. Optional when the MCP request itself carries Authorization: Bearer.

### `list_messages` (~115 tokens)

List messages in an inbox, newest first. Pass after=<newest createdAt seen> to poll for only new mail.

Input parameters:

- `after` (string): ISO date-time; only messages created after this instant.
- `before` (string): ISO date-time cursor for older mail.
- `inbox_id` (string, required): Inbox UUID.
- `limit` (integer)
- `token` (string): Mailbox bearer token (mi_live_...) returned when the inbox was purchased. Optional when the MCP request itself carries Authorization: Bearer.

### `get_message` (~74 tokens)

Fetch one message with parsed text, HTML, and attachment download URLs.

Input parameters:

- `inbox_id` (string, required): Inbox UUID.
- `message_id` (string, required)
- `token` (string): Mailbox bearer token (mi_live_...) returned when the inbox was purchased. Optional when the MCP request itself carries Authorization: Bearer.

### `get_verification_code` (~91 tokens)

Extract the newest one-time verification code or confirmation link from inbound mail. Ideal for signup and login flows.

Input parameters:

- `inbox_id` (string, required): Inbox UUID.
- `sender` (string): Only consider senders whose address contains this substring.
- `token` (string): Mailbox bearer token (mi_live_...) returned when the inbox was purchased. Optional when the MCP request itself carries Authorization: Bearer.

### `reply_to_message` (~107 tokens)

Send an included plain-text reply to the authenticated sender of an inbound message.

Input parameters:

- `idempotency_key` (string, required): New unique key for this reply; reuse only to retry the identical reply.
- `inbox_id` (string, required): Inbox UUID.
- `message_id` (string, required)
- `text` (string, required)
- `token` (string): Mailbox bearer token (mi_live_...) returned when the inbox was purchased. Optional when the MCP request itself carries Authorization: Bearer.

### `set_webhook` (~106 tokens)

Register or replace the inbox webhook: an HMAC-signed POST fires on every inbound message with metadata, extracted verification codes, and injection risk (never the body). Returns the signing secret.

Input parameters:

- `inbox_id` (string, required): Inbox UUID.
- `token` (string): Mailbox bearer token (mi_live_...) returned when the inbox was purchased. Optional when the MCP request itself carries Authorization: Bearer.
- `url` (string, required): Public https URL that receives the signed POST.

### `get_webhook` (~80 tokens)

Read the inbox webhook state: URL, delivery counters, and whether it is disabled. The secret is only returned by set_webhook.

Input parameters:

- `inbox_id` (string, required): Inbox UUID.
- `token` (string): Mailbox bearer token (mi_live_...) returned when the inbox was purchased. Optional when the MCP request itself carries Authorization: Bearer.

### `delete_webhook` (~58 tokens)

Remove the inbox webhook.

Input parameters:

- `inbox_id` (string, required): Inbox UUID.
- `token` (string): Mailbox bearer token (mi_live_...) returned when the inbox was purchased. Optional when the MCP request itself carries Authorization: Bearer.

### `delete_inbox` (~67 tokens)

Delete an inbox: revokes the token and erases stored mail.

Input parameters:

- `inbox_id` (string, required): Inbox UUID.
- `token` (string): Mailbox bearer token (mi_live_...) returned when the inbox was purchased. Optional when the MCP request itself carries Authorization: Bearer.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-machineinbox-machine-inbox/machineinbox#diagnostics

## Score history

- 2026-09-20: 71
- 2026-09-19: 71
- 2026-09-18: 71
- 2026-09-17: 71
- 2026-09-16: 71
- 2026-09-15: 70
- 2026-09-14: 70
- 2026-09-13: 69
- 2026-09-12: 69
- 2026-09-11: 68
- 2026-09-10: 68
- 2026-09-09: 67
- 2026-09-08: 67
- 2026-09-07: 66
- 2026-09-06: 66
- 2026-09-05: 65
- 2026-09-04: 65
- 2026-09-03: 64
- 2026-09-02: 64
- 2026-09-01: 64
- 2026-08-31: 63
- 2026-08-30: 63
- 2026-08-29: 62
- 2026-08-28: 62
- 2026-08-27: 61
- 2026-08-26: 61
- 2026-08-25: 60
- 2026-08-24: 60
- 2026-08-23: 59
- 2026-08-22: 58

## Common questions

### What is the com.machineinbox/machine-inbox MCP server?

com.machineinbox/machine-inbox is an MCP server listed in the public MCP registry as com.machineinbox/machine-inbox. Task-scoped email inboxes for AI agents: read mail, extract verification codes, and reply. This page covers its hosted endpoint (https://machineinbox.com/mcp).

### Is the com.machineinbox/machine-inbox MCP server safe to use?

com.machineinbox/machine-inbox scores 71 out of 100 on VerifyMCP. 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 com.machineinbox/machine-inbox MCP server expose?

com.machineinbox/machine-inbox exposes 11 tools: get_service_info, create_inbox, get_inbox, list_messages, get_message, and 6 more. Their descriptions and schemas cost roughly 875 tokens of context every time the server is loaded.

### Does the com.machineinbox/machine-inbox MCP server require authentication?

No. We connected to com.machineinbox/machine-inbox without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the com.machineinbox/machine-inbox MCP server still maintained?

com.machineinbox/machine-inbox is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://machineinbox.com/mcp
- Website: https://machineinbox.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-machineinbox-machine-inbox/machineinbox.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-machineinbox-machine-inbox/machineinbox.json
- HTML version of this page: https://verifymcp.io/servers/com-machineinbox-machine-inbox/machineinbox