# catchy-me (remote · app.catchy-me.com)

Find B2B leads on LinkedIn that match your ICP, with verified facts and a first message for each.

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `app.catchy-me.com`: 65/100 (this document), [markdown](https://verifymcp.io/servers/com-catchy-me-catchy-me/app.md), [page](https://verifymcp.io/servers/com-catchy-me-catchy-me/app)

## Channel facts

- Endpoint: `https://app.catchy-me.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (cancel_subscription).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 9799 tokens (~148/item across 66 items; 66 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 86/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 57% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 67 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the catchy-me MCP server?

catchy-me is a hosted endpoint at https://app.catchy-me.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-catchy-me-catchy-me 'https://app.catchy-me.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-catchy-me-catchy-me": {
      "url": "https://app.catchy-me.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-catchy-me-catchy-me": {
      "type": "http",
      "url": "https://app.catchy-me.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-catchy-me-catchy-me]
url = "https://app.catchy-me.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-catchy-me-catchy-me": {
      "type": "remote",
      "url": "https://app.catchy-me.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-catchy-me-catchy-me --url 'https://app.catchy-me.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-catchy-me-catchy-me:
    url: "https://app.catchy-me.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-catchy-me-catchy-me": {
      "Transport": "http",
      "Url": "https://app.catchy-me.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-catchy-me-catchy-me -t streamable-http -u 'https://app.catchy-me.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-catchy-me-catchy-me": {
      "type": "http",
      "url": "https://app.catchy-me.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 63, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] The server changed its declared name: catchy → catchy-me
- [security] Tool “accept_legal” rewrote its description, which is the text the model reads
- [security] Tool “catchy_info” rewrote its description, which is the text the model reads
- [security] Tool “get_account” rewrote its description, which is the text the model reads
- [security] Tool “list_plans” rewrote its description, which is the text the model reads
- [security] Tool “sign_in” rewrote its description, which is the text the model reads
- [security] Tool “sign_up” rewrote its description, which is the text the model reads
- [security] Tool “subscribe” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “confirm_sign_up” reworded the description of “lang”
- [cosmetic] “request_password_reset” reworded the description of “lang”
- [cosmetic] “resend_sign_up_code” reworded the description of “lang”
- [cosmetic] “reset_password” reworded the description of “lang”
- [cosmetic] “sign_in” reworded the description of “lang”
- [cosmetic] “sign_up” reworded the description of “lang”
- [cosmetic] Tool “catchy_info” changed its title: About Catchy → About catchy-me
- [cosmetic] Tool “sign_up” changed its title: Create a Catchy account → Create a catchy-me account

### 2026-11-17 (score 63)

First indexed and scored.

## MCP tools (66)

### `catchy_info` (~70 tokens)

About catchy-me

What catchy-me is and how it works: lead search with facts and AI outreach, plans, briefs and credits, how to connect this MCP server (OAuth or an API key), how an agent signs up by itself, and the links to the Terms of Use and the Privacy Policy. No sign-in needed.

### `sign_up` (~213 tokens)

Create a catchy-me account

Registers a new catchy-me account and emails a 6-digit code to confirm it (then confirm_sign_up). Set accept_terms=true ONLY after the user has read and agreed to the Terms of Use and the Privacy Policy (their links: catchy_info terms_of_use / privacy_policy) — ask them first. Without a password one is generated and returned once: give it to the user. Returns signup_token for confirm_sign_up. [REST: POST /api/auth/register/start]

Input parameters:

- `accept_terms` (boolean, required): The user agreed to the Terms of Use and the Privacy Policy.
- `email` (string, required)
- `invite` (string): An invite code, when registration is by invitation.
- `lang` (string): The account's language: ru, en, es (Spanish), de (German), fr (French), pt (Brazilian Portuguese) or ja (Japanese); the messages, the emails and the texts of its searches. Default en.
- `name` (string, required)
- `password` (string)

### `resend_sign_up_code` (~108 tokens)

Send the sign-up code again

Sends a new code for a pending registration (at most once a minute; the answer is the same whether or not one is pending). [REST: POST /api/auth/register/resend]

Input parameters:

- `email` (string, required)
- `lang` (string): The account's language: ru, en, es (Spanish), de (German), fr (French), pt (Brazilian Portuguese) or ja (Japanese); the messages, the emails and the texts of its searches. Default en.

### `confirm_sign_up` (~178 tokens)

Confirm the account and get an API key

Confirms the registration with the emailed code and the signup_token of sign_up, and returns an API key for this MCP server (shown once). [REST: POST /api/auth/register/verify]

Input parameters:

- `code` (string, required)
- `email` (string, required)
- `key_access` (string)
- `key_days` (integer|null): Lifetime of the key in days; null = no limit. Default 365.
- `key_name` (string): Name of the API key in Settings (default «MCP agent»).
- `lang` (string): The account's language: ru, en, es (Spanish), de (German), fr (French), pt (Brazilian Portuguese) or ja (Japanese); the messages, the emails and the texts of its searches. Default en.
- `signup_token` (string, required)

### `sign_in` (~166 tokens)

Sign in and get an API key

An existing catchy-me account: email and password -> an API key for this MCP server (shown once). The web's login limits apply. [REST: POST /api/auth/login]

Input parameters:

- `email` (string, required)
- `key_access` (string)
- `key_days` (integer|null): Lifetime of the key in days; null = no limit. Default 365.
- `key_name` (string): Name of the API key in Settings (default «MCP agent»).
- `lang` (string): The account's language: ru, en, es (Spanish), de (German), fr (French), pt (Brazilian Portuguese) or ja (Japanese); the messages, the emails and the texts of its searches. Default en.
- `password` (string, required)

### `request_password_reset` (~107 tokens)

Forgot the password

Emails a code to reset the password of an account (the answer is the same whether or not the account exists). Then reset_password. [REST: POST /api/auth/password/forgot]

Input parameters:

- `email` (string, required)
- `lang` (string): The account's language: ru, en, es (Spanish), de (German), fr (French), pt (Brazilian Portuguese) or ja (Japanese); the messages, the emails and the texts of its searches. Default en.

### `reset_password` (~114 tokens)

Set a new password

Sets a new password with the emailed code (every session of the account ends). Then sign_in with it. [REST: POST /api/auth/password/reset]

Input parameters:

- `code` (string, required)
- `email` (string, required)
- `lang` (string): The account's language: ru, en, es (Spanish), de (German), fr (French), pt (Brazilian Portuguese) or ja (Japanese); the messages, the emails and the texts of its searches. Default en.
- `password` (string, required)

### `get_account` (~120 tokens)

Account, plan and balance

The signed-in catchy-me account: name, email, language, plan («тариф»: code, status, period end), briefs («брифы») left this period and when they renew, the free brief, the balance in whole credits (available = balance minus holds of running work) and the search limits (max leads per search). Call it first to know what the user can do: starting a search or an outreach needs a plan or credits, and each new setup spends one brief. [REST: GET /api/account, GET /api/config]

### `accept_legal` (~135 tokens)

Accept the updated Terms and Privacy Policy

Records that the user accepted the current Terms of Use (https://catchy-me.com/terms) and took note of the current Privacy Policy (https://catchy-me.com/privacy). Use it when a tool answered legal_pending: first show the user both links and ask whether they accept the updated Terms; call it with confirm=true ONLY after the user explicitly agreed — never on your own. The other tools work again after it. The user may instead accept them in the catchy-me web app. [REST: (as POST /api/legal/accept)]

Input parameters:

- `confirm` (boolean, required): The user read the links and explicitly agreed.

### `get_balance_history` (~63 tokens)

Balance history

The account's balance lines, newest first: top-ups, grants and charges (search, facts on request, outreach) in whole credits, with the search each charge was for. [REST: GET /api/account/balance/history]

Input parameters:

- `limit` (integer)

### `list_plans` (~61 tokens)

Plans (tariffs)

The tariff catalog: each plan's monthly price (USD, RUB), credits and briefs a period. A subscription is bought with subscribe (a LavaTop payment link the user opens and pays). No sign-in needed. [REST: GET /api/plans]

### `suggest_company_description` (~207 tokens)

Describe the company (onboarding step 1)

Step 1 of a new search («Компания»): reads the user's company site (url) or a text about it and writes a short plain-language description of what it sells, to whom and why it matters. The user may edit it before create_search. Takes up to a minute. Part of a new search's onboarding: the first assistant call of an onboarding spends one brief (a free account has one search brief and may call each assistant once); pass the returned onboarding_id to the next calls and to create_search. [REST: POST /api/assist/company]

Input parameters:

- `onboarding_id` (string): The onboarding id that ties the assistant calls and create_search into ONE brief. Omit it on the first call: the answer gives one; pass it to every later assistant call and to create_search of the sa…
- `text` (string): Or: a text about the company.
- `url` (string): The company's site, e.g. acme.com.

### `suggest_goals` (~171 tokens)

Suggest outreach goals (onboarding step 2)

Step 2 («Цель»): four goals for the outreach to the people found (e.g. invite to a call), from the company description. The user picks or writes one. Part of a new search's onboarding: the first assistant call of an onboarding spends one brief (a free account has one search brief and may call each assistant once); pass the returned onboarding_id to the next calls and to create_search. [REST: POST /api/assist/goals]

Input parameters:

- `company` (string, required): The company description (step 1).
- `onboarding_id` (string): The onboarding id that ties the assistant calls and create_search into ONE brief. Omit it on the first call: the answer gives one; pass it to every later assistant call and to create_search of the sa…

### `suggest_audiences` (~187 tokens)

Suggest audiences (onboarding step 3)

Step 3 («Кому пишем»): three customer profiles (ICP) to search for, from the company and the goal; each with a short title, the profile text and why. The chosen text is the `icp` of create_search. Part of a new search's onboarding: the first assistant call of an onboarding spends one brief (a free account has one search brief and may call each assistant once); pass the returned onboarding_id to the next calls and to create_search. [REST: POST /api/assist/audiences]

Input parameters:

- `company` (string, required)
- `goal` (string, required)
- `onboarding_id` (string): The onboarding id that ties the assistant calls and create_search into ONE brief. Omit it on the first call: the answer gives one; pass it to every later assistant call and to create_search of the sa…

### `parse_exclusions_file` (~209 tokens)

Read people to exclude from a file

«Исключить уже знакомых»: a CSV, TSV, TXT or XLSX file with the people the user already knows (LinkedIn links in any column) -> the profile links found (pass them as exclude_urls of create_search) and the company pages (exclude_company_urls). Part of a new search's onboarding: the first assistant call of an onboarding spends one brief (a free account has one search brief and may call each assistant once); pass the returned onboarding_id to the next calls and to create_search. [REST: POST /api/assist/exclusions]

Input parameters:

- `data_base64` (string, required): The file's bytes, base64.
- `file_name` (string, required): The file's name with its extension.
- `onboarding_id` (string): The onboarding id that ties the assistant calls and create_search into ONE brief. Omit it on the first call: the answer gives one; pass it to every later assistant call and to create_search of the sa…

### `extract_site_file_text` (~185 tokens)

Read the company text from a file

When the site cannot be read: a saved page (HTML), a PDF or a text file -> its text, to describe the company with suggest_company_description(text=...). Part of a new search's onboarding: the first assistant call of an onboarding spends one brief (a free account has one search brief and may call each assistant once); pass the returned onboarding_id to the next calls and to create_search. [REST: POST /api/assist/site_file]

Input parameters:

- `data_base64` (string, required): The file's bytes, base64.
- `file_name` (string, required): The file's name with its extension.
- `onboarding_id` (string): The onboarding id that ties the assistant calls and create_search into ONE brief. Omit it on the first call: the answer gives one; pass it to every later assistant call and to create_search of the sa…

### `list_previous_onboardings` (~57 tokens)

Earlier onboardings

The user's earlier search onboardings (company, goal, audience), newest first. A new search can start from one of them (get_onboarding_prefill) without the assistants. [REST: GET /api/onboardings]

### `get_onboarding_prefill` (~94 tokens)

Fill from an earlier onboarding

The answers of an earlier onboarding (company, goal, icp, language) to reuse in create_search; pass its id as source_task there too, so the search plan made then is reused when the brief stays the same. [REST: GET /api/onboardings/{id}]

Input parameters:

- `task_id` (string, required): The search id (task id), e.g. from list_searches or create_search.

### `list_exclusion_sources` (~49 tokens)

Earlier searches to exclude

The user's earlier searches whose people can be left out of a new one (exclude_tasks of create_search): all analysed or only the leads. [REST: GET /api/exclusions/sources]

### `create_search` (~323 tokens)

Create a lead search

Creates a new lead search («поиск лидов») from the onboarding answers and starts compiling its requirements (~1-2 minutes; nothing is charged in credits, but it spends the onboarding's brief if no assistant did). Then poll get_search every 20-30 s until status is `ready`, review the spec with the user (get_search detail=spec), and only then quote and run it. company and icp are required. [REST: POST /api/tasks]

Input parameters:

- `company` (string, required): What the user's company does (step 1).
- `exclude_companies` (boolean): Also leave out the companies of those people.
- `exclude_company_urls` (array)
- `exclude_scope` (string): From those searches: everyone analysed (all) or only leads.
- `exclude_tasks` (array): Earlier searches whose people to leave out.
- `exclude_urls` (array): LinkedIn profile links of people to leave out.
- `goal` (string): What the outreach should achieve (step 2).
- `icp` (string, required): Whom to find: the customer profile (step 3).
- `language` (string): Language of the outreach messages (default english).
- `onboarding_id` (string): The onboarding id that ties the assistant calls and create_search into ONE brief. Omit it on the first call: the answer gives one; pass it to every later assistant call and to create_search of the sa…
- `source_task` (string): The earlier onboarding this one was filled from (get_onboarding_prefill).

### `get_subscription` (~77 tokens)

Current subscription

The account's subscription: plan, status (active, past_due, cancelling, ended), who manages it (admin or lavatop), price and currency, period end, whether it renews, credits and briefs a period. null: no subscription (list_plans, then subscribe). [REST: GET /api/billing/subscription]

### `subscribe` (~200 tokens)

Buy a plan (payment link)

Creates a LavaTop payment for a monthly plan (trial, start, growth, scale; prices in list_plans) and returns its payment_url and order id. Confirm the plan, price and currency with the user first. GIVE THE LINK TO THE USER: a person pays on LavaTop's page by card, SBP or PayPal (an agent cannot). Currency is also the method: RUB — Russian cards and SBP; USD — foreign cards, PayPal, Apple Pay (Russian cards pay only in RUB). A USD link lives 15 minutes, a RUB link 24 hours. A plan not yet sold online answers plan_unavailable: the user writes to support. Then poll get_payment_status every 15-30 s until paid; the plan's credits and briefs arrive with the payment and renew monthly until cancel_subscription. [REST: POST /api/billing/checkout]

Input parameters:

- `currency` (string)
- `plan` (string, required)

### `get_payment_status` (~65 tokens)

Payment status

The status of a payment order made by subscribe: pending, paid, failed, expired, cancelled. When paid, get_account shows the plan and credits. [REST: GET /api/billing/orders/{id}]

Input parameters:

- `order_id` (string, required): The order id from subscribe.

### `cancel_subscription` (~65 tokens)

Cancel the subscription

Stops the renewal of a LavaTop subscription: the plan stays until the period's end and the credits stay on the balance after it. Ask the user to confirm and pass confirm=true. [REST: POST /api/billing/subscription/cancel]

Input parameters:

- `confirm` (boolean, required)

### `list_leads` (~136 tokens)

Leads of a search

The people of a search by kind: fit («Подходят»: the leads, in their order), partial («Частично»: some requirement not proven, with what was assumed), miss («Не подходят», with the reason). Compact rows; paginate with offset/limit. get_lead gives one person's dossier with facts. [REST: GET /api/tasks/{id}/leads?kind=]

Input parameters:

- `kind` (string)
- `limit` (integer)
- `offset` (integer)
- `task_id` (string, required): The search id (task id), e.g. from list_searches or create_search.

### `get_lead` (~115 tokens)

A lead's dossier

One person of a search: the profile card, the company, the verdict and why they fit, each criterion's status with how it was checked, and the facts found (dated, with source links) — the material for a personal message. [REST: GET /api/tasks/{id}/candidates/{cid}]

Input parameters:

- `cid` (string, required): The person's id (cid) from list_leads.
- `task_id` (string, required): The search id (task id), e.g. from list_searches or create_search.

### `quote_facts_on_request` (~149 tokens)

Price of facts on request / move to fit

After a search: the price in credits of finding facts for chosen partial people and moving them to fit («перевести в подходящие», promote=true), or facts only (promote=false). Free, changes nothing; the answer's `credits` is the confirm_credits of start_facts_on_request, `skipped` the people it does not take and why. [REST: POST /api/tasks/{id}/manual/quote]

Input parameters:

- `cids` (array, required): Person ids (cid) from list_leads.
- `promote` (boolean)
- `task_id` (string, required): The search id (task id), e.g. from list_searches or create_search.

### `start_facts_on_request` (~146 tokens)

Start facts on request (spends credits)

SPENDS CREDITS: quote_facts_on_request first, show the price to the user and after their yes pass its `credits` as confirm_credits. The work runs in the background; poll get_search / list_leads. [REST: POST /api/tasks/{id}/manual]

Input parameters:

- `cids` (array, required): Person ids (cid) from list_leads.
- `confirm_credits` (integer, required): The price in credits the matching quote returned, shown to the user and confirmed by them.
- `promote` (boolean)
- `task_id` (string, required): The search id (task id), e.g. from list_searches or create_search.

### `demote_lead` (~99 tokens)

Move fit leads to partial

After a search: moves chosen fit people to partial («в частично подходящие»), e.g. the user disagrees with the verdict. Free, at once. [REST: POST /api/tasks/{id}/demote]

Input parameters:

- `cids` (array, required): Person ids (cid) from list_leads.
- `task_id` (string, required): The search id (task id), e.g. from list_searches or create_search.

### `diagnose_search` (~120 tokens)

Why the leads are dear or ran out

The criteria revision («Изменить критерии»): while a search asks about a higher price, or when a finished search ran out of people, works out which criteria hold it back and proposes changes, each combination with its price in credits and the leads it may give. Takes up to ~75 s. Then revise_search with the chosen proposal ids. [REST: POST /api/tasks/{id}/revise/diagnose]

Input parameters:

- `task_id` (string, required): The search id (task id), e.g. from list_searches or create_search.

### `revise_search` (~187 tokens)

Apply criteria changes (spends credits)

Applies chosen proposals of diagnose_search. SPENDS CREDITS: show the price of that combination and pass it as confirm_credits after the user's yes, with the diagnosis' `version`. For a finished search whose people ran out, `more` (and stop_at_target) say how many more leads to find with the changes. [REST: POST /api/tasks/{id}/revise]

Input parameters:

- `accept` (array, required)
- `confirm_credits` (integer, required): The price in credits the matching quote returned, shown to the user and confirmed by them.
- `more` (integer)
- `stop_at_target` (boolean)
- `task_id` (string, required): The search id (task id), e.g. from list_searches or create_search.
- `version` (integer): The spec version from get_search (optional: protects against an edit made meanwhile in the web).

### `get_search_funnel` (~75 tokens)

Search funnel

A finished search's funnel in plain words: how many people were seen, checked, rejected and why, and how many became leads. [REST: GET /api/tasks/{id}/funnel]

Input parameters:

- `task_id` (string, required): The search id (task id), e.g. from list_searches or create_search.

### `export_search` (~122 tokens)

Export the leads (download link)

A download link for the search's leads as Excel (xlsx) or PDF: chosen kinds (default fit and partial), with the facts and the brief. The link works for one hour without signing in; give it to the user. [REST: GET /api/tasks/{id}/export.xlsx|pdf?kinds= (signed link /api/dl/{token})]

Input parameters:

- `format` (string)
- `kinds` (array)
- `task_id` (string, required): The search id (task id), e.g. from list_searches or create_search.

### `get_outreach` (~123 tokens)

Outreach desk

The outreach («Рассылка») of a finished search: the campaign (sender with its card, essence = offer / ask / tone / rules / language, the accounts, counts, the current generation, credits charged) and the fit people with their state (paginated), plus what to do next (`next`). [REST: GET /api/tasks/{id}/outreach]

Input parameters:

- `limit` (integer)
- `offset` (integer)
- `task_id` (string, required): The search id (task id), e.g. from list_searches or create_search.

### `list_outreach_presets` (~75 tokens)

Saved outreach setups

The user's saved outreach setups across searches (sender, offer, ask, language, accounts, source search), newest used first; new_outreach with preset_id copies one into a fresh generation. [REST: GET /api/outreach/presets]

Input parameters:

- `cursor` (string)
- `limit` (integer)

### `new_outreach` (~133 tokens)

Start a new outreach setup

A fresh outreach generation of the search: empty, or with this search's previous setup (reuse_previous) or a saved one (preset_id). Free; the first paid setup step of the generation spends one brief. [REST: POST /api/tasks/{id}/outreach/new]

Input parameters:

- `generation_id` (string): The outreach generation id (get_outreach campaign.generation.id); omitted: the current one.
- `preset_id` (string)
- `reuse_previous` (boolean)
- `task_id` (string, required): The search id (task id), e.g. from list_searches or create_search.

### `set_outreach_sender` (~153 tokens)

Set the sender

Who writes the messages: mode=linkedin with the sender's LinkedIn link (the profile and posts are analysed, about a minute), or mode=text with a few sentences about them. The first paid setup step of a generation spends its brief. Then poll get_outreach. [REST: PUT /api/tasks/{id}/outreach/sender]

Input parameters:

- `generation_id` (string): The outreach generation id (get_outreach campaign.generation.id); omitted: the current one.
- `linkedin_url` (string)
- `mode` (string, required)
- `task_id` (string, required): The search id (task id), e.g. from list_searches or create_search.
- `text` (string)

### `edit_sender_card` (~152 tokens)

Edit the sender card

Correct the sender's card the analysis made (name, role, company, voice = how they write, summary, background, interests). [REST: PATCH /api/tasks/{id}/outreach/sender/card]

Input parameters:

- `background` (array)
- `company` (string)
- `generation_id` (string): The outreach generation id (get_outreach campaign.generation.id); omitted: the current one.
- `interests` (array)
- `name` (string)
- `role` (string)
- `summary` (string)
- `task_id` (string, required): The search id (task id), e.g. from list_searches or create_search.
- `voice` (string)

### `suggest_outreach_essence` (~85 tokens)

Draft the offer

A draft of «Что предлагаем» (the offer) from the search's onboarding. Free for the user (it may spend the generation's brief). [REST: POST /api/tasks/{id}/outreach/essence/suggest]

Input parameters:

- `task_id` (string, required): The search id (task id), e.g. from list_searches or create_search.

### `set_outreach_essence` (~145 tokens)

Set the essence

«Суть»: offer (what we offer), ask (what we want from the person), optional tone and client_rules, and the message language. [REST: PUT /api/tasks/{id}/outreach/essence]

Input parameters:

- `ask` (string, required)
- `client_rules` (string)
- `generation_id` (string): The outreach generation id (get_outreach campaign.generation.id); omitted: the current one.
- `language` (string)
- `offer` (string, required)
- `task_id` (string, required): The search id (task id), e.g. from list_searches or create_search.
- `tone` (string)

### `set_outreach_funnel` (~163 tokens)

Set the accounts

«Аккаунты»: what the user can write from — email (bool), linkedin (none | basic | sales_navigator), threads (bool), linkedin_comments (public comments on LinkedIn posts, bool). At least one. The route of each person's messages is chosen from these. [REST: PUT /api/tasks/{id}/outreach/funnel]

Input parameters:

- `email` (boolean, required)
- `generation_id` (string): The outreach generation id (get_outreach campaign.generation.id); omitted: the current one.
- `linkedin` (string, required)
- `linkedin_comments` (boolean)
- `task_id` (string, required): The search id (task id), e.g. from list_searches or create_search.
- `threads` (boolean, required)

### `quote_outreach` (~147 tokens)

Price of the outreach

The price in credits of researching and writing messages for the chosen fit people (per person, total, the most it may hold), the balance, and who is skipped. Free. Its `credits` is the confirm_credits of start_outreach. [REST: POST /api/tasks/{id}/outreach/quote]

Input parameters:

- `cids` (array, required): Fit people (cid) of the search; get_outreach lists them.
- `generation_id` (string): The outreach generation id (get_outreach campaign.generation.id); omitted: the current one.
- `task_id` (string, required): The search id (task id), e.g. from list_searches or create_search.

### `start_outreach` (~182 tokens)

Write the messages (spends credits)

SPENDS CREDITS: quote_outreach first, show the price to the user and after their yes pass its `credits` as confirm_credits. Needs the sender ready, the essence and the accounts. Runs in the background (minutes); poll get_outreach every 30-60 s. [REST: POST /api/tasks/{id}/outreach/start]

Input parameters:

- `cids` (array, required): Fit people (cid) of the search; get_outreach lists them.
- `confirm_credits` (integer, required): The price in credits the matching quote returned, shown to the user and confirmed by them.
- `generation_id` (string): The outreach generation id (get_outreach campaign.generation.id); omitted: the current one.
- `task_id` (string, required): The search id (task id), e.g. from list_searches or create_search.

### `quote_outreach_retry` (~134 tokens)

Price of retrying failed people

The price in credits of retrying the people whose messages failed, from where they stopped. Free; its `credits` is the confirm_credits of retry_outreach. [REST: POST /api/tasks/{id}/outreach/retry/quote]

Input parameters:

- `cids` (array): The failed people to retry; omitted: every failed person of the generation.
- `generation_id` (string): The outreach generation id (get_outreach campaign.generation.id); omitted: the current one.
- `task_id` (string, required): The search id (task id), e.g. from list_searches or create_search.

### `retry_outreach` (~153 tokens)

Retry failed people (spends credits)

SPENDS CREDITS: quote_outreach_retry first, show the price, after the user's yes pass its `credits` as confirm_credits. [REST: POST /api/tasks/{id}/outreach/retry]

Input parameters:

- `cids` (array): The failed people to retry; omitted: every failed person of the generation.
- `confirm_credits` (integer, required): The price in credits the matching quote returned, shown to the user and confirmed by them.
- `generation_id` (string): The outreach generation id (get_outreach campaign.generation.id); omitted: the current one.
- `task_id` (string, required): The search id (task id), e.g. from list_searches or create_search.

### `get_outreach_lead` (~137 tokens)

One person's messages

One person of the outreach: the messages by step (network, kind, text, character limit, hook and the fact it uses, the post of a comment), the route and why, the findings of the research with sources, contacts. step_id, result_id and the revision are what the edit, rewrite and variant tools need. [REST: GET /api/tasks/{id}/outreach/leads/{cid}]

Input parameters:

- `cid` (string, required): The person's id (cid) from list_leads.
- `task_id` (string, required): The search id (task id), e.g. from list_searches or create_search.

### `edit_outreach_message` (~151 tokens)

Edit a message by hand

Saves the user's own text of one message step (free). result_id and expected_revision from get_outreach_lead protect against an edit made meanwhile. [REST: PATCH /api/tasks/{id}/outreach/leads/{cid}/steps/{step_id}]

Input parameters:

- `cid` (string, required): The person's id (cid) from list_leads.
- `expected_revision` (integer)
- `result_id` (string)
- `step_id` (string, required): The step id of the message (get_outreach_lead steps[].step_id).
- `task_id` (string, required): The search id (task id), e.g. from list_searches or create_search.
- `text` (string, required)

### `quote_message_rewrite` (~179 tokens)

Price of an AI rewrite

The price in credits of rewriting one message by AI (mode). Free; answers result_id, expected_revision and `credits` for rewrite_message. [REST: POST /api/tasks/{id}/outreach/leads/{cid}/steps/{step_id}/rewrite/quote]

Input parameters:

- `cid` (string, required): The person's id (cid) from list_leads.
- `generation_id` (string): The outreach generation id (get_outreach campaign.generation.id); omitted: the current one.
- `mode` (string, required): other_hook (another fact), shorter, warmer, rewrite (with the note).
- `step_id` (string, required): The step id of the message (get_outreach_lead steps[].step_id).
- `task_id` (string, required): The search id (task id), e.g. from list_searches or create_search.

### `rewrite_message` (~240 tokens)

Rewrite a message by AI (spends credits)

SPENDS CREDITS: quote_message_rewrite first, show the price, after the user's yes pass its credits, result_id and expected_revision. The new text comes in a few seconds: get_outreach_lead. [REST: POST /api/tasks/{id}/outreach/leads/{cid}/steps/{step_id}/rewrite]

Input parameters:

- `cid` (string, required): The person's id (cid) from list_leads.
- `confirm_credits` (integer, required): The price in credits the matching quote returned, shown to the user and confirmed by them.
- `expected_revision` (integer)
- `generation_id` (string): The outreach generation id (get_outreach campaign.generation.id); omitted: the current one.
- `mode` (string, required): other_hook (another fact), shorter, warmer, rewrite (with the note).
- `note` (string)
- `result_id` (string)
- `step_id` (string, required): The step id of the message (get_outreach_lead steps[].step_id).
- `task_id` (string, required): The search id (task id), e.g. from list_searches or create_search.

### `get_message_variant` (~110 tokens)

An AI variant not applied

A finished AI variant of a person's messages that was not applied because the text was edited meanwhile (its id from get_outreach_lead). [REST: GET /api/tasks/{id}/outreach/leads/{cid}/candidates/{candidate_id}]

Input parameters:

- `candidate_id` (string, required)
- `cid` (string, required): The person's id (cid) from list_leads.
- `task_id` (string, required): The search id (task id), e.g. from list_searches or create_search.

### `apply_message_variant` (~125 tokens)

Apply an AI variant

Replaces the person's messages with that variant (free); result_id and expected_result_revision from get_outreach_lead. [REST: POST /api/tasks/{id}/outreach/leads/{cid}/candidates/{candidate_id}/apply]

Input parameters:

- `candidate_id` (string, required)
- `cid` (string, required): The person's id (cid) from list_leads.
- `expected_result_revision` (integer)
- `result_id` (string)
- `task_id` (string, required): The search id (task id), e.g. from list_searches or create_search.

### `export_outreach` (~99 tokens)

Export the outreach (download link)

A download link for the whole outreach as one Excel sheet (every person with the messages by touch, the route, the facts). Works for one hour without signing in; give it to the user. [REST: GET /api/tasks/{id}/outreach/export.xlsx (signed link /api/dl/{token})]

Input parameters:

- `task_id` (string, required): The search id (task id), e.g. from list_searches or create_search.

### `list_searches` (~73 tokens)

My searches

The user's searches («Мои поиски»), newest first: id, title, status, leads / partial found, target, credits charged, progress of a running one. [REST: GET /api/tasks]

Input parameters:

- `limit` (integer)
- `offset` (integer)
- `status` (string)

### `get_search` (~163 tokens)

A search: state and next step

One search: status, progress, counts, credits charged, the estimate (price examples), what to do next (`next`); for a search that asks about a higher price, the question (`ask`). detail=spec adds the requirements as the review screen shows them (criteria with ids, pains, counter-signals, the search method and its options, veins); detail=full adds the brief in full. Poll it while a search compiles or runs. [REST: GET /api/tasks/{id} (+ GET /api/tasks while it runs, GET /api/tasks/{id}/snapshot while it asks)]

Input parameters:

- `detail` (string)
- `task_id` (string, required): The search id (task id), e.g. from list_searches or create_search.

### `get_search_requirements` (~71 tokens)

Requirements as checked

The requirements of a search as the results sheet shows them (how each criterion is checked, where the facts come from). [REST: GET /api/tasks/{id}/requirements]

Input parameters:

- `task_id` (string, required): The search id (task id), e.g. from list_searches or create_search.

### `edit_search_spec` (~158 tokens)

Change criteria roles / proof

Before the run (status ready): change the role of criteria (required = must be proven, plus = a bonus) and how strictly they are proven (inference = may be inferred, explicit = needs an explicit source; dearer), and the order of the sources. No AI call; the estimate is counted again. Needs a plan (or credits). [REST: PATCH /api/tasks/{id}/spec]

Input parameters:

- `criteria` (array)
- `source_order` (array)
- `task_id` (string, required): The search id (task id), e.g. from list_searches or create_search.
- `version` (integer): The spec version from get_search (optional: protects against an edit made meanwhile in the web).

### `edit_criterion` (~208 tokens)

Add, reword, remove or restore a criterion

Before the run: action=add (a new requirement in words; an AI call adds it), edit (new wording and/or role / standard of criterion_id), remove («Неверно»: drop it; `confirm` true when the answer warned that it is the only job-title criterion), restore («Вернуть»: undo the last change of it). The estimate is counted again. [REST: POST /api/tasks/{id}/criteria, POST /api/tasks/{id}/criteria/{cid}/edit|remove|restore]

Input parameters:

- `action` (string, required)
- `confirm` (boolean)
- `criterion_id` (string)
- `role` (string)
- `standard` (string)
- `task_id` (string, required): The search id (task id), e.g. from list_searches or create_search.
- `text` (string)
- `version` (integer): The spec version from get_search (optional: protects against an edit made meanwhile in the web).

### `edit_pain` (~136 tokens)

Edit, remove or restore a pain

Before the run: the pains («боли») the search looks for in a lead's facts. action=edit (new text of pain_id), remove, restore. [REST: POST /api/tasks/{id}/pains/{pid}/edit|remove|restore]

Input parameters:

- `action` (string, required)
- `pain_id` (string, required)
- `task_id` (string, required): The search id (task id), e.g. from list_searches or create_search.
- `text` (string)
- `version` (integer): The spec version from get_search (optional: protects against an edit made meanwhile in the web).

### `edit_counter_signal` (~125 tokens)

Remove or restore a counter-signal

Before the run: the counter-signals («контрсигналы») that make a lead partial or a miss. action=remove or restore. [REST: POST /api/tasks/{id}/counter-signals/{sid}/remove|restore]

Input parameters:

- `action` (string, required)
- `signal_id` (string, required)
- `task_id` (string, required): The search id (task id), e.g. from list_searches or create_search.
- `version` (integer): The spec version from get_search (optional: protects against an edit made meanwhile in the web).

### `set_search_strategy` (~136 tokens)

Change the search method

Before the run: the search method («способ поиска») — people (search people directly), companies_first (find the companies, then the people in them), via_related_people; only the options get_search detail=spec lists for this spec. The plan and the estimate are made again. [REST: POST /api/tasks/{id}/strategy]

Input parameters:

- `strategy` (string, required)
- `task_id` (string, required): The search id (task id), e.g. from list_searches or create_search.
- `version` (integer): The spec version from get_search (optional: protects against an edit made meanwhile in the web).

### `quote_search` (~140 tokens)

Price of a search run

The price in whole credits of running a ready search for `leads` leads (or of continuing a finished one for `leads` more): a low-high range; the start holds the high figure and charges what it really spends. Also the available balance. Show the price to the user and get a yes before run_search / continue_search, passing credits_high as confirm_credits. Free, changes nothing. [REST: GET /api/tasks/{id} (estimate.credits_by_target)]

Input parameters:

- `leads` (integer)
- `task_id` (string, required): The search id (task id), e.g. from list_searches or create_search.

### `run_search` (~201 tokens)

Start a search (spends credits)

Starts a ready search for `leads` leads. SPENDS CREDITS: first call quote_search, show the price to the user, and only after their explicit yes call this with confirm_credits = the quote's credits_high. stop_at_target (default true) stops at the number of leads. Returns at once (maybe queued); then poll get_search every 30-60 s. Needs a plan or credits on the balance. [REST: POST /api/tasks/{id}/run]

Input parameters:

- `confirm_credits` (integer, required): The price in credits the matching quote returned, shown to the user and confirmed by them.
- `leads` (integer, required)
- `stop_at_target` (boolean)
- `task_id` (string, required): The search id (task id), e.g. from list_searches or create_search.
- `version` (integer): The spec version from get_search (optional: protects against an edit made meanwhile in the web).

### `continue_search` (~156 tokens)

Find more leads (spends credits)

«Продолжить поиск»: a finished or stopped search goes on for `more` more leads with the same requirements (no new brief). SPENDS CREDITS: quote_search(leads=more) first, show the price, and after the user's yes pass its credits_high as confirm_credits. Returns at once; poll get_search. [REST: POST /api/tasks/{id}/more]

Input parameters:

- `confirm_credits` (integer, required): The price in credits the matching quote returned, shown to the user and confirmed by them.
- `more` (integer, required)
- `stop_at_target` (boolean)
- `task_id` (string, required): The search id (task id), e.g. from list_searches or create_search.

### `control_search` (~145 tokens)

Pause, resume, stop or answer a search

A started search: pause, resume, stop (the leads found are kept and charged), or continue — the answer to a search that asks about a higher price (status asking): it SPENDS the extra credits of get_search's `ask.continue_credits`; show them and pass them as confirm_credits after the user's yes. [REST: POST /api/tasks/{id}/control]

Input parameters:

- `action` (string, required)
- `confirm_credits` (integer): The price in credits the matching quote returned, shown to the user and confirmed by them.
- `task_id` (string, required): The search id (task id), e.g. from list_searches or create_search.

### `rename_search` (~64 tokens)

Rename a search

The name a search card shows (1-80 characters). [REST: PUT /api/tasks/{id}/title]

Input parameters:

- `task_id` (string, required): The search id (task id), e.g. from list_searches or create_search.
- `title` (string, required)

### `delete_search` (~85 tokens)

Delete a search (destructive)

Deletes a search with its leads and outreach; a running one is stopped first. Nothing is refunded and it cannot be undone. Ask the user to confirm and pass confirm=true. [REST: DELETE /api/tasks/{id}]

Input parameters:

- `confirm` (boolean, required)
- `task_id` (string, required): The search id (task id), e.g. from list_searches or create_search.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-catchy-me-catchy-me/app#diagnostics

## Score history

- 2026-11-21: 65
- 2026-11-20: 64
- 2026-11-19: 64
- 2026-11-18: 63
- 2026-11-17: 63

## Common questions

### What is the catchy-me MCP server?

catchy-me is an MCP server listed in the public MCP registry as com.catchy-me/catchy-me. Find B2B leads on LinkedIn that match your ICP, with verified facts and a first message for each. This page covers its hosted endpoint (https://app.catchy-me.com/mcp).

### Is the catchy-me MCP server safe to use?

catchy-me scores 65 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the catchy-me MCP server expose?

catchy-me exposes 66 tools: catchy_info, sign_up, resend_sign_up_code, confirm_sign_up, sign_in, and 61 more. Their descriptions and schemas cost roughly 8,920 tokens of context every time the server is loaded.

### Does the catchy-me MCP server require authentication?

No. We connected to catchy-me without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the catchy-me MCP server still maintained?

catchy-me is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the catchy-me MCP server?

VerifyMCP ran 13 checks on catchy-me, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://app.catchy-me.com/mcp
- Website: https://catchy-me.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-catchy-me-catchy-me/app.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-catchy-me-catchy-me/app/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-catchy-me-catchy-me/app.json
- HTML version of this page: https://verifymcp.io/servers/com-catchy-me-catchy-me/app
