Vendor: revenuehero.io · entry id 10-revenuehero · source 10-scheduling-routing.md line 84
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 by hand on 2026-08-24. On 2026-09-04 the recorded URL served a documentation page, not an MCP endpoint. That is where to read about the server, not where to connect to it. An agent needs the second.
mcp_status, verbatim from the file:
official
mcp_url, verbatim from the file:
https://www.revenuehero.io/resources/tales-of-ops (vendor's own case-study page - the only public documentation found; describes a live MCP server RevenueHero's own engineering team provisions per customer over an SSE endpoint with a router token and system prompt)
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.
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:
unknown/enterprise-leaning - no public developer/API docs were found (help.revenuehero.io covers webhooks, JS events, and workflows only); the MCP server is obtainable only by contacting RevenueHero directly. The product itself is self-serve and tiered (Inbound Essentials ~$79/mo + $25-35/user; Enterprise ~$79/mo + $35-45/user; Lite $15/user; 14-day free trial, no perpetual free tier), but MCP access specifically is white-glove, not a plan checkbox.
949 of 1252 entries carry an unknown gate. Unknown is a legal answer and it ships as unknown rather than as a guess.
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/revenuehero tied to the vendor by rule 2, account website https://revenuehero.io/ has the vendor's domain, confidence strong
The five most recently pushed, on 2026-09-08:
| Repository | Kind | Description | Stars | Pushed | Latest release |
|---|---|---|---|---|---|
| sdk | SDK | 0 | 2026-04-07 |
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.
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.
5 source URLs. Raw sources field, verbatim:
https://www.revenuehero.io/resources/tales-of-ops, https://www.revenuehero.io/pricing, https://help.revenuehero.io/home/get-started, https://help.revenuehero.io/llms.txt, https://github.com/revenuehero/sdk
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.