https://mailmergepdf.com/mcp ↗
Mail Merge PDF: the site's own MCP server — checker, enquiry (enquiry = a human handoff, not a...
com.mailmergepdf/site is a remote MCP server published at mailmergepdf.com. It has been probed 12 times since 9/12/2026. It answered in 12 of them (100.0%), a near-uninterrupted record. Median response time is 497 ms, placing it among the faster endpoints. It offers a narrow, focused set of 6 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
checker_start — Description does not explain when or why to use it.checker_tree — Name and description lack clarity on its purpose.submit_enquiry — Description is cut off, missing critical details.| Run | Era | Modern | ms | Legacy | ms | Versions |
|---|
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
Tools the server advertised in the latest measurement — measured, not catalog-claimed.
checker_startThe first question of the Which mail merge to PDF route? decision guide.
checker_answerGiven a question id and the chosen option (its `choice` index), return the next question or the final verdict.
questionstringrequiredchoiceintegerrequiredchecker_treeEvery question, option and verdict of the Which mail merge to PDF route? guide, for reasoning end to end.
enquiry_describeRead 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_fieldsEvery 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_enquirySubmits 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. Step 2: only if the person agrees, call again with the same answers, consent=true and the confirmation token; the enquiry is then submitted, and the person receives an email with a link they must click before any provider sees it. Consent means the person has read and agreed to: "Happy for my details to go to document automation suppliers, who'll contact me directly."
answersobjectrequiredconsentbooleanrequiredconfirmationstringDerived by comparing consecutive probes — changes in era, protocol version, build and reachability.
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/com-mailmergepdf-site)<a href="https://mcpmetrics.io/servers/com-mailmergepdf-site"><img src="https://mcpmetrics.io/badge/com.mailmergepdf/site/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to seeThe catalog entries whose name and description are closest to this one, found with the same index the search box uses.
Class Q Checker: the site's own MCP server — checker, enquiry (enquiry = a human handoff, not a...
Bin Rules Checker: the site's own MCP server — checker, enquiry (enquiry = a human handoff, not...
Catchment Checker: the site's own MCP server — checker, enquiry (enquiry = a human handoff, not...
CQC Registration Checker: the site's own MCP server — checker, enquiry (enquiry = a human...
Malta Work Permit Checker: the site's own MCP server — checker, enquiry (enquiry = a human...
Smoke Control Checker: the site's own MCP server — checker, enquiry (enquiry = a human handoff,...
| 2026-09-13 14:49:35 | Legacy | 400 | 921 | 200 | 942 | 2025-11-25 |
| 2026-09-13 12:47:19 | Unknown | 429 | 252 | 429 | 247 | — |
| 2026-09-13 10:45:14 | Unknown | 429 | 336 | 429 | 330 | — |
| 2026-09-13 08:43:04 | Unknown | 429 | 571 | 429 | 675 | — |
| 2026-09-13 06:40:42 | Unknown | 429 | 371 | 429 | 372 | — |
| 2026-09-13 04:35:29 | Unknown | 429 | 498 | 429 | 497 | — |
| 2026-09-13 01:33:33 | Unknown | 429 | 725 | 429 | 712 | — |
| 2026-09-12 23:31:36 | Unknown | 429 | 616 | 429 | 611 | — |
| 2026-09-12 21:29:15 | Unknown | 429 | 992 | 429 | 668 | — |
| 2026-09-12 19:27:29 | Unknown | 429 | 316 | 429 | 282 | — |
Each block is one measurement round. Green: working response. Amber: responded but the server was returning errors (5xx). Red: no response at all.
Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.
The two probe legs separately: modern server/discover and legacy initialize.
Comments
Sign in to write a comment
No comments yet. Be the first.