Google Maps Email Cleaner & Lead Verifier

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

Clean, dedupe and verify Google Maps leads from any scraper.

VerifiedStreamable HTTPWeb executableData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

A remote Apify-hosted MCP server that lets an assistant clean, deduplicate and verify Google Maps lead lists from any scraper.

What you can do
Clean Google Maps lead data, removing duplicates and normalizing entries from any scraper source. Verify lead records so an assistant can flag or confirm contact details. Work with scraped business listings as a tidy, deduplicated dataset. No individual tools are listed in the manifest, so exact operations are not documented.
When to use it
Useful when you have raw Google Maps lead exports from a scraper and want an assistant to tidy, deduplicate and verify them before outreach or import into a CRM.
Requirements
A remote endpoint at mcp.apify.com over streamable HTTP. Authentication is required: an Apify API token sent as a Bearer token in the Authorization header, or OAuth if the MCP client supports it. An Apify account is implied.
Before you install
You must supply an Apify API token, a credential that grants access to your Apify account; keep it private. Lead data is processed through Apify's hosted service, a third party. Verification results may be inaccurate, so confirm contacts before outreach. Usage may consume Apify account credits.

Installation

In SourceWeft

  1. Open Google Maps Email Cleaner & Lead Verifier 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%2Fmaps-contact-cleaner/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": {
    "google-maps-email-cleaner-lead-verifier": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=enezli/maps-contact-cleaner"
    }
  }
}

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.