Vertical Lead Pack API - Real Estate & Clinics

com.ranovamPublished by ranovam.comv0.1.1Updated Oct 24, 2026

Decision-maker leads for one vertical (real estate or clinics).

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

A remote MCP server that gives an assistant decision-maker lead data for one vertical: real estate or clinics.

What you can do
It exposes a lead-pack capability for a single vertical, either real estate or clinics, returning decision-maker leads. The manifest lists no individual tools, so the exact operations are not documented. It runs as a remote streamable HTTP endpoint rather than a local package.
When to use it
Consider it when you need decision-maker contact leads in real estate or clinics and want an assistant to pull them into a workflow. It is not a general-purpose data source; it is scoped to those two verticals.
Requirements
A remote MCP endpoint reached over streamable HTTP. Authentication is required: an Apify API token sent as a Bearer token in the Authorization header, or OAuth if your MCP client supports it. No local runtime, packages, or environment variables are declared.
Before you install
The Authorization header carries an Apify API token, a billable account credential; keep it secret and prefer OAuth where supported. Apify usage may incur costs on your account. Lead data concerns named individuals, so handle it under applicable privacy rules. The manifest lists no tools, so review what the server actually does before relying on it.

Installation

In SourceWeft

  1. Open Vertical Lead Pack API - Real Estate & Clinics 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/com.ranovam%2Fvertical-lead-pack/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": {
    "vertical-lead-pack-api-real-estate-clini": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=enezli/vertical-lead-pack"
    }
  }
}

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

2
  1. v0.1.1LatestSep 28, 2026
  2. v0.1Sep 16, 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.