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.

Magic Envelope

REMOTE · MAGIC-ENVELOPE.COM

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

0 this week 76 Trust /100

Last scanned (20 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Communication

Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability65
  • AI-judged instruction clarity (good).Pass
  • 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. 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 Coverage82
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 47% 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 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. See how to fix → Fail
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation 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.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

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.

  • 17 Nov 26 0
    • Tool “create_letter” rewrote its description, which is the text the model reads security
  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 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
  • 5 Nov 26 0
    • Stability: 0.97 → pass security
  • 4 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.

  • 2 Nov 26 +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.

  • 31 Oct 26 +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.

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 · Probed https://magic-envelope.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=magic-envelope.com CN=YR2,O=Let's Encrypt,C=US 5 Oct 2026 3 Jan 2027 RSA 2048 SHA256-RSA 64cb3121aeae93f11a242c968423a55deac
SANs: magic-envelope.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of magic-envelope.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
magic-envelope.com. No DS 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
strict-transport-security max-age=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://magic-envelope.com/api/mcp Verified 200
http (plaintext) http://magic-envelope.com/api/mcp HTTPS enforced 308 https://magic-envelope.com/api/mcp
MCP tools · 6 exposed · ~915 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
create_letter ~475

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.

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

No output schema declared.

No examples provided.

delete_letter ~54

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

NameTypeReqDescription
editKeystringyes–
idstringyes–

No output schema declared.

No examples provided.

get_catalog ~70

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_letter ~59

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).

NameTypeReqDescription
editKeystringyes–
idstringyes–

No output schema declared.

No examples provided.

rate_app ~108

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.

NameTypeReqDescription
editKeystringyes–
idstringyes–
starsintegeryes–

No output schema declared.

No examples provided.

update_letter ~149

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.

NameTypeReqDescription
editKeystringyes–
idstringyes–

No output schema declared.

No examples provided.

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.

remote · magic-envelope.com

# add to Claude Code
claude mcp add --transport http com-magic-envelope-invitations 'https://magic-envelope.com/api/mcp'
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.