Zovo Envelope Printer
REMOTE · ENVELOPE-PRINTER.ZOVO.ONE
Print envelopes with addresses at home.
Available components
Last scanned (21 hours ago)
Scores higher than 71% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Documents and Files
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability69
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1401 tokens (~467/item across 3 items; 2 tools + 1 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 Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
Checks we ran (14)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
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 →
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.
- 19 Nov 26 +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.
- 17 Nov 26 +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.
- 15 Nov 26 +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.
- 13 Nov 26 +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.
- 11 Nov 26 +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.
- 9 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 8 Nov 26 72
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 21 Nov 2026 · Probed https://envelope-printer.zovo.one/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zovo.one | CN=WE1,O=Google Trust Services,C=US | 3 Oct 2026 | 1 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 1a6be51dae225a780e14b5b59cd24fa3 |
| SANs: zovo.one, *.zovo.one | ||||||
| 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 envelope-printer.zovo.one. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| one. | DS published | 64939 | 8 | Verified |
| zovo.one. | 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=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://envelope-printer.zovo.one/mcp | Verified | 200 | |
| http (plaintext) | http://envelope-printer.zovo.one/mcp | HTTPS enforced | 301 | https://envelope-printer.zovo.one/mcp |
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 →
find_envelope_size Find envelope size ~241
Use this when the user asks what size envelope to use or how big an envelope is ("what size envelope for a 5x7 card", "#10 envelope size", "a7 envelope size", "envelope for a letter folded in thirds", "dl envelope size in inches"). Give a card, photo or folded sheet size and it lists the envelopes it fits with at least 1/8 in to spare, smallest first; give an envelope name and it returns its size in inches and mm, what it is used for and its USPS mail shape (letter, nonmachinable or large envelope). Does not print anything (use generate_envelope_pdf) and does not give postage prices.
| Name | Type | Req | Description |
|---|---|---|---|
| height | – | – | Height of the card or insert, e.g. 7. |
| query | – | – | A card or sheet size, an envelope name, or a use, e.g. "5x7 card", "letter folded in thirds", "A4 folded in half", "#10", "A7" or "wedding invitation". |
| width | – | – | Width of the card or insert, e.g. 5 or "127 mm". |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| insert | string|null | yes | – |
| matches | array | yes | – |
| query | string | yes | – |
No examples provided.
generate_envelope_pdf Print addresses on envelopes ~1,006
Use this when the user wants to print addresses on envelopes ("print envelopes with addresses", "print envelopes from excel", "#10 envelope template", "a7 envelope template", "address wedding invitation envelopes", "print address on envelope"). First convert any pasted text or image of addresses into recipients objects (name, address1, address2, city, state, zip, country). Makes a PDF with one page per envelope at the real envelope size (#10 default, #9, #6 3/4, Monarch, A2, A6, A7, A9, 6x9, 9x12, 10x13, DL, C6, C5, C4 or custom), the return address in the top-left corner and the delivery address inside the USPS read area, in the destination country's line order. Each address gets an envelope; problems (missing ZIP, unknown state, wrapped lines) are listed. Also a CSV. Does not buy postage, print stamps or barcodes, verify addresses, or print label sheets.
| Name | Type | Req | Description |
|---|---|---|---|
| addresses | – | – | Same as recipients (either name works). |
| bold_name | – | – | Print the recipient's name in bold, e.g. true. Default false. |
| columns | – | – | Column mapping when headings are unusual, field to heading, e.g. {"name":"Guest","address1":"Mailing Street","zip":"Postcode"}. |
| envelope_size | – | – | Envelope size: 10, 9, 6-3/4, monarch, a2, a6, a7, a9, 6x9, 9x12, 10x13, dl, c6, c5, c4 or a custom size like "5.5 x 8.5 in" or "114 x 229 mm". Synonyms work: "business" = 10, "5x7" or "invitation" =… |
| feed | – | – | With paper letter or a4: where the envelope sits in the tray, center (default), left or right. |
| file | object | – | Optional uploaded address list: CSV, TSV or Excel .xlsx with a header row (Name, Address, City, State, ZIP, Country), e.g. wedding guests.xlsx. Google Contacts, Outlook, Etsy and Shopify exports work. |
| font_size | – | – | Address text size in points, 8 to 24, e.g. 12. Default 12 (11 on narrow envelopes). Long lines shrink to fit and wrap; nothing is cut off. |
| height | – | – | Custom envelope height with width, e.g. 4.125 or "162 mm". |
| home_country | – | – | Country you mail from; the country line is printed only for other countries, e.g. "UK". Default: the return address's country, else United States. |
| include_home_country | – | – | Also print the country line for addresses in your own country when a country is given. Default false. |
| outline | – | – | Draw the envelope edge on every page (for checking on plain paper). Default false. |
| paper | – | – | envelope (default: each PDF page is the envelope size) or letter / a4 (the envelope is drawn turned on a full sheet, for printers that cannot take a custom size). |
| recipients | – | – | The addresses, one envelope each. Convert what the user pasted or showed in an image into objects first, e.g. [{"name":"Jane Smith","address1":"123 Main St","address2":"Apt 4B","city":"Springfield","… |
| return_address | – | – | Sender address for the top-left corner, as text with \n or commas between lines, a list of lines, or an object, e.g. "The Garcia Family\n42 Oak Lane\nPortland, OR 97205". Leave out for no return addr… |
| sheet | – | – | Excel sheet to read, e.g. Guests. Default: the first sheet with data. |
| sort | – | – | Order of the envelopes: none (list order, default), zip, name or country. |
| test_page | – | – | Add a first page with the envelope outline and sample text, to print on plain paper and hold against an envelope. Default true. |
| uppercase | – | – | USPS style: all capitals without periods or commas, e.g. true. Default false. |
| width | – | – | Custom envelope width with height, e.g. 9.5 or "229 mm". Numbers are inches unless above 30 (then mm). |
| Name | Type | Req | Description |
|---|---|---|---|
| assumed | array | yes | – |
| countries | object | yes | – |
| downloads | object | yes | – |
| duplicates | number | yes | – |
| envelope | object | yes | – |
| envelopes | number | yes | – |
| envelopes_with_issues | number | yes | – |
| feed | string|null | yes | – |
| file_name | string|null | yes | – |
| font_size_pt | number | yes | – |
| home_country | string | yes | – |
| issues | array | yes | – |
| issues_count | number | yes | – |
| links_expire_minutes | number | yes | – |
| notes | array | yes | – |
| paper | string | yes | – |
| pdf_pages | number | yes | – |
| preview | array | yes | – |
| preview_count | object | – | – |
| print_instructions | string | yes | – |
| printed_as_given | number | yes | – |
| return_address | array | yes | – |
| smallest_font_pt | number | yes | – |
| test_page | boolean | yes | – |
| usps_note | string | yes | – |
No examples provided.
How do I install the Zovo Envelope Printer MCP server?
Zovo Envelope Printer is a hosted endpoint at https://envelope-printer.zovo.one/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 · envelope-printer.zovo.one
claude mcp add --transport http theluckystrike-envelope-printer 'https://envelope-printer.zovo.one/mcp'
What is the Zovo Envelope Printer MCP server?
Zovo Envelope Printer is an MCP server listed in the public MCP registry as io.github.theluckystrike/envelope-printer. Print envelopes with addresses at home. This page covers its hosted endpoint (https://envelope-printer.zovo.one/mcp).
Is the Zovo Envelope Printer MCP server safe to use?
Zovo Envelope Printer scores 78 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 Zovo Envelope Printer MCP server expose?
Zovo Envelope Printer exposes 2 tools: generate_envelope_pdf, find_envelope_size. Their descriptions and schemas cost roughly 1,247 tokens of context every time the server is loaded.
Does the Zovo Envelope Printer MCP server require authentication?
No. We connected to Zovo Envelope Printer without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Zovo Envelope Printer MCP server still maintained?
Zovo Envelope Printer 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 Zovo Envelope Printer MCP server?
VerifyMCP ran 14 checks on Zovo Envelope Printer, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. 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.