Re:Vault

io.re-vaultPublished by re-vault.ioOfficial publisherv1.0.0Updated Oct 30, 2026

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

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Re:Vault is a remote MCP server that helps an assistant find B2B buyers with a live reason to talk, draft first messages, and send them from your own LinkedIn.

What you can do
  • Find B2B buyers that have a current, live reason to talk.
  • Draft first outreach messages for those prospects.
  • Send messages from your own LinkedIn account.
  • No tool list is published, so the exact actions available are not documented here.
When to use it
Useful for sales or business-development work where you want an assistant to surface prospects with a timely trigger and prepare or send first-touch LinkedIn outreach.
Requirements
A remote endpoint at mcp.re-vault.io over streamable HTTP, with OAuth sign-in required. No environment variables or headers are declared. A LinkedIn account is implied by sending from your own LinkedIn.
Before you install
Sending happens from your own LinkedIn account, so messages go out under your identity and may be visible to recipients and LinkedIn. OAuth grants the server access to your account. Prospect data is handled by a third-party service. Review what it will send before enabling outreach.

Installation

In SourceWeft

  1. Open Re:Vault in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.re-vault%2Foutreach/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "re-vault": {
      "type": "http",
      "url": "https://mcp.re-vault.io/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 29, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.