How it works The email Proof Price Questions Playbooks MCP Writing Levels and pricing Connect
Built for Claude Code and any MCP client

A reason behind every message,run from your own Claude.

One line connects Claude, ChatGPT or Cursor to the stack we run our own pipeline on. The price covers what happens around each message: a checked fact before it, the platform's limits and pacing during it, a text measured for repetition, and a weekly review that changes one rule on data. 26 tools, one token, from $199 a month.

claude · revault connected

Who are we writing to next week?

called queue_upcomingTwelve companies are queued for Monday to Wednesday, operations leads at logistics firms hiring for delivery roles.
Northwind FreightMon, 3 people
Halden GroupMon, 2 people
Baltic LaneTue, 2 people
Ferro SupplyWed, 3 people
Your own pipeline, asked in your own words Connect
Works with Claude app and web ChatGPT Claude Code Cursor and Codex

A token is issued to a person and revoked in a second. Every call is logged.

Connected in about a minute

Three steps, and the tools show up inside the chat you already work in.

1

Get your code

Enter your name and work email in the form below. The code arrives by email within a minute, issued to you by name. It sees one workspace: yours.

2

Press Connect, or paste one line

Claude app, Claude in the browser, ChatGPT, Codex: add a connector with the address below, press Connect, enter the code. Claude Code and Cursor: paste the line from the email.

https://mcp.re-vault.io/mcp
3

Say: Use Re:Vault

Two words start every chat. Claude asks what you sell and who buys it, finds real people, writes the first texts and connects your LinkedIn. The full guide, step by step.

Claude
Connectors
  • revault
  • Google Drive
  • Notion
revault tools
  • audience_search
  • queue_upcoming
  • outreach_recent
  • conversations
  • stats
  • exclude
How did last week go?
called stats148 invites out, 22 accepted, 3 replies. Accept rate 14.9%, inside the healthy band for cold LinkedIn. Your second profile is carrying the accepts at 20.1%.
Anything waiting on me?
called conversationsTwo replies. Both are drafted and waiting for your yes.

Names and numbers in the examples are made up. Your token returns your own.

Five things the price pays for

The tools are the door. Around every message the stack does five things, and each one is held by code: a database trigger, a check before the queue, a counter that pauses the profile.

  • A reason, then a nameEvery first message stands on one checked fact about the company: a sales role posted this week, a round filed, a product launched. The fact carries its source and its date. A person without one stays in the pool until there is one.
  • A live profile, kept inside the limitsDaily caps come from the provider's documentation, with a rolling ceiling of 100 invitations per profile per seven days. A new account ramps from one invitation a day to ten over ten working days. The day's volume is spread across the working window, one cold touch a minute at most. A refusal pauses the profile for 30 to 60 minutes and the queue moves to the next person. An invitation note goes out from premium profiles only: on basic accounts we measured 66% refusals with a note against 0.3% without. New mechanics are tried on rented profiles first and reach a real person's account once they have held.
  • Copy under measurementThree voices of first touch run side by side, and the lead's id decides which one a person gets, so the comparison is fair inside every batch. Before a batch is queued the texts are checked for repetition: zero identical messages, any five-word phrase under 30% of the batch, any closing line under 25%. Three sentences or more go out as paragraphs. The booking link appears once in a thread.
  • Learning on outcomesEvery batch carries its signal and its segment, so a reply is credited to the reason that produced it. The weekly review reads reply rate by slice and changes one rule at a time, on 30 sends and 3 replies at minimum. Below that, the verdict is "still collecting".
  • An operator on the lineOn the Agent level, Dmitry reads the account every day and tunes it to the market. On MCP you drive it yourself from your Claude, and the caps, the profile protection and the weekly review underneath are the same ones.

26 tools, six questions

Grouped by what you actually want to know. In practice you ask in plain language and your agent picks.

Getting started

  • next_stepWhere you are and what comes next, with the one tool to call.
  • onboard_nextThe guided first run: what you sell, who buys it, the first people, the first texts, the channel.
  • linkedin_connectA one-time link to connect your own LinkedIn.
  • email_connectA mailbox on a pre-warmed domain for cold email, with your name and an opt-out line. Your own domain stays out of it.
  • budget_statusSpend for the month, what is left, and the breakdown by source.

Finding people

  • sources_listThe markers you can pull: what each returns, how often it refreshes, what a call costs.
  • sources_searchCompanies and people by one marker: open sales roles, a fresh Form D, LinkedIn posts by phrase, reactions under a post, Hacker News launches, a company's tech stack, news.
  • people_enrichLive profiles for a list of links: headline, city, audience size, the latest post.
  • contacts_findA verified work email for up to 25 profiles. Role mailboxes are flagged as what they are.
  • contacts_requestOrder a hunt for work emails and mobiles on a list of people. The finished list comes back with titles and the order to write in.

The audience and the queue

  • audience_profileWho counts as your buyer: segments, firmographics, personas, geography, exclusions.
  • audience_searchPeople in your base by name, company, title, geography, stage, and whether they replied.
  • queue_upcomingWho we write to in the coming days, with the date. This is where you cross out a pilot before the message goes.
  • outreach_queuePut invitations and messages from your connected LinkedIn into the queue. The sending layer takes it from there: inside the caps, in the recipient's working hours, spread across the day.
  • outreach_recentWhat already went out in your name: invites, likes, messages, InMail, with the text.

