mcpbeat Sign in

Re:Vault MCP Server

answering

Re:Vault is answering right now. Last checked 9 min ago.

Find B2B buyers with a live reason to talk, write first messages, send from your own LinkedIn.

Uptime history 5 days of history
5 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
199 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Re:Vault every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add outreach --transport http https://mcp.re-vault.io/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mcp.re-vault.io/mcp
~/.codex/config.toml
[mcp_servers.outreach]
url = "https://mcp.re-vault.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "outreach": {
      "url": "https://mcp.re-vault.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "outreach": {
      "type": "http",
      "url": "https://mcp.re-vault.io/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://mcp.re-vault.io/mcp streamable-http sign-in 174 ms 9 min ago

Alternatives to Re:Vault

same job, measured the same way
PumpGTM MCP server
by pumpgtm

Find buyers, run LinkedIn, email and X outreach, and answer replies from your AI.

answering
LinkedIn
by johannsenlum

Read LinkedIn profiles, companies, jobs and messages via your own browser session

126 installs/wk local only
LinkedIn MCP (by TalkToHumans)
by talktohumans

The safest LinkedIn MCP: your Agents read DMs, search your network and draft messages you send.

answering
LinkedIn MCP (by TalkToHumans)
by coolsapiens

The safest LinkedIn MCP: your Agents read DMs, search your network and draft messages you send.

answering
Naano
by naano

B2B LinkedIn creator campaigns from your AI assistant: find creators, run campaigns, read results.

answering
LinkedIn Ads
by getmcpads

LinkedIn Ads MCP server: 18 read tools, 15 opt-in preview-first writes.

583 installs/wk local only
Bereach
by benjaminb10

Find, qualify and message B2B leads from public LinkedIn data; every send is human-approved.

answering
Gigi AI
by usegigi

LinkedIn outreach from Claude with a human veto: review, approve and send drafts, triage replies.

answering

Re:Vault — questions

Answers built from our own checks of this server.

Why is there no tool list for Re:Vault?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Re:Vault working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 199 ms. The bar chart above shows every period we have measured.
How do I connect Re:Vault?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Re:Vault?
No API key is involved. Re:Vault answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Re:Vault?
It answers our handshake in 199 ms on average, which is faster than 71% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.