
zRev AI MCP server
Which MCP servers are zRev AI's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-24
- Registry nameai.zrev/zrevverified in the MCP registry
The registry name sits under zrev.ai. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-24
- Tools9
- Server calls itselfzrev
- Server version1.0.0
- Protocol version2025-06-18
On 2026-10-24 the server answered initialize and tools/list without a sign-in. First answer in 81 ms.
- Its tools do none of the product's use cases we checked: score and route inbound leads to the right rep; clean up CRM data and forecasting reports; run outbound sequences and follow-up emails.
- Checked on 3 of the 7 days it takes to judge reliability.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
- What an agent can do with it0 of 3 use cases
- Answeredmeasuring3 of the 7 daily checks it takes to print a share
- Median first answer155 ms
- Space in an agent's context≈ 1,778 tokensthe definitions of all its tools (9), which an agent carries on every turn
- Tool definitionsA · 100 of 100
- Typed results0 of 9 toolsdeclared outputSchema: results come typed, read once
- Every tool passes all six checks.
What an agent can do with it
- cannot · score and route inbound leads to the right rep
- cannot · clean up CRM data and forecasting reports
- cannot · run outbound sequences and follow-up emails
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
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…
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…
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…
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…
grade_llms_txtFetches https://<domain>/llms.txt (the file that tells AI systems what a site contains) and grades it with seven deterministic checks. Returns a 0 to 100 score and the pass or miss result of each check as plain text. If the site has no…
cold_readFetches a company's public homepage and returns, in two or three sentences, what the company appears to do and who it serves, based only on the visible text of that page and with no outside knowledge. Anything missing from the answer is…
gtm_diligence_checklistReturns zRev's go-to-market due diligence checklist for investors and acquirers: 47 questions across ten dimensions, each with the data-room artifact that answers it and the red flag to watch for. Call with no arguments to get the list of…
book_callReturns the link and instructions for booking a free 30-minute intro call with zRev's founder, plus what the call covers. It does not book anything: it only returns the scheduling link for the human to open themselves. Use when a user…
leave_contactRecords an email address, with optional name, company and note, so that zRev's founder can reach out, and returns a plain-text confirmation. This is the only tool here that writes data: it creates one lead record on zRev's side and…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"zrev": {
"type": "http",
"url": "https://go.zrev.ai/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http zrev https://go.zrev.ai/mcpclaude.ai, ChatGPT and other clients: add https://go.zrev.ai/mcp as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.