Vendor: quickmail.com (redirected from quickmail.io) · entry id 02-quickmail · source 02-engagement-outbound.md line 217
No server was found at the time of the check. That is a statement about the search, not a promise that none exists. The status was established on 2026-09-02.
mcp_status, verbatim from the file:
none-found
mcp_url, verbatim from the file:
n/a
No CLI found by the 2026-09-27 harvest across vendor docs, npm, PyPI, Homebrew and GitHub. That is a probe result, not proof of absence.
api_gate, verbatim from the file:
paid
No documentation URL recorded.
727 of 1252 entries are in the same position. Blank is legal and it is published as blank.
Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build.
The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale.
No GitHub organisation could be tied to quickmail.com with evidence on 2026-09-08.
Recorded by the harvest: github candidates were seen but none passed the evidence rules.
5 candidate accounts seen and rejected by the evidence rules: QuickMail, QuickmailAu, QuickMailServer, quickmails, quickmail-io. A name match alone is never accepted; the account has to point at the vendor domain.
A job tag means the vendor says the tool does this. It is not a test result, not proof the capability is reachable through the tool's MCP server, and not proof it is available on the gate this entry records.
Tagged by machine-pass on 2026-08-25 against the closed 56 job vocabulary. 271 of 1,252 entries carry at least one tag; 849 tags are assigned in total.
2 source URLs. Raw sources field, verbatim:
https://quickmail.com/pricing, https://quickmail.com/
Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the methodology page.