Server Details
B2B lead generation and company search through Generect Live API for sales prospecting.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
See and control every tool call
Available Tools
5 toolsgenerate_emailInspect
Generate email by first/last name and domain via Generect Email Generator
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Company domain without protocol (e.g., generect.com) | |
| last_name | Yes | Last name of the person | |
| first_name | Yes | First name of the person | |
| timeout_ms | No | Request timeout in milliseconds |
get_lead_by_urlInspect
Get Lead by LinkedIn URL
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | LinkedIn profile URL (e.g., https://www.linkedin.com/in/username/) | |
| posts | No | Include posts data | |
| comments | No | Include comments data | |
| timeout_ms | No | Request timeout in milliseconds | |
| inexact_company | No | Allow inexact company matching | |
| people_also_viewed | No | Include people also viewed |
healthInspect
Health check Generect API via a quick lead-by-link request
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | LinkedIn profile URL to validate (defaults to a public profile) | |
| timeout_ms | No | Request timeout in milliseconds |
search_companiesInspect
Search for companies by ICP filters
| Name | Required | Description | Default |
|---|---|---|---|
| compact | No | Return compact summary instead of full JSON | |
| keywords | No | Keywords | |
| max_items | No | Maximum items to include in response (local trim) | |
| headcounts | No | Headcount ranges | |
| industries | No | Industries | |
| timeout_ms | No | Request timeout in milliseconds | |
| company_types | No | Company types | |
| get_max_companies | No | Get maximum companies | |
| fallback_from_leads | No | If no companies, derive from leads by keywords |
search_leadsInspect
Search for leads by ICP filters
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Number of results to return | |
| offset | No | Offset for pagination | |
| compact | No | Return compact summary instead of full JSON | |
| industry | No | Industry filter (e.g., Technology, Healthcare) | |
| location | No | Location filter (e.g., San Francisco, New York) | |
| job_title | No | Job title filter (e.g., CEO, CTO, Engineer) | |
| max_items | No | Maximum items to include in response (local trim) | |
| company_id | No | LinkedIn company id | |
| timeout_ms | No | Request timeout in milliseconds | |
| company_link | No | LinkedIn company URL | |
| company_name | No | Company name |
Verify Ownership
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [
{
"email": "your-email@example.com"
}
]
}The email address must match the email associated with your Glama account. Once verified, the connector will appear as claimed by you.
Sign in to verify ownershipControl your server's listing on Glama, including description and metadata
Receive usage reports showing how your server is being used
Get monitoring and health status updates for your server
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!