Vendor: saleshandy.com · entry id 02-saleshandy · source 02-engagement-outbound.md line 580
The vendor ships and maintains the server itself. A wrapper built by Zapier, Composio or a similar third party does not count as official. The status was established on 2026-09-07 and the MCP URL has not been probed live yet.
mcp_status, verbatim from the file:
official
mcp_url, verbatim from the file:
https://mcp.saleshandy.com/mcp (docs: https://developer.saleshandy.com/api-reference/mcp; product page: https://www.saleshandy.com/mcp) ; repo https://github.com/saleshandy/saleshandy-plugin
Not harvested yet. Unmeasured, not empty: nobody has read this server's tool list, so this page says nothing about what it exposes.
141 of the 741 entries that record an official or community MCP server carry a harvested tool list. The other 600 are unmeasured, which is not the same as empty. Harvest last run 2026-09-27. The full roll up is on the tools index.
Install, as the source shows it:
npm install -g @saleshandy/saleshandy-cliquoted from https://www.npmjs.com/package/@saleshandy/saleshandy-cli on 2026-09-27, via npm
Packages seen, with the version on 2026-09-27:
A CLI being listed means the harvest found an install command or a package on a stated date. Nobody has run it. Every command is quoted verbatim from the URL beneath it. Harvest date 2026-09-27.
api_gate, verbatim from the file:
paid - published self-serve tiers are Starter $34/month, Pro $76/month and Scale $149/month billed annually, each with a 7-day free trial, and the pricing page's feature list includes a row reading "MCP and CLI: Connect AI assistants, ChatGPT, Claude, Gemini, and more, to Saleshandy via the Model Context Protocol (MCP)" alongside "Platform API access: Push and pull data programmatically with the REST API." The per-tier ticks for those two rows are rendered client-side and did not fetch, so the plan floor is not recorded here.
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.
A github.com URL already appears somewhere in this entry, which is a seed for that rail and not a measurement of repo health:
github.com/saleshandy tied to the vendor by rule 3, account website https://www.saleshandy.com has the vendor's domain, confidence strong
The five most recently pushed, on 2026-09-08:
| Repository | Kind | Description | Stars | Pushed | Latest release |
|---|---|---|---|---|---|
| icons | other | The Saleshandy Icons Library is a comprehensive collection of 570+ SVG icons for use in your projects. | 1 | 2026-09-05 | |
| aws-kms-crypto | other | Package that lets you integrate AWS KMS seamlessly in your javascript project | 0 | 2026-08-26 | |
| devops.infrastructure.tf-modules | other | 0 | 2026-07-10 | ||
| outreach-superpower | other | 1 | 2026-05-19 | ||
| saleshandy-plugin | plugin or integration | 0 | 2026-05-11 |
Kind is a heuristic guessed from the repository name, topics and description, not a fact the vendor stated. A repository count is activity, not a verdict. Read 2026-09-08.
No job tag on this entry.
981 of 1,252 entries are untagged. An empty list here means nobody has tagged this, not that the tool does nothing. The vocabulary is closed, so a tool whose job is genuinely not in it stays blank rather than being forced into the nearest tag.
4 source URLs. Raw sources field, verbatim:
https://developer.saleshandy.com/api-reference/mcp, https://www.saleshandy.com/mcp, https://www.saleshandy.com/pricing/, https://mcp.saleshandy.com/mcp
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.