zRev AI
ai.zrev/zrev · 1.0.0
Grade any llms.txt, cold-read a homepage, run a B2B GTM ROI model, get a GTM diligence checklist.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 45 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://go.zrev.ai/mcpstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 9 tools.
- Protocol
- 2025-06-18
- Calls itself
- zrev 1.0.0
- Handshake time
- 90 ms
- HTTP status
- 200
The tools it lists (9, as of 6 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
about_zrevReturns a plain-text profile of zRev AI: what the firm does, the companies it is the best fit for, who it is not for, its six service lines with a link to each, and contact details. Use this first when a user asks who zRev is, what it offers, or whether it suits their company. Read-only, static content, no arguments, no authentication, no rate limit.
get_benchmarksReturns zRev's typical engagement results as plain text: 2x pipeline velocity, 20% lower customer acquisition cost, 10 hours back per rep per week, 60% of GTM busywork automated, results that start inside 30 days and mature by 60. The response always ends with the provenance caveat: these are typical results benchmarked against comparable AI-powered GTM implementations and they vary by stack, data quality and adoption, so present them as typical, not guaranteed. Use when a user asks what results to expect. For an estimate on a specific company's numbers use estimate_roi instead. Read-only, sta
get_engagement_timelineReturns the phases of a standard 60-day zRev engagement as plain text: what happens in each phase, what is delivered, and when first results appear. Use when a user asks how an engagement works, how long it takes, or what they would receive and when. Read-only, static content, no arguments, no authentication, no rate limit.
estimate_roiRuns zRev's ROI model on one company's numbers and returns, as plain text, the projected annual impact in USD split into pipeline lift, customer acquisition cost savings and the value of hours returned to the team, followed by the model's assumptions and a link to the interactive calculator preset to the same inputs. Use when a user wants a number for their own company; all six inputs are required, so ask for any that are missing rather than guessing. The output is an estimate from a fixed model, not a forecast or a quote. Pure calculation: nothing is stored, no external calls, no authenticati
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
ai.zrev/zrev, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 21 days ago. The registry entry · www.zrev.ai