com.machineinbox/machine-inbox
REMOTE · MACHINEINBOX.COM
Task-scoped email inboxes for AI agents: read mail, extract verification codes, and reply.
Available components
Last scanned (3 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Communication
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. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 918 tokens (~83/item across 11 items; 11 tools + 0 resources), lean.Pass
- 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 Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 86% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 17 Sept 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 19 Aug 26 0
- Schema quality: 674 → 918 ▼ functional
- Tool coverage: 81% → 86% ▲ functional
- Stability: unverified → 0.03 ▲ functional
- New tool “delete_webhook” functional
- New tool “get_webhook” functional
- New tool “set_webhook” functional
- 18 Aug 26 0
First indexed and scored.
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 5 Nov 2026 · Probed https://machineinbox.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=machineinbox.com | CN=WE1,O=Google Trust Services,C=US | 14 Oct 2026 | 12 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | c28a9db6a3ab880b13074ffe26915684 |
| SANs: machineinbox.com, www.machineinbox.com, *.www.machineinbox.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of machineinbox.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| machineinbox.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| content-security-policy | default-src 'self'; script-src 'self'; style-src 'self'; img-src 'self' data:; connect-src 'self'; frame-ancestors 'none'; base-uri 'none'; form-action 'self' |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://machineinbox.com/mcp | Verified | 200 | |
| http (plaintext) | http://machineinbox.com/mcp | Inconclusive | 405 |
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 →
create_inbox ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | – | High-entropy key to bind the eventual paid retry to this request. |
No output schema declared.
No examples provided.
delete_inbox ~67
Delete an inbox: revokes the token and erases stored mail.
| Name | Type | Req | Description |
|---|---|---|---|
| inbox_id | string | yes | Inbox UUID. |
| token | string | – | Mailbox bearer token (mi_live_...) returned when the inbox was purchased. Optional when the MCP request itself carries Authorization: Bearer. |
No output schema declared.
No examples provided.
delete_webhook ~58
Remove the inbox webhook.
| Name | Type | Req | Description |
|---|---|---|---|
| inbox_id | string | yes | Inbox UUID. |
| token | string | – | Mailbox bearer token (mi_live_...) returned when the inbox was purchased. Optional when the MCP request itself carries Authorization: Bearer. |
No output schema declared.
No examples provided.
get_inbox ~68
Read an inbox: address, status, expiry, limits, and usage.
| Name | Type | Req | Description |
|---|---|---|---|
| inbox_id | string | yes | Inbox UUID. |
| token | string | – | Mailbox bearer token (mi_live_...) returned when the inbox was purchased. Optional when the MCP request itself carries Authorization: Bearer. |
No output schema declared.
No examples provided.
get_message ~74
Fetch one message with parsed text, HTML, and attachment download URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| inbox_id | string | yes | Inbox UUID. |
| message_id | string | yes | – |
| token | string | – | Mailbox bearer token (mi_live_...) returned when the inbox was purchased. Optional when the MCP request itself carries Authorization: Bearer. |
No output schema declared.
No examples provided.
get_service_info ~26
Read the Machine Inbox service instructions: pricing, payment rails, endpoints, and limits.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_verification_code ~91
Extract the newest one-time verification code or confirmation link from inbound mail. Ideal for signup and login flows.
| Name | Type | Req | Description |
|---|---|---|---|
| inbox_id | string | yes | 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. |
No output schema declared.
No examples provided.
get_webhook ~80
Read the inbox webhook state: URL, delivery counters, and whether it is disabled. The secret is only returned by set_webhook.
| Name | Type | Req | Description |
|---|---|---|---|
| inbox_id | string | yes | Inbox UUID. |
| token | string | – | Mailbox bearer token (mi_live_...) returned when the inbox was purchased. Optional when the MCP request itself carries Authorization: Bearer. |
No output schema declared.
No examples provided.
list_messages ~115
List messages in an inbox, newest first. Pass after=<newest createdAt seen> to poll for only new mail.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | ISO date-time; only messages created after this instant. |
| before | string | – | ISO date-time cursor for older mail. |
| inbox_id | string | yes | 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. |
No output schema declared.
No examples provided.
reply_to_message ~107
Send an included plain-text reply to the authenticated sender of an inbound message.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | New unique key for this reply; reuse only to retry the identical reply. |
| inbox_id | string | yes | Inbox UUID. |
| message_id | string | yes | – |
| text | string | yes | – |
| token | string | – | Mailbox bearer token (mi_live_...) returned when the inbox was purchased. Optional when the MCP request itself carries Authorization: Bearer. |
No output schema declared.
No examples provided.
set_webhook ~106
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.
| Name | Type | Req | Description |
|---|---|---|---|
| inbox_id | string | yes | 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 | yes | Public https URL that receives the signed POST. |
No output schema declared.
No examples provided.
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.
remote · machineinbox.com
claude mcp add --transport http com-machineinbox-machine-inbox 'https://machineinbox.com/mcp'
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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.