> **Building with AI coding agents?** Install the authstack plugin with one command. This equips your agent with accurate Scalekit implementation patterns.
>
> **Recommended** (the `-y` flags skip prompts, so the command runs without an interactive terminal):
> ```bash
> npx -y @scalekit-inc/cli setup -y
> ```
>
> Global:
> ```bash
> npm install -g @scalekit-inc/cli
> scalekit setup -y
> ```
>
> Supports Claude Code, Cursor, GitHub Copilot, Codex + skills for other Agent Skills-compatible agents in `~/.agents/skills`.
> Skills: integrate-agentkit, implement-saaskit, add-mcp-oauth, implement-sso, implement-scim.
> [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# Connect AI agents to the ContactOut MCP server

The ContactOut MCP connector routes your AI agent's tool calls to ContactOut's own MCP server through Scalekit. Each user signs in to ContactOut once, and Scalekit stores and refreshes their tokens, so your agent never handles credentials. It comes with 15 tools.

**Authentication:** OAuth 2.1/DCR
**Categories:** CRM & Sales
**Tools:** 15: 15 read, 0 write, 0 destructive
**Users sign in with:** OAuth
**OAuth app:** Your own ContactOut MCP server app
**Built by:** Vendor MCP
**Try it:** [Playground in the Scalekit dashboard](https://app.scalekit.com/ws/signup?sk_intent=playground&provider=CONTACTOUTMCP)

## Setup

1. ### Install the SDK

   **Node.js**

   ```bash
   npm install @scalekit-sdk/node dotenv
   ```

   **Python**

   ```bash
   pip install scalekit-sdk-python python-dotenv
   ```

2. ### Set your credentials

   Add your Scalekit credentials to your `.env` file. Find values in **[app.scalekit.com](https://app.scalekit.com)** > **Developers** > **API Credentials**.

   ```sh title=".env"
   SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
   SCALEKIT_CLIENT_ID=<your-client-id>
   SCALEKIT_CLIENT_SECRET=<your-client-secret>
   ```

3. ### Create the ContactOut MCP connection

   In **AgentKit > Connections**, create a ContactOut MCP connection and copy its redirect URI. The name you give it is the `connection_name` your code passes. See [Configure connections](/agentkit/connections/).

4. ### Register an OAuth app

   ContactOut MCP server connections use your own OAuth app. Register one with ContactOut MCP server and add the redirect URI you copied.

   Then enter the app's Client ID and Client Secret on the ContactOut MCP connection.

5. ### Authorize a user and make your first call

   **Node.js** (`quickstart.mts`)

   ```typescript
   import { ScalekitClient } from '@scalekit-sdk/node'
   import 'dotenv/config'
   import { createInterface } from 'node:readline/promises'

   const scalekit = new ScalekitClient(
     process.env.SCALEKIT_ENVIRONMENT_URL,
     process.env.SCALEKIT_CLIENT_ID,
     process.env.SCALEKIT_CLIENT_SECRET,
   )
   const actions = scalekit.actions

   const connector = 'contactoutmcp'
   const identifier = 'user_123'

   // Generate an authorization link for the user
   const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
   console.log('Authorize ContactOut MCP:', link)
   const rl = createInterface({ input: process.stdin, output: process.stdout })
   await rl.question('Press Enter after authorizing...')
   rl.close()

   // Make your first call
   const result = await actions.executeTool({
     connector,
     identifier,
     toolName: 'contactoutmcp_company_information_from_domain',
     toolInput: {},
   })
   console.log(result)
   ```

   ```bash
   npx tsx quickstart.mts
   ```

   **Python** (`quickstart.py`)

   ```python
   import os
   from scalekit import ScalekitClient
   from dotenv import load_dotenv
   load_dotenv()

   scalekit_client = ScalekitClient(
       env_url=os.getenv("SCALEKIT_ENVIRONMENT_URL"),
       client_id=os.getenv("SCALEKIT_CLIENT_ID"),
       client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),
   )
   actions = scalekit_client.actions

   connection_name = "contactoutmcp"
   identifier = "user_123"

   # Generate an authorization link for the user
   link_response = actions.get_authorization_link(
       connection_name=connection_name,
       identifier=identifier,
   )
   print("Authorize ContactOut MCP:", link_response.link)
   input("Press Enter after authorizing...")

   # Make your first call
   result = actions.execute_tool(
       tool_input={},
       tool_name="contactoutmcp_company_information_from_domain",
       connection_name=connection_name,
       identifier=identifier,
   )
   print(result)
   ```

   ```bash
   python quickstart.py
   ```

   Each user signs in once. See [Authorize a user](/agentkit/tools/authorize/) for the full flow and statuses.

## Tools

Pass the exact name to `execute_tool`, with an input like each tool's example. To ask for a tool that's missing, use the [request form](https://scalekitsupport.portal.usepylon.com/forms/request-a-connector-tool).

**Node.js**

```typescript
const result = await actions.executeTool({
  toolName: 'contactoutmcp_company_information_from_domain',
  toolInput: {},
  connector: 'contactoutmcp',
  identifier: 'user_123',
})
```

**Python**

```python
result = actions.execute_tool(
    tool_name="contactoutmcp_company_information_from_domain",
    tool_input={},
    connection_name="contactoutmcp",
    identifier="user_123",
)
```

`result.data` is the app's response as JSON, and `result.execution_id` (`executionId` in Node.js) is the ID of the call.

### `contactoutmcp_company_information_from_domain`

Company Information from Domain · Read-only

Get company information based on given input domains.

Cost: Consumes 1 search credit for each company found.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `domains` (`array`, optional): Domain names to look up (e.g. `example.com`). Up to 30 entries.

Example input: `{}`

### `contactoutmcp_company_search`

Company Search · Read-only

Get company profiles matching the search criteria.

Cost: Consumes 1 search credit for each company returned.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `domain` (`array`, optional): Company website domains
- `hq_only` (`boolean`, optional): Filter search locations by headquarters only
- `industry` (`array`, optional): Industries; supports boolean expressions (OR, AND, NOT) with parentheses.
- `linkedin_url` (`array`, optional): Company LinkedIn identifiers: full URL, slug (`contactout`), numeric id (`27927`), etc. Up to 25; Cannot be used with other search filters.
- `location` (`array`, optional): Locations to match
- `max_revenue` (`integer`, optional): Maximum annual revenue in whole dollars (same allowed values as `min_revenue`; must be greater than `min_revenue` when both are set). One of: `0`, `1000000`, `5000000`, `10000000`, `50000000`, `100000000`, `250000000`, `500000000`, `1000000000`.
- `min_revenue` (`integer`, optional): Minimum annual revenue in whole dollars. Allowed values: 0, 1_000_000, 5_000_000, 10_000_000, 50_000_000, 100_000_000, 250_000_000, 500_000_000, 1_000_000_000. One of: `0`, `1000000`, `5000000`, `10000000`, `50000000`, `100000000`, `250000000`, `500000000`, `1000000000`.
- `name` (`array`, optional): Company names to match
- `page` (`integer`, optional): Provides results for the given page
- `size` (`array`, optional): Employee-count bucket codes: `1_10`, `11_50`, `51_200`, `201_500`, `501_1000`, `1001_5000`, `5001_10000`, `10001` (10,000+ employees).
- `year_founded_from` (`integer`, optional): Minimum year founded of the company; not before 1985.
- `year_founded_to` (`integer`, optional): Maximum year founded of the company (not after the current year). Use together with `year_founded_from`.

Example input: `{}`

### `contactoutmcp_contact_info_from_linkedin_profile`

Contact Info from LinkedIn Profile · Read-only

Get contact details for a single LinkedIn profile. Requesting real-time work emails via `email_type=work` may increase response time. Real-time verified `work_email` is **not** included unless you pass `email_type` accordingly.

LinkedIn URLs from Sales Navigator or Recruiter are not supported.

If `email_type` is not specified in the request, the response includes both personal and work emails. However, real-time verification is only performed when `email_type=work` is explicitly included, which may yield more work email results but can increase response time.

Cost: Consumes 1 email credit if email is found and 1 phone credit if phone number is found (and `include_phone` is set to `true`).

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `email_type` (`string`, optional): `email_type=personal` — only personal emails. `email_type=work` — only work emails. `email_type=personal,work` — both. `email_type=none` — no emails and no email credits. When omitted, both personal and work emails are returned.
- `include_phone` (`boolean`, optional): If true, include phone numbers in the response (uses phone credits when numbers are found).
- `profile` (`string`, optional): The fully formed URL of the LinkedIn profile. URL must begin with `http` and must contain `linkedin.com/in/` or `linkedin.com/pub/`

Example input: `{}`

### `contactoutmcp_decision_makers`

Decision Makers · Read-only

Get profiles of key decision makers within a specified company.

**At least one** of `linkedin_url`, `domain`, or `name` is required. You may pass any combination of these to identify the company.

Cost: Consumes 1 search credit for each profile returned. Consumes 1 email/phone credit for every profile where email/phone info is found, if `reveal_info=true` is specified.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `domain` (`string`, optional): The domain name of the company's website, e.g. example.com
- `linkedin_url` (`string`, optional): The fully formed URL of the company's LinkedIn profile. URL must begin with http and must contain linkedin.com/company/. Accepts both the numeric or string version of the URL, e.g. `https://linkedin.com/company/contactout` or `https://linkedin.com/company/27090845`
- `name` (`string`, optional): The name of the company
- `page` (`integer`, optional): Provides results for the given page
- `reveal_info` (`boolean`, optional): If true, `contact_info` includes emails and phone numbers and credits are charged accordingly.

Example input: `{}`

### `contactoutmcp_email_verifier`

Email Verifier · Read-only

Verify the deliverability of an email address.

`status` returns the status of the email address. Below are the possible values:

- `valid`: the email address is valid.
- `invalid`: the email address is not valid.
- `accept_all`: the email address is valid but any email address is accepted by the server.
- `disposable`: the email address comes from a disposable email service provider.
- `unknown`: we failed to verify the email address.

Cost: Consumes 1 "verifier" credit if result is either `valid`, `invalid` or `accept_all`

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `email` (`string`, optional): Email address

Example input: `{}`

### `contactoutmcp_get_api_usage_stats`

Get API Usage Stats · Read-only

Get ContactOut account stats for email, phone, and search for the requested month (`usage` in the JSON body).

Responses:
- `count` / `phone_count` / `search_count`: successful API requests that consumed that credit in the period.
- `quota` / `phone_quota` / `search_quota`: postpaid → monthly quota; prepaid → current prepaid balance.
- `remaining` / `phone_remaining` / `search_remaining`: postpaid only; credits left in the month vs period usage.
- `over_quota` / `phone_over_quota` / `search_over_quota`: postpaid only; amount over monthly quota when applicable.
- `is_prepaid`: boolean indicating if the account is prepaid (true) or postpaid (false).

Search (postpaid only): if the account has unlimited search credits, `search_quota` may be the string `unlimited` and `search_remaining` / `search_over_quota` may be omitted.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `period` (`string`, optional): Month to report in `YYYY-MM` format; defaults to current month if not provided

Example input: `{}`

### `contactoutmcp_linkedin_profile_from_email`

LinkedIn Profile from Email · Read-only

Get profile details for a single email address. The match rate is typically higher with a personal email address as they change less frequently. For work emails, if the domain is from a past employer, previous work experience is checked to ensure accurate identification.

Cost: Consumes 1 email credit if email is found and 1 phone credit if phone number is found.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `email` (`string`, optional): Email address
- `include` (`string`, optional): Extra data to return; currently supports `work_email`

Example input: `{}`

### `contactoutmcp_linkedin_profile_from_url`

LinkedIn Profile from URL · Read-only

Get profile details for a single linkedin profile URL. Only standard LinkedIn profile URLs are accepted—not Sales Navigator or Talent / Recruiter products. Returns email addresses, phone numbers, work experience, education, skills, and more associated with a LinkedIn profile.

Cost: Consumes 1 email credit if email is found and 1 phone credit if phone number is found. Consumes 1 search credit if `profile_only` is set to true or if there is no contact information available for the requested profile.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `profile` (`string`, optional): The fully formed URL of the LinkedIn profile. URL must begin with `http` and must contain `linkedin.com/in/` or `linkedin.com/pub/`
- `profile_only` (`boolean`, optional): If true, returns profile data without contact information.

Example input: `{}`

### `contactoutmcp_linkedin_url_from_email`

LinkedIn URL from Email · Read-only

Get LinkedIn profile url for a given email.

Cost: Consumes 1 email credit if profile is found.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `email` (`string`, optional): Email address

Example input: `{}`

### `contactoutmcp_people_count`

People Count · Read-only

Get the total count of profiles matching the search criteria.

Uses the same request fields as the `people-search` tool except do not send `page`, `data_types`, or `reveal_info` (they are not supported for counts).

Cost: Does not consume credits

Access: Only available to paid users

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `company` (`array`, optional): Company names to match
- `company_filter` (`string`, optional): `current` — match current company name. `past` — match any past company. `both` — match current or past experience.
- `company_size` (`array`, optional): Employee-count bucket codes: `1_10`, `11_50`, `51_200`, `201_500`, `501_1000`, `1001_5000`, `5001_10000`, `10001` (10,000+ employees).
- `current_company_only` (`boolean`, optional): If true, require a match on the current company name.
- `current_titles_only` (`boolean`, optional): If true, match the current job title only; if false, include past titles as well.
- `current_work_location` (`array`, optional): Cities or countries where the person currently works. Each entry supports boolean expressions (OR, AND, NOT).
- `detailed_education` (`boolean`, optional): If true, `education` returns structured objects (`school_name`, `degree`, `field_of_study`, `description`, dates, `url`, etc.); if false, returns simple text strings.
- `detailed_experience` (`boolean`, optional): If true, `experience` returns structured objects (`title`, `company_name`, `summary`, dates, `is_current`, `linkedin_url`, `logo_url`, etc.); if false, returns simple text strings.
- `domain` (`array`, optional): Company domains to match
- `education` (`array`, optional): Schools or degrees. Supports boolean expressions (OR, AND, NOT)
- `educations` (`array`, optional): Structured education filters. Provide at least one of `school_name`, `field_of_study`, or `location` per object. Each supports boolean expressions (OR, AND, NOT).
- `exclude_companies` (`array`, optional): Company names to exclude
- `exclude_job_titles` (`array`, optional): Job titles to exclude from results.
- `include_related_job_titles` (`boolean`, optional): If true, include related job titles in the match.
- `industry` (`array`, optional): Industries; supports boolean expressions (OR, AND, NOT).
- `job_function` (`array`, optional): Job functions (e.g. Engineering, Marketing, Sales, Finance); values must match supported job-function labels.
- `job_title` (`array`, optional): Job titles to match. Supports boolean expressions (OR, AND, NOT).
- `keyword` (`string`, optional): Returns profiles that contain the mentioned keyword anywhere in their profile. Supports boolean expressions (OR, AND, NOT).
- `languages` (`array`, optional): Language filters: each item has `language` and optionally `proficiency`. `language` supports boolean expressions (OR, AND, NOT).
- `location` (`array`, optional): Locations to match
- `location_radius` (`integer`, optional): Search radius in miles (1-500). Only works when `location` is provided and the location is a city / area. Filters profiles within the specified radius of the location.
- `match_experience` (`string`, optional): Allowed values: current, past, past_only, or both. `current` — `job_title` and `company` must match the current experience. `past` — match any past experience. `past_only` — match a past experience, excluding profiles that also have a current role at the same company. `both` — match current or past. When set, do not use `current_titles_only`, `company_filter`, or `current_company_only` (the request will be rejected).
- `name` (`string`, optional): Name of the profile
- `output_fields` (`array`, optional): This parameter controls which fields are included in the output. By default, all fields are returned.
                Use this to limit the output to only the fields you need, which can reduce token usage and cost.
                Allowed values: li_vanity, full_name, title, headline, company, company.name, company.website, company.headquarter, company.domain, company.size, location, industry, experience, education, skills, profile_picture_url.
- `past_work_location` (`array`, optional): Cities or countries where the person previously worked. Each entry supports boolean expressions (OR, AND, NOT).
- `recently_changed_jobs` (`boolean`, optional): Filter for profiles who recently changed jobs
- `seniority` (`array`, optional): Seniority levels to filter profiles by their career level`owner / founder` (Founder/Owner), `cxo` (C-suite), `vp` (Vice President), plus `partner`, `head`, `director`, `manager`, `senior`, `entry`, `intern`.
- `skills` (`array`, optional): Skills to match. Supports boolean expressions (OR, AND, NOT)
- `years_in_current_role` (`array`, optional): Tenure in current role as `X_Y` (e.g. `1_3` = 1–3 years). Multiple ranges are OR’d.
- `years_of_experience` (`array`, optional): Total experience ranges as `X_Y` (e.g. `2_5` = 2–5 years). Multiple ranges are OR’d.

Example input: `{}`

### `contactoutmcp_people_enrich`

People Enrich · Read-only

Get profile details using a combination of data points such as name, email, phone, LinkedIn URL, company information, education, and location. This tool provides flexible enrichment by allowing you to provide multiple identifying parameters to find and enrich a person's profile.

By default, this endpoint returns profile information without contact details. To include contact information such as email addresses and phone numbers, you must specify the include parameter with the desired contact types.

Matching rules: supply one primary identifier (`linkedin_url`, `email`, or `phone`) **or** a name (`full_name`, or `first_name` + `last_name`) together with at least one secondary field among `company`, `company_domain`, `job_title`, `location`, or `education`.

Contact details only appear when you list them in `include` (`work_email`, `personal_email`, `phone`).

Cost: Consumes 1 search credit if a profile was found. Consumes 1 email credit if email is found and 1 phone credit if phone number is found.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `company` (`array`, optional): Company names (up to 10)
- `company_domain` (`array`, optional): Company domains (up to 10)
- `education` (`array`, optional): Educational institutions (up to 10).
- `email` (`string`, optional): Email address
- `first_name` (`string`, optional): First name (must be used with last_name)
- `full_name` (`string`, optional): Full name of the person
- `include` (`array`, optional): Data to include: `work_email`, `personal_email`, `phone`
- `job_title` (`string`, optional): Job title
- `last_name` (`string`, optional): Last name (must be used with first_name)
- `linkedin_url` (`string`, optional): LinkedIn profile URL
- `location` (`string`, optional): Location/city
- `phone` (`string`, optional): Phone number

Example input: `{}`

### `contactoutmcp_people_search`

People Search · Read-only

Get profiles matching the search criteria.

Some parameters accept boolean expressions using OR, AND, and NOT. Use parentheses so grouping is explicit (e.g. `(React AND Python) NOT Java`).

For example, if you are looking for profiles who have the skills ReactJS and Python, but not Java, you can format the skills parameter as: { "skills": ["(ReactJS AND Python) NOT Java"] }. Always add brackets to ensure the boolean logic is applied correctly.

Supported operators: OR, AND, NOT.

Responses contain meta information and the matching list of profiles. Each profile contains the information like title, headline, company details, experience, skills etc. It also lists the contact availability and contact information fields.

Cost: Consumes 1 search credit for each profile returned. Consumes 1 email/phone credit for every profile where email/phone info is found, if `reveal_info=true` is specified.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `company` (`array`, optional): Company names to match
- `company_filter` (`string`, optional): `current` — match current company name. `past` — match any past company. `both` — match current or past experience.
- `company_size` (`array`, optional): Employee-count bucket codes: `1_10`, `11_50`, `51_200`, `201_500`, `501_1000`, `1001_5000`, `5001_10000`, `10001` (10,000+ employees).
- `current_company_only` (`boolean`, optional): If true, require a match on the current company name.
- `current_titles_only` (`boolean`, optional): If true, match the current job title only; if false, include past titles as well.
- `current_work_location` (`array`, optional): Cities or countries where the person currently works. Each entry supports boolean expressions (OR, AND, NOT).
- `data_types` (`array`, optional): Require at least one of: `personal_email`, `work_email`, `phone`.
- `detailed_education` (`boolean`, optional): If true, `education` returns structured objects (`school_name`, `degree`, `field_of_study`, `description`, dates, `url`, etc.); if false, returns simple text strings.
- `detailed_experience` (`boolean`, optional): If true, `experience` returns structured objects (`title`, `company_name`, `summary`, dates, `is_current`, `linkedin_url`, `logo_url`, etc.); if false, returns simple text strings.
- `domain` (`array`, optional): Company domains to match
- `education` (`array`, optional): Schools or degrees. Supports boolean expressions (OR, AND, NOT)
- `educations` (`array`, optional): Structured education filters. Provide at least one of `school_name`, `field_of_study`, or `location` per object. Each supports boolean expressions (OR, AND, NOT).
- `exclude_companies` (`array`, optional): Company names to exclude
- `exclude_job_titles` (`array`, optional): Job titles to exclude from results.
- `include_related_job_titles` (`boolean`, optional): If true, include related job titles in the match.
- `industry` (`array`, optional): Industries; supports boolean expressions (OR, AND, NOT).
- `job_function` (`array`, optional): Job functions (e.g. Engineering, Marketing, Sales, Finance); values must match supported job-function labels.
- `job_title` (`array`, optional): Job titles to match. Supports boolean expressions (OR, AND, NOT).
- `keyword` (`string`, optional): Returns profiles that contain the mentioned keyword anywhere in their profile. Supports boolean expressions (OR, AND, NOT).
- `languages` (`array`, optional): Language filters: each item has `language` and optionally `proficiency`. `language` supports boolean expressions (OR, AND, NOT).
- `location` (`array`, optional): Locations to match
- `location_radius` (`integer`, optional): Search radius in miles (1-500). Only works when `location` is provided and the location is a city / area. Filters profiles within the specified radius of the location.
- `match_experience` (`string`, optional): Allowed values: current, past, past_only, or both. `current` — `job_title` and `company` must match the current experience. `past` — match any past experience. `past_only` — match a past experience, excluding profiles that also have a current role at the same company. `both` — match current or past. When set, do not use `current_titles_only`, `company_filter`, or `current_company_only` (the request will be rejected).
- `name` (`string`, optional): Name of the profile
- `output_fields` (`array`, optional): This parameter controls which fields are included in the output. By default, all fields are returned.
                Use this to limit the output to only the fields you need, which can reduce token usage and cost.
                Allowed values: li_vanity, full_name, title, headline, company, company.name, company.website, company.headquarter, company.domain, company.size, location, industry, experience, education, skills, profile_picture_url.
- `page` (`integer`, optional): Provides results for the given page
- `past_work_location` (`array`, optional): Cities or countries where the person previously worked. Each entry supports boolean expressions (OR, AND, NOT).
- `recently_changed_jobs` (`boolean`, optional): Filter for profiles who recently changed jobs
- `reveal_info` (`boolean`, optional): If true, `contact_info` includes emails and phone numbers and credits are charged accordingly.
- `seniority` (`array`, optional): Seniority levels to filter profiles by their career level`owner / founder` (Founder/Owner), `cxo` (C-suite), `vp` (Vice President), plus `partner`, `head`, `director`, `manager`, `senior`, `entry`, `intern`.
- `skills` (`array`, optional): Skills to match. Supports boolean expressions (OR, AND, NOT)
- `years_in_current_role` (`array`, optional): Tenure in current role as `X_Y` (e.g. `1_3` = 1–3 years). Multiple ranges are OR’d.
- `years_of_experience` (`array`, optional): Total experience ranges as `X_Y` (e.g. `2_5` = 2–5 years). Multiple ranges are OR’d.

Example input: `{}`

### `contactoutmcp_personal_email_checker`

Personal Email Checker · Read-only

Get personal email availability status for a single Linkedin profile

Cost: Does not consume credits

Access: Only available to paid users

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `profile` (`string`, optional): The fully formed URL of the LinkedIn profile. URL must begin with `http` and must contain `linkedin.com/in/` or `linkedin.com/pub/`

Example input: `{}`

### `contactoutmcp_phone_checker`

Phone Checker · Read-only

Get phone availability status for a single LinkedIn profile

Cost: Does not consume credits

Access: Only available to paid users

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `profile` (`string`, optional): The fully formed URL of the LinkedIn profile. URL must begin with `http` and must contain `linkedin.com/in/` or `linkedin.com/pub/`

Example input: `{}`

### `contactoutmcp_work_email_checker`

Work Email Checker · Read-only

Get work email availability status for a single LinkedIn profile

Response: `profile.email` returns true if work email is present. `profile.email_status` returns whether the email is verified or unverified, and may be `Verified`, `Unverified`, or `null`.

Cost: Does not consume credits

Access: Only available to paid users

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `profile` (`string`, optional): The fully formed URL of the LinkedIn profile. URL must begin with `http` and must contain `linkedin.com/in/` or `linkedin.com/pub/`.

Example input: `{}`

## Related

Other CRM & Sales connectors ([all 174](/agentkit/connectors/?category=crm-sales)):

- [Salesforce](/agentkit/connectors/salesforce/): Scalekit connector, OAuth, 74 tools
- [HubSpot](/agentkit/connectors/hubspot/): Scalekit connector, OAuth, 457 tools
- [Close](/agentkit/connectors/close/): Scalekit connector, OAuth, 103 tools


---

## More Scalekit documentation

| Resource | What it contains | When to use it |
|----------|-----------------|----------------|
| [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content |
| [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas |
| [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |
