com.mailmergepdf/site · v1.0.1 · productivity
com.mailmergepdf/site is healthy: it completed an MCP handshake in 5994 ms and exposes 6 tools. It scores 59/100.
Mail Merge PDF: the site's own MCP server — checker, enquiry (enquiry = a human handoff, not a...
Endpoint: https://mailmergepdf.com/mcp (streamable-http)
No repository listed · Website · JSON · Add to my inventory
| health | 17 / 25 |
| authEase | 15 / 15 |
| toolQuality | 15 / 15 |
| maintenance | 7 / 15 |
| adoption | 0 / 10 |
| usage | 0 / 10 |
| security | 5 / 10 |
Scoring v0.3, computed 2026-10-15T02:31:25.495Z.
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-14T20:25:49.180Z | Healthy | 5994 |
checker_start | The first question of the Which mail merge to PDF route? decision guide. |
checker_answer | Given a question id and the chosen option (its `choice` index), return the next question or the final verdict. |
checker_tree | Every question, option and verdict of the Which mail merge to PDF route? guide, for reasoning end to end. |
enquiry_describe | Read first. States plainly what submit_enquiry does on Mail Merge PDF: it starts an enquiry with human providers who quote directly. Nothing is bought, ordered or paid; no quote is guaranteed; it is free. Also returns who receives the details, the consent wording, and how the person confirms. |
enquiry_fields | Every field of the Mail Merge PDF enquiry: key, label, type, whether required, help text and the allowed options where there are any. Pass answers to submit_enquiry keyed by field key. |
submit_enquiry | Submits an enquiry to Mail Merge PDF — NOT a purchase, NOT a guaranteed quote. Step 1: call with the answers (keyed by field key from enquiry_fields) and consent=true; it validates and returns a summary, the consent line and a confirmation token — show the person the summary and the consent line. St |