Prospeo MCP Serverofficial
A
licenseA
qualityF
maintenanceEnables AI tools to search and enrich B2B leads, including finding professional emails, company profiles, and filtering people and companies by various criteria.
5
227
MIT
generect-mcp
by com.generect
Server Details
B2B lead generation and company search through Generect Live API for sales prospecting.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Unhealthy
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- generect/generect_mcp
- GitHub Stars
- 1
- Server Listing
- Generect Live API MCP Server
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
4 tool updates
- Changed
generate_email6 fields changed- added
Input schema / properties / candidatesAdded value: +{ + "description": "Batch mode: resolve many people in one call. Each needs first_name, last_name, domain (middle_name optional).", + "items": { + "additionalProperties": false, + "properties": { + "domain": { + "type": "string" + }, + "first_name": { + "type": "string" + }, + "last_name": { + "type": "string" + }, + "middle_name": { + "type": "string" + } + }, + "required": [ + "first_name", + "last_name", + "domain" + ], + "type": "object" + }, + "type": "array" +} - changed
Input schema / properties / domain / descriptionPrevious value: -"Company domain without protocol (e.g., generect.com)"New value: +"Company domain without protocol, e.g. \"generect.com\" (required in single-person mode)." - changed
Input schema / properties / first_name / descriptionPrevious value: -"First name of the person"New value: +"First name (single-person mode)." - changed
Input schema / properties / last_name / descriptionPrevious value: -"Last name of the person"New value: +"Last name (single-person mode)." - added
Input schema / properties / middle_nameAdded value: +{ + "description": "Middle name (optional).", + "type": "string" +} - removed
Input schema / requiredRemoved value: -[ - "first_name", - "last_name", - "domain" -]
- Changed
health2 fields changed- added
Input schema / properties / deepAdded value: +{ + "description": "Run a live API probe (lead-by-link). Consumes a credit. Default false.", + "type": "boolean" +} - changed
Input schema / properties / url / descriptionPrevious value: -"LinkedIn profile URL to validate (defaults to a public profile)"New value: +"LinkedIn profile URL for the deep probe (defaults to a public profile)."
- Changed
search_companies15 fields changed- changed
Input schema / properties / compact / descriptionPrevious value: -"Return compact summary instead of full JSON"New value: +"Default true: 6-field summary per company. Set false for the full raw object." - added
Input schema / properties / company_namesAdded value: +{ + "description": "Restrict to specific company names.", + "items": { + "type": "string" + }, + "type": "array" +} - added
Input schema / properties / exclude_industriesAdded value: +{ + "description": "Industries to exclude (same taxonomy as industries).", + "items": { + "type": "string" + }, + "type": "array" +} - added
Input schema / properties / exclude_locationsAdded value: +{ + "description": "Locations to exclude.", + "items": { + "type": "string" + }, + "type": "array" +} - changed
Input schema / properties / fallback_from_leads / descriptionPrevious value: -"If no companies, derive from leads by keywords"New value: +"Default FALSE. If true and the company search is empty, derive candidate company NAMES by aggregating a keyword lead search. These are lead-derived name counts (source:\"leads_derived\"), NOT real company records, and cost an extra query." - changed
Input schema / properties / get_max_companies / descriptionPrevious value: -"Get maximum companies"New value: +"Also report the total number of matching companies." - changed
Input schema / properties / headcounts / descriptionPrevious value: -"Employee headcount ranges. Allowed values ONLY: \"1\", \"2-10\", \"11-50\", \"51-200\", \"201-500\", \"501-1000\", \"1001-5000\", \"5001-10000\", \"10000+\". Note the largest bucket is \"10000+\" (NOT \"10001+\")."New value: +"Employee headcount buckets. Allowed ONLY: \"1-10\",\"11-50\",\"51-200\",\"201-500\",\"501-1000\",\"1001-5000\",\"5001-10000\",\"10 000+\" (note the space in \"10 000+\")." - changed
Input schema / properties / industries / descriptionPrevious value: -"Industries. Must match Generect industry names exactly (e.g. \"Software Development\", \"Financial Services\"). Invalid names are rejected by the API."New value: +"Industries. Must match Generect industry names exactly (e.g. \"Software Development\", \"Financial Services\"). Names are hierarchical. Invalid names are rejected (HTTP 400)." - changed
Input schema / properties / keywords / descriptionPrevious value: -"Keywords"New value: +"Free-text keywords (Boolean phrases allowed)." - changed
Input schema / properties / limit_by / descriptionPrevious value: -"Number of results to return"New value: +"Companies to return (1–100, default 25)." - changed
Input schema / properties / locations / descriptionPrevious value: -"Locations (countries, e.g. [\"United States\"])"New value: +"Locations (countries/regions, e.g. [\"United States\"])." - added
Input schema / properties / num_of_followersAdded value: +{ + "description": "LinkedIn follower-count buckets.", + "items": { + "type": "string" + }, + "type": "array" +} - changed
Input schema / properties / offset_by / descriptionPrevious value: -"Offset for pagination"New value: +"Offset for pagination." - added
Input schema / properties / revenues_rangeAdded value: +{ + "additionalProperties": false, + "description": "Annual revenue range in millions USD, e.g. {\"min\":0.5,\"max\":1001}. Single object, NOT an array.", + "properties": { + "max": { + "type": "number" + }, + "min": { + "type": "number" + } + }, + "required": [ + "min", + "max" + ], + "type": "object" +} - added
Input schema / properties / technologiesAdded value: +{ + "description": "Technologies the company uses (BuiltWith taxonomy).", + "items": { + "type": "string" + }, + "type": "array" +}
- Changed
search_leads25 fields changed- added
Input schema / properties / changed_jobsAdded value: +{ + "description": "Only leads who recently changed jobs.", + "type": "boolean" +} - changed
Input schema / properties / compact / descriptionPrevious value: -"Return compact summary instead of full JSON"New value: +"Default true: return a 9-field summary per lead (name/title/company/industry/location/linkedin_url). Set false for the full raw lead object (skills, experience, etc.). Neither mode includes email — use generate_email." - added
Input schema / properties / company_headcountsAdded value: +{ + "description": "Employer size buckets. Allowed ONLY: \"1-10\",\"11-50\",\"51-200\",\"201-500\",\"501-1000\",\"1001-5000\",\"5001-10000\",\"10 000+\" (note the space in \"10 000+\").", + "items": { + "type": "string" + }, + "type": "array" +} - changed
Input schema / properties / company_id / descriptionPrevious value: -"LinkedIn company id"New value: +"Anchor to a specific LinkedIn company id (returns its employees; this branch is less deterministic and does not enforce lead_industries)." - added
Input schema / properties / company_industriesAdded value: +{ + "description": "Filter by the lead employer's industry (same taxonomy as lead_industries).", + "items": { + "type": "string" + }, + "type": "array" +} - changed
Input schema / properties / company_link / descriptionPrevious value: -"LinkedIn company URL"New value: +"Anchor to a specific LinkedIn company URL." - added
Input schema / properties / company_locationsAdded value: +{ + "description": "Filter by the employer HQ location (country/region names).", + "items": { + "type": "string" + }, + "type": "array" +} - changed
Input schema / properties / company_name / descriptionPrevious value: -"Company name"New value: +"Anchor to a specific company by name." - added
Input schema / properties / company_typesAdded value: +{ + "description": "Employer types: \"Public Company\",\"Educational\",\"Self Employed\",\"Government Agency\",\"Non Profit\",\"Self Owned\",\"Privately Held\",\"Partnership\".", + "items": { + "type": "string" + }, + "type": "array" +} - added
Input schema / properties / exclude_idsAdded value: +{ + "description": "sales_ids to exclude — pass the ids of leads already returned in prior calls to paginate/deduplicate.", + "items": { + "type": [ + "string", + "number" + ] + }, + "type": "array" +} - added
Input schema / properties / exclude_namesAdded value: +{ + "description": "Full names to exclude from results.", + "items": { + "type": "string" + }, + "type": "array" +} - added
Input schema / properties / exclude_title_keywordsAdded value: +{ + "description": "Title keywords to exclude from persona matching. Defaults to [assistant, intern, junior, student, trainee]; pass [] to disable.", + "items": { + "type": "string" + }, + "type": "array" +} - added
Input schema / properties / functionsAdded value: +{ + "description": "Job functions (LinkedIn Sales-Nav categories, e.g. [\"Engineering\",\"Operations\",\"Marketing\",\"Sales\",\"Finance\"]). Validated by the API.", + "items": { + "type": "string" + }, + "type": "array" +} - added
Input schema / properties / get_max_leadsAdded value: +{ + "description": "Also report the total number of matching leads (results_count). The number of rows returned is still bounded by limit_by.", + "type": "boolean" +} - changed
Input schema / properties / job_title / descriptionPrevious value: -"Job title filter (e.g., CEO, CTO, Engineer)"New value: +"Single job title (e.g., \"CEO\"). For multiple titles use job_titles." - added
Input schema / properties / job_titlesAdded value: +{ + "description": "One or more target job titles, OR-matched (e.g. [\"CEO\",\"Founder\",\"Owner\",\"President\"]). Preferred over job_title. Assistant/intern/junior/student/trainee are excluded by default; override with exclude_title_keywords.", + "items": { + "type": "string" + }, + "type": "array" +} - added
Input schema / properties / keywordsAdded value: +{ + "description": "Free-text keywords matched against the profile (Boolean phrases allowed).", + "items": { + "type": "string" + }, + "type": "array" +} - changed
Input schema / properties / lead_industries / descriptionPrevious value: -"Industry filter. Must match Generect industry names exactly (e.g. \"Information Technology and Services\", \"Financial Services\"). Invalid names are rejected by the API."New value: +"Lead personal-industry filter. Must match Generect industry names exactly (e.g. \"Financial Services\", \"IT Services and IT Consulting\"). Names are hierarchical (Financial Services includes Banking/Insurance). Invalid names are rejected (HTTP 400)." - changed
Input schema / properties / limit_by / descriptionPrevious value: -"Number of results to return"New value: +"Total leads to return this call (1–100, default 25). This is a TOTAL cap across all personas. For more, paginate with exclude_ids." - changed
Input schema / properties / locations / descriptionPrevious value: -"Location filter — country or region names, e.g. [\"United States\", \"Canada\"]"New value: +"Lead location filter — country/region names, e.g. [\"United States\",\"Canada\"]." - changed
Input schema / properties / offset_by / descriptionPrevious value: -"Offset for pagination"New value: +"Offset for pagination (note: ordering is not stable — exclude_ids is more reliable)." - added
Input schema / properties / personasAdded value: +{ + "description": "Advanced: raw persona tuples [label,[titles],[secondary],[exclusions],seniority?]. Overrides job_title/job_titles.", + "type": "array" +} - added
Input schema / properties / posted_on_linkedinAdded value: +{ + "description": "Only leads who recently posted on LinkedIn.", + "type": "boolean" +} - added
Input schema / properties / senioritiesAdded value: +{ + "description": "Seniority levels (LinkedIn Sales-Nav categories, e.g. [\"Director\",\"VP\",\"Head\",\"Owner\",\"Manager\"]). Validated by the API.", + "items": { + "type": "string" + }, + "type": "array" +} - changed
Input schema / properties / without_company / descriptionPrevious value: -"Search leads without filtering by companies"New value: +"Search across all companies (filter-only). Auto-enabled when no company_id/link/name is given; this branch enforces all filters. Ignored when a company anchor is set."
2 tool updates
- Changed
search_companies6 fields changed- changed
Input schema / properties / company_types / descriptionPrevious value: -"Company types"New value: +"Company types. Allowed values: \"Public Company\", \"Educational\", \"Self Employed\", \"Government Agency\", \"Non Profit\", \"Self Owned\", \"Privately Held\", \"Partnership\"." - changed
Input schema / properties / headcounts / descriptionPrevious value: -"Headcount ranges"New value: +"Employee headcount ranges. Allowed values ONLY: \"1\", \"2-10\", \"11-50\", \"51-200\", \"201-500\", \"501-1000\", \"1001-5000\", \"5001-10000\", \"10000+\". Note the largest bucket is \"10000+\" (NOT \"10001+\")." - changed
Input schema / properties / industries / descriptionPrevious value: -"Industries"New value: +"Industries. Must match Generect industry names exactly (e.g. \"Software Development\", \"Financial Services\"). Invalid names are rejected by the API." - added
Input schema / properties / limitAdded value: +{ + "description": "Alias for limit_by", + "type": "number" +} - changed
Input schema / properties / locations / descriptionPrevious value: -"Locations (Countries, e.g \"United States\")"New value: +"Locations (countries, e.g. [\"United States\"])" - added
Input schema / properties / offsetAdded value: +{ + "description": "Alias for offset_by", + "type": "number" +}
- Changed
search_leads5 fields changed- changed
Input schema / properties / lead_industries / descriptionPrevious value: -"Industry filter (e.g., Technology, Healthcare)"New value: +"Industry filter. Must match Generect industry names exactly (e.g. \"Information Technology and Services\", \"Financial Services\"). Invalid names are rejected by the API." - added
Input schema / properties / limitAdded value: +{ + "description": "Alias for limit_by", + "type": "number" +} - changed
Input schema / properties / locations / descriptionPrevious value: -"Location filter (e.g., San Francisco, New York)"New value: +"Location filter — country or region names, e.g. [\"United States\", \"Canada\"]" - added
Input schema / properties / offsetAdded value: +{ + "description": "Alias for offset_by", + "type": "number" +} - changed
Input schema / properties / without_company / descriptionPrevious value: -"Search leads without filrest by companies"New value: +"Search leads without filtering by companies"
2 tool updates
- Changed
search_companies4 fields changed- added
Input schema / properties / limit_byAdded value: +{ + "description": "Number of results to return", + "type": "number" +} - added
Input schema / properties / locationsAdded value: +{ + "description": "Locations (Countries, e.g \"United States\")", + "items": { + "type": "string" + }, + "type": "array" +} - removed
Input schema / properties / max_itemsRemoved value: -{ - "description": "Maximum items to include in response (local trim)", - "type": "number" -} - added
Input schema / properties / offset_byAdded value: +{ + "description": "Offset for pagination", + "type": "number" +}
- Changed
search_leads10 fields changed- removed
Input schema / properties / industryRemoved value: -{ - "description": "Industry filter (e.g., Technology, Healthcare)", - "type": "string" -} - added
Input schema / properties / lead_industriesAdded value: +{ + "description": "Industry filter (e.g., Technology, Healthcare)", + "items": { + "type": "string" + }, + "type": "array" +} - removed
Input schema / properties / limitRemoved value: -{ - "description": "Number of results to return", - "type": "number" -} - added
Input schema / properties / limit_byAdded value: +{ + "description": "Number of results to return", + "type": "number" +} - removed
Input schema / properties / locationRemoved value: -{ - "description": "Location filter (e.g., San Francisco, New York)", - "type": "string" -} - added
Input schema / properties / locationsAdded value: +{ + "description": "Location filter (e.g., San Francisco, New York)", + "items": { + "type": "string" + }, + "type": "array" +} - removed
Input schema / properties / max_itemsRemoved value: -{ - "description": "Maximum items to include in response (local trim)", - "type": "number" -} - removed
Input schema / properties / offsetRemoved value: -{ - "description": "Offset for pagination", - "type": "number" -} - added
Input schema / properties / offset_byAdded value: +{ + "description": "Offset for pagination", + "type": "number" +} - added
Input schema / properties / without_companyAdded value: +{ + "description": "Search leads without filrest by companies", + "type": "boolean" +}
5 tool updates
- First observed
generate_email - First observed
get_lead_by_url - First observed
health - First observed
search_companies - First observed
search_leads
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
Real-time B2B data for agents: search and enrich 1B+ people and 200M+ company profiles.
- SalesQLOAuthcom.salesql
Find verified B2B emails and phone numbers; search and enrich people and companies for prospecting.
Search B2B contacts, enrich verified emails and phone numbers, and export results.
B2B lead generation — prospect discovery, ICP scoring, outreach, and pipeline management.
Related MCP Servers
- FlicenseNot gradedqualityCmaintenanceReal-time B2B company firmographics, headcount tier, ARR estimate, tech stack adoption, and verified C-Level executive contact emails for AI SDRs and sales automation.-
- FlicenseNot gradedqualityDmaintenanceTransforms job postings into qualified sales leads by searching for active jobs, enriching company data, and identifying decision-maker contact information.-
- AlicenseAqualityDmaintenanceEnables AI assistants to search and retrieve B2B leads and company data from the LeadBrew database, including contact details and company information.51MIT
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.6/5.0
Disambiguation5/5
Each tool has a distinct purpose: email generation from name+domain, lead retrieval by LinkedIn URL, health check, company search, and lead search. Descriptions clearly differentiate inputs and outputs, leaving no ambiguity.
Naming Consistency4/5
Most tools follow a verb_noun pattern (generate_email, search_companies, search_leads), but 'health' is a noun and 'get_lead_by_url' uses a longer phrase. Snake_case is consistent, and the deviation is minor.
Tool Count5/5
With 5 tools, the set covers essential lead generation operations without being too sparse or bloated. The count is well-suited for the domain.
Completeness4/5
Core workflows (search companies, search leads, get lead by URL, generate emails) are covered. Missing a tool for company details by URL, but batch email generation partially compensates. Minor gap prevents a perfect score.