RevenueBase

ai.revenuebasePublished by revenuebase.aiOfficial publisherv0.1.0Updated Oct 24, 2026

Find B2B contacts, inspect audience coverage, enrich emails, and verify deliverability.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Lets an assistant find B2B contacts, check audience coverage, enrich email addresses and verify deliverability.

What you can do
The server exposes RevenueBase capabilities to an assistant over a remote streamable HTTP endpoint. According to the registry description it can find B2B contacts, inspect audience coverage, enrich emails and verify deliverability. No individual tools are listed in the manifest, so the exact operations and their inputs are not shown.
When to use it
Worth considering when a workflow needs B2B contact discovery, audience or coverage checks, email enrichment, or deliverability verification, and the assistant should reach that data directly rather than through manual lookups.
Requirements
Runs as a remote streamable HTTP endpoint at no packages, environment variables or headers are declared. The manifest declares no authentication, so any account, API key or credential needed is not stated in the supplied material.
Before you install
The registry description mentions enriching emails and verifying deliverability, which implies contact data is processed; the manifest declares no authentication, environment variables or headers, so how access is controlled is not shown. No details are given about data sent to third parties, spending, or write actions.

Installation

In SourceWeft

  1. Open RevenueBase 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/ai.revenuebase%2Frevenuebase/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": {
    "revenuebase": {
      "type": "http",
      "url": "https://mcp.revenuebase.ai/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. v0.1.0LatestOct 14, 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.