Conversations and numbers

  • conversationsLive threads: who replied, whose turn it is, the last thing said.
  • statsInvites, accepts and replies by sender and in total, next to the outside benchmark.
  • clients_listYour workspace at a glance: stage, live senders, audience size, touched, replied.
  • export_sheetAny of it as a Google Sheet, delivered to the address on your token.

The next message

  • message_briefThe material behind a message: the checkable fact with its source, the profile, the recent post, the thread so far, the voice and the hard rules.
  • message_generateDrafts written on our side with the copy rules and the sender voice, returned as finished texts.
  • draft_submitHand over a message you wrote yourself. It lands as a draft with the rules checked: length, dashes, banned words.
  • export_message_planA Google Doc with the prepared messages, and the same texts placed as drafts.
  • contacts_showWork emails and phone numbers from the base, with role mailboxes marked as what they are.

What you can change

  • excludeTake a company or a person out. It leaves the queue that second and the audience keeps the note.
  • requestPausing a profile, sending times, limits, changing the audience, money: all of it becomes a written request with Dmitry's answer, usually the same day.

Behind the tools

The tools are the questions you can ask. What fills your base is a sourcing stack that runs every day: buying signals from their first source, then enrichment, then a manual pass before anyone is written to.

42data providers reachable under one key
625endpoints across ads, news, jobs, tech, intent
14kinds of buying signal we collect today
5collectors we wrote ourselves, running daily
  • Hiring, from the sourceJob boards read directly, not resold: Greenhouse, Lever, Ashby, SmartRecruiters, Recruitee, Workable, Rippling. A role opened three days ago is a reason to write today.
  • Funding, the day it filesSEC Form D parsed daily, with the executive officers named. The company and the people arrive together.
  • What people say out loudLinkedIn posts, comments and reactions, GitHub activity, Hacker News launches and questions. Someone describing the problem is the strongest signal there is.
  • Money already movingLive ad activity, fresh news, partnership and launch events. Companies that are spending are companies that are deciding.
  • What they run onTechnology detections on the company's own stack, so the message can name the thing you integrate with.
  • Who exactly, and how to reach themFirmographics, personas and role changes, then waterfall enrichment for work email and mobile.

Every person in your base carries the signal they came from, so the weekly review compares sources against each other instead of guessing. That comparison is ours to run. The result of it is yours to read, through the 26 tools.

We run it on ourselves first

27.5%accept rate, 325 of 1,181 invitations sent in the last 30 days, each at least 3 days old
16.2%reply rate after the accept, 53 of 327 people who accepted in the last 30 days, each at least 7 days ago
0.2%of invitation attempts refused by the platform in the last 30 days, 3 of 1,220

Re:Vault sells the outreach it runs for itself, on the same stack and the same door. Recomputed 26 October 2026 across every workspace on the stack. The same rates sit next to the Expandi, Belkins and SmartReach reports of 2026, with definitions, on the numbers page.

Connect from $199 a month Token the same day, cancel in one message.

Where the door stops

Two things in outbound are permanent once they happen: a message sent under someone's name, and a wider audience touched. Both stay with the operator, and that is what keeps your account safe.

  • Sending stays with usInvites, messages and InMail leave from one place, on the rhythm your profile is warmed for.
  • Timing and volume stay with usWorking hours, pacing, warmup and daily caps. This rhythm is what platforms read as a human, and it is worth guarding.
  • Profiles stay as they areConnecting, pausing and limits live on our side, so the account keeps one owner and one hand.
  • Your workspace is yours aloneA token sees one account: yours. The filter runs on the query and again on the answer.
  • The method stays in houseSignals, scoring, the copy library, the experiments and the rejected candidates. You buy the result of the method, and the result is yours.
  • Personal contacts stay privateWork email and work phone are in. Personal addresses and personal accounts stay where they belong.

Ask for any of it and the door turns your ask into a request with a name on it, so the answer comes back the same day.

Questions people ask before connecting

  • Do I need to be technical?One line goes into your Claude, and after that you ask in plain words. If you would rather not paste anything, send the token to whoever handles your tooling and they will be done in a minute.
  • What can my agent see?Your workspace: your audience, your queue, your sent messages, your conversations, your numbers, your contacts. The filter runs on the query and again on the answer.
  • What does the price pay for?Five things around every message: a checked reason to write, a profile kept inside the platform's limits, copy measured for repetition, a weekly review that changes one rule on data, and an operator who set it up and keeps it running. The tools are how you reach all of it from your own Claude.
  • Is this safe for my LinkedIn account?Sending, timing and daily volume stay with the sending layer: caps from the provider's documentation, a ten-day ramp for a new account, the day spread across the working window, a 30 to 60 minute pause after a refusal. Your agent reads and narrows, and the pace stays where it is.
  • What if I need something the door does not do?Say it in the chat. It becomes a written request with your name on it, and the answer comes back the same day.
  • Can I stop?Month to month. One message cancels it, and the token dies the second you say so.
$199 / month
1 · $1992 · $2993 · $3994 · $499
  • One LinkedIn account is $199 a month. Each account after that adds $100, up to four at $499
  • Month to month, cancel in one message
  • Every call is logged: the tool, the arguments, the rows returned
  • Revoked in a second whenever you say so
The code arrives by email within a minute. Three days or $30 in credits to find people, write and send from your own Claude, then $199 a month. How to connect.
The operated worker Levels and pricing Our numbers