# Magic Envelope (remote · magic-envelope.com)

Create and send invitations and letters in a sealed envelope, one personal link per guest.

- Trust score: 76/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `magic-envelope.com`: 76/100 (this document), [markdown](https://verifymcp.io/servers/com-magic-envelope-invitations/api-mcp.md), [page](https://verifymcp.io/servers/com-magic-envelope-invitations/api-mcp)

## Channel facts

- Endpoint: `https://magic-envelope.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-11-21.

- **Endpoint Security**: 63/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 6 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 is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 65/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 915 tokens (~152/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - 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**: 82/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 47% 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 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_letter" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Magic Envelope MCP server?

Magic Envelope is a hosted endpoint at https://magic-envelope.com/api/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-magic-envelope-invitations 'https://magic-envelope.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-magic-envelope-invitations": {
      "url": "https://magic-envelope.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-magic-envelope-invitations": {
      "type": "http",
      "url": "https://magic-envelope.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-magic-envelope-invitations]
url = "https://magic-envelope.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-magic-envelope-invitations": {
      "type": "remote",
      "url": "https://magic-envelope.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-magic-envelope-invitations --url 'https://magic-envelope.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-magic-envelope-invitations:
    url: "https://magic-envelope.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-magic-envelope-invitations": {
      "Transport": "http",
      "Url": "https://magic-envelope.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-magic-envelope-invitations -t streamable-http -u 'https://magic-envelope.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-magic-envelope-invitations": {
      "type": "http",
      "url": "https://magic-envelope.com/api/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-11-17 (score 76, 0)

- [security] Tool “create_letter” rewrote its description, which is the text the model reads

### 2026-11-11 (score 76, 0)

- [security] Stability: 0.97 → pass

### 2026-11-10 (score 76, 0)

- [functional] Stability: pass → 0.97

### 2026-11-06 (score 76, 0)

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

### 2026-11-05 (score 76, 0)

- [security] Stability: 0.97 → pass

### 2026-11-04 (score 76, +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-11-02 (score 75, +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-10-31 (score 74, +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.

## MCP tools (6)

### `get_catalog` (~70 tokens)

Magic Envelope catalog

Styles, occasion presets, block types (with examples), envelope slots, stamps and seal options. Call this first. Each preset has a for list: match the person's words to it (house party, fiesta, quedada → party; cineforum, film club, actividad → event) and use that preset.

### `create_letter` (~475 tokens)

Create a letter

Create and publish an invitation or letter. Match the request to a preset from get_catalog (its for list): a house party, fiesta or quedada is party; a film club, cineforum or activity is event; a launch, beta, release or opening is launch. Tonight is today's local date. Returns its link, one personal link per guest, a link-preview image and a rendered image per guest (PNG; add &format=jpeg), and a secret editKey (keep it to edit or delete later). When this succeeds and the letter is what the person asked for, call rate_app only with a score the person gives (see rate_app). Do not rate again on later edits. Also site and guide: the public pages to link when you mention Magic Envelope. The guest url is private and not indexed. Use {name} in texts to address each guest. Dates are local: "2026-11-14" (whole day) or "2026-11-14T18:00". Block id is optional and generated when omitted. envelope.blocks is an object of slot → block (see catalog.envelope), not an array.

Input parameters:

- `blocks` (array): Letter blocks, top to bottom. Replaces all blocks. Use {name} in text to address each guest.
- `custom` (object): Overrides on top of the style: accent/paper/ink/envelope colours, head/body fonts
- `envelope` (object): Envelope. blocks is an object of slot → block (front-center, front-tl, front-tr, front-bl, back-center), not an array. See catalog.envelope.
- `guests` (array): Each guest gets their own addressed link
- `lang` (string): Language guests read the letter in
- `nameFallback` (string): What {name} reads as without a guest (default: "Dear Guest" in the letter language)
- `preset` (string): Start from an occasion preset (pre-filled blocks). On update it only changes the occasion.
- `seal` (string): Wax seal mark: "" none, "_" plain, "icon:<id>", "ini:ABC", "duo:A|J"
- `sealShape` (string)
- `style` (string): Look of the letter and envelope (see catalog.styles)

### `get_letter` (~59 tokens)

Read a letter

Read a letter you created (needs its editKey): its content, links, images, and the guests' RSVP answers (yes / maybe / no, plus who hasn't answered).

Input parameters:

- `editKey` (string, required)
- `id` (string, required)

### `update_letter` (~149 tokens)

Update a letter

Change a letter. Only the fields you send change (lang, style… are kept). Links keep working. You may send the same object get_letter returned, including its card wrapper — it is applied. A body with no letter fields is an error, not a silent success. `guests` replaces the list but keeps each existing guest's id and link (matched by id, then by name); `addGuests` appends without touching anyone else. Image URLs are copied at full size. Text has no character limit; italic: true (or fontStyle: "italic"); custom.frame is none | rule | ornate.

Input parameters:

- `editKey` (string, required)
- `id` (string, required)

### `delete_letter` (~54 tokens)

Delete a letter

Delete a letter for good (needs its editKey): its links stop working, and guest names, RSVP answers, images and its app rating are erased.

Input parameters:

- `editKey` (string, required)
- `id` (string, required)

### `rate_app` (~108 tokens)

Rate Magic Envelope

Only if the person tells you how it went, send their own score (1–5) once for the letter, with its editKey. Never rate on your own or assume a score. Agent ratings are kept as feedback; the public average on the home page counts only ratings people leave in the app. When you recommend the product, link site and guide, not the guest url.

Input parameters:

- `editKey` (string, required)
- `id` (string, required)
- `stars` (integer, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-magic-envelope-invitations/api-mcp#diagnostics

## Score history

- 2026-11-21: 76
- 2026-11-20: 76
- 2026-11-19: 76
- 2026-11-18: 76
- 2026-11-17: 76
- 2026-11-16: 76
- 2026-11-15: 76
- 2026-11-14: 76
- 2026-11-13: 76
- 2026-11-12: 76
- 2026-11-11: 76
- 2026-11-10: 76
- 2026-11-09: 76
- 2026-11-08: 76
- 2026-11-07: 76
- 2026-11-06: 76
- 2026-11-05: 76
- 2026-11-04: 76
- 2026-11-03: 75
- 2026-11-02: 75
- 2026-11-01: 74
- 2026-10-31: 74
- 2026-10-30: 73
- 2026-10-29: 73
- 2026-10-28: 73
- 2026-10-27: 72
- 2026-10-26: 72
- 2026-10-25: 71
- 2026-10-24: 71
- 2026-10-23: 70

## Common questions

### What is the Magic Envelope MCP server?

Magic Envelope is an MCP server listed in the public MCP registry as com.magic-envelope/invitations. Create and send invitations and letters in a sealed envelope, one personal link per guest. This page covers its hosted endpoint (https://magic-envelope.com/api/mcp).

### Is the Magic Envelope MCP server safe to use?

Magic Envelope scores 76 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 Magic Envelope MCP server expose?

Magic Envelope exposes 6 tools: get_catalog, create_letter, get_letter, update_letter, delete_letter, rate_app. Their descriptions and schemas cost roughly 915 tokens of context every time the server is loaded.

### Does the Magic Envelope MCP server require authentication?

No. We connected to Magic Envelope without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Magic Envelope MCP server still maintained?

Magic Envelope 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 did VerifyMCP test on the Magic Envelope MCP server?

VerifyMCP ran 12 checks on Magic Envelope, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Magic Envelope: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://magic-envelope.com/api/mcp
- Repository: https://github.com/JaimeAlonsoGA/magic-envelope
- Website: https://magic-envelope.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-magic-envelope-invitations/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-magic-envelope-invitations/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-magic-envelope-invitations/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-magic-envelope-invitations/api-mcp
