Skip to main content
Glama
Sign In
sourcing

sourcing

by m2nho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to sourcing

No user-submitted related servers found.

    Related Servers

    • mcp-local-leads

      ellokillox
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to find local businesses that appear on Google Maps but lack a website, filter by city and niche, and export matching leads to CSV via Google Places API (New).
      MIT

    • LinkedIn Profile Data Mining

      amankale376
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables comprehensive LinkedIn profile search, data extraction, and contact enrichment using Google Search, Apollo.io, and AI-powered analysis. Includes automated data mining workflows with database storage and CSV export capabilities.
      3
      ISC

    • LeadMarina MCP server

      macgregordev
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to search for verified local-business leads by niche and US location, check email deliverability and phone details, filter collected leads, and export or schedule results to CRM, spreadsheet, or file destinations. It also supports advanced multi-keyword searches, lead estimates, integrations, and automation management through natural language.
      MIT

    • medical-hospital-mcp-server

      handaas
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables hospital search and detail lookup to discover medical institutions and verify campuses, departments, contacts, introductions, and operating entities.
      1
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 7 tools

    Disambiguation4/5

    The async job lifecycle tools (start/check/list/cancel_collection) are clearly distinct, as are get_leads and export_excel. The only mild confusion is the shared 'check_' prefix on check_collection (job progress) and check_site_whatsapp (single website lookup), and list_collections overlapping somewhat with check_collection in purpose, but descriptions resolve these adequately.

    Naming Consistency4/5

    All tools follow a verb_noun snake_case pattern (start_collection, cancel_collection, get_leads, export_excel), which is predictable and readable. Minor deviations: list_collections uses plural while other collection tools use singular, and check_site_whatsapp is a compound noun rather than a simple object.

    Tool Count5/5

    Seven tools is well-scoped for the stated purpose of bulk Google Maps lead collection. Each tool earns its place: four for the async job lifecycle, one for reading results, one for single-site WhatsApp verification, and one for Excel export recovery.

    Completeness5/5

    The tool set fully covers the collection lifecycle: start, check progress, list jobs, cancel (with preserved partial results), read leads, verify a single site, and export to Excel even after cancellation. Cross-session access via csv_path is a thoughtful touch that prevents dead ends.

    Maintenance

    ActivityStale
    ResponsivenessNo recent community issues

    Resources