Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

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.

65 Trust /100

Last scanned (18 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 21 Nov 2026.

Category CRM and Sales

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability61
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 57% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 67 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +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.

  • 19 Nov 26 +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.

  • 18 Nov 26 0
    • 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 security
    • Stability: unverified → 0.03 ▲ functional
    • “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 cosmetic
  • 17 Nov 26 63

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://app.catchy-me.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=app.catchy-me.com CN=YE2,O=Let's Encrypt,C=US 6 Nov 2026 4 Feb 2027 ECDSA 256 ECDSA-SHA384 6e226a72bd51aa5ac50b586e3a61b76cb63
SANs: app.catchy-me.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of app.catchy-me.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
catchy-me.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=(), usb=(), browsing-topics=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://app.catchy-me.com/mcp Verified 200
http (plaintext) http://app.catchy-me.com/mcp HTTPS enforced 308 https://app.catchy-me.com/mcp
MCP tools · 66 exposed · ~8,920 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
accept_legal ~135

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)]

NameTypeReqDescription
confirmbooleanyesThe user read the links and explicitly agreed.

No output schema declared.

No examples provided.

apply_message_variant ~125

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]

NameTypeReqDescription
candidate_idstringyes–
cidstringyesThe person's id (cid) from list_leads.
expected_result_revisioninteger––
result_idstring––
task_idstringyesThe search id (task id), e.g. from list_searches or create_search.

No output schema declared.

No examples provided.

cancel_subscription ~65

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]

NameTypeReqDescription
confirmbooleanyes–

No output schema declared.

No examples provided.

catchy_info ~70

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

confirm_sign_up ~178

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]

NameTypeReqDescription
codestringyes–
emailstringyes–
key_accessstring––
key_daysinteger|null–Lifetime of the key in days; null = no limit. Default 365.
key_namestring–Name of the API key in Settings (default «MCP agent»).
langstring–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_tokenstringyes–

No output schema declared.

No examples provided.

continue_search ~156

«Продолжить поиск»: 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]

NameTypeReqDescription
confirm_creditsintegeryesThe price in credits the matching quote returned, shown to the user and confirmed by them.
moreintegeryes–
stop_at_targetboolean––
task_idstringyesThe search id (task id), e.g. from list_searches or create_search.

No output schema declared.

No examples provided.

control_search ~145

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]

NameTypeReqDescription
actionstringyes–
confirm_creditsinteger–The price in credits the matching quote returned, shown to the user and confirmed by them.
task_idstringyesThe search id (task id), e.g. from list_searches or create_search.

No output schema declared.

No examples provided.

create_search ~323

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]

NameTypeReqDescription
companystringyesWhat the user's company does (step 1).
exclude_companiesboolean–Also leave out the companies of those people.
exclude_company_urlsarray––
exclude_scopestring–From those searches: everyone analysed (all) or only leads.
exclude_tasksarray–Earlier searches whose people to leave out.
exclude_urlsarray–LinkedIn profile links of people to leave out.
goalstring–What the outreach should achieve (step 2).
icpstringyesWhom to find: the customer profile (step 3).
languagestring–Language of the outreach messages (default english).
onboarding_idstring–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_taskstring–The earlier onboarding this one was filled from (get_onboarding_prefill).

No output schema declared.

No examples provided.

delete_search ~85

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}]

NameTypeReqDescription
confirmbooleanyes–
task_idstringyesThe search id (task id), e.g. from list_searches or create_search.

No output schema declared.

No examples provided.

demote_lead ~99

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]

NameTypeReqDescription
cidsarrayyesPerson ids (cid) from list_leads.
task_idstringyesThe search id (task id), e.g. from list_searches or create_search.

No output schema declared.

No examples provided.

diagnose_search ~120

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]

NameTypeReqDescription
task_idstringyesThe search id (task id), e.g. from list_searches or create_search.

No output schema declared.

No examples provided.

edit_counter_signal ~125

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]

NameTypeReqDescription
actionstringyes–
signal_idstringyes–
task_idstringyesThe search id (task id), e.g. from list_searches or create_search.
versioninteger–The spec version from get_search (optional: protects against an edit made meanwhile in the web).

No output schema declared.

No examples provided.

edit_criterion ~208

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]

NameTypeReqDescription
actionstringyes–
confirmboolean––
criterion_idstring––
rolestring––
standardstring––
task_idstringyesThe search id (task id), e.g. from list_searches or create_search.
textstring––
versioninteger–The spec version from get_search (optional: protects against an edit made meanwhile in the web).

No output schema declared.

No examples provided.

edit_outreach_message ~151

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}]

NameTypeReqDescription
cidstringyesThe person's id (cid) from list_leads.
expected_revisioninteger––
result_idstring––
step_idstringyesThe step id of the message (get_outreach_lead steps[].step_id).
task_idstringyesThe search id (task id), e.g. from list_searches or create_search.
textstringyes–

No output schema declared.

No examples provided.

edit_pain ~136

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]

NameTypeReqDescription
actionstringyes–
pain_idstringyes–
task_idstringyesThe search id (task id), e.g. from list_searches or create_search.
textstring––
versioninteger–The spec version from get_search (optional: protects against an edit made meanwhile in the web).

No output schema declared.

No examples provided.

edit_search_spec ~158

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]

NameTypeReqDescription
criteriaarray––
source_orderarray––
task_idstringyesThe search id (task id), e.g. from list_searches or create_search.
versioninteger–The spec version from get_search (optional: protects against an edit made meanwhile in the web).

No output schema declared.

No examples provided.

edit_sender_card ~152

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]

NameTypeReqDescription
backgroundarray––
companystring––
generation_idstring–The outreach generation id (get_outreach campaign.generation.id); omitted: the current one.
interestsarray––
namestring––
rolestring––
summarystring––
task_idstringyesThe search id (task id), e.g. from list_searches or create_search.
voicestring––

No output schema declared.

No examples provided.

export_outreach ~99

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})]

NameTypeReqDescription
task_idstringyesThe search id (task id), e.g. from list_searches or create_search.

No output schema declared.

No examples provided.

export_search ~122

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})]

NameTypeReqDescription
formatstring––
kindsarray––
task_idstringyesThe search id (task id), e.g. from list_searches or create_search.

No output schema declared.

No examples provided.

extract_site_file_text ~185

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]

NameTypeReqDescription
data_base64stringyesThe file's bytes, base64.
file_namestringyesThe file's name with its extension.
onboarding_idstring–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…

No output schema declared.

No examples provided.

get_account ~120

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]

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_balance_history ~63

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]

NameTypeReqDescription
limitinteger––

No output schema declared.

No examples provided.

get_lead ~115

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}]

NameTypeReqDescription
cidstringyesThe person's id (cid) from list_leads.
task_idstringyesThe search id (task id), e.g. from list_searches or create_search.

No output schema declared.

No examples provided.

get_message_variant ~110

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}]

NameTypeReqDescription
candidate_idstringyes–
cidstringyesThe person's id (cid) from list_leads.
task_idstringyesThe search id (task id), e.g. from list_searches or create_search.

No output schema declared.

No examples provided.

get_onboarding_prefill ~94

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}]

NameTypeReqDescription
task_idstringyesThe search id (task id), e.g. from list_searches or create_search.

No output schema declared.

No examples provided.

get_outreach ~123

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]

NameTypeReqDescription
limitinteger––
offsetinteger––
task_idstringyesThe search id (task id), e.g. from list_searches or create_search.

No output schema declared.

No examples provided.

get_outreach_lead ~137

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}]

NameTypeReqDescription
cidstringyesThe person's id (cid) from list_leads.
task_idstringyesThe search id (task id), e.g. from list_searches or create_search.

No output schema declared.

No examples provided.

get_payment_status ~65

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}]

NameTypeReqDescription
order_idstringyesThe order id from subscribe.

No output schema declared.

No examples provided.

get_search ~163

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)]

NameTypeReqDescription
detailstring––
task_idstringyesThe search id (task id), e.g. from list_searches or create_search.

No output schema declared.

No examples provided.

get_search_funnel ~75

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]

NameTypeReqDescription
task_idstringyesThe search id (task id), e.g. from list_searches or create_search.

No output schema declared.

No examples provided.

get_search_requirements ~71

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]

NameTypeReqDescription
task_idstringyesThe search id (task id), e.g. from list_searches or create_search.

No output schema declared.

No examples provided.

get_subscription ~77

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]

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_exclusion_sources ~49

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]

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_leads ~136

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=]

NameTypeReqDescription
kindstring––
limitinteger––
offsetinteger––
task_idstringyesThe search id (task id), e.g. from list_searches or create_search.

No output schema declared.

No examples provided.

list_outreach_presets ~75

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]

NameTypeReqDescription
cursorstring––
limitinteger––

No output schema declared.

No examples provided.

list_plans ~61

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]

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_previous_onboardings ~57

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]

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_searches ~73

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

NameTypeReqDescription
limitinteger––
offsetinteger––
statusstring––

No output schema declared.

No examples provided.

new_outreach ~133

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]

NameTypeReqDescription
generation_idstring–The outreach generation id (get_outreach campaign.generation.id); omitted: the current one.
preset_idstring––
reuse_previousboolean––
task_idstringyesThe search id (task id), e.g. from list_searches or create_search.

No output schema declared.

No examples provided.

parse_exclusions_file ~209

«Исключить уже знакомых»: 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]

NameTypeReqDescription
data_base64stringyesThe file's bytes, base64.
file_namestringyesThe file's name with its extension.
onboarding_idstring–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…

No output schema declared.

No examples provided.

quote_facts_on_request ~149

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]

NameTypeReqDescription
cidsarrayyesPerson ids (cid) from list_leads.
promoteboolean––
task_idstringyesThe search id (task id), e.g. from list_searches or create_search.

No output schema declared.

No examples provided.

quote_message_rewrite ~179

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]

NameTypeReqDescription
cidstringyesThe person's id (cid) from list_leads.
generation_idstring–The outreach generation id (get_outreach campaign.generation.id); omitted: the current one.
modestringyesother_hook (another fact), shorter, warmer, rewrite (with the note).
step_idstringyesThe step id of the message (get_outreach_lead steps[].step_id).
task_idstringyesThe search id (task id), e.g. from list_searches or create_search.

No output schema declared.

No examples provided.

quote_outreach ~147

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]

NameTypeReqDescription
cidsarrayyesFit people (cid) of the search; get_outreach lists them.
generation_idstring–The outreach generation id (get_outreach campaign.generation.id); omitted: the current one.
task_idstringyesThe search id (task id), e.g. from list_searches or create_search.

No output schema declared.

No examples provided.

quote_outreach_retry ~134

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]

NameTypeReqDescription
cidsarray–The failed people to retry; omitted: every failed person of the generation.
generation_idstring–The outreach generation id (get_outreach campaign.generation.id); omitted: the current one.
task_idstringyesThe search id (task id), e.g. from list_searches or create_search.

No output schema declared.

No examples provided.

quote_search ~140

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)]

NameTypeReqDescription
leadsinteger––
task_idstringyesThe search id (task id), e.g. from list_searches or create_search.

No output schema declared.

No examples provided.

rename_search ~64

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

NameTypeReqDescription
task_idstringyesThe search id (task id), e.g. from list_searches or create_search.
titlestringyes–

No output schema declared.

No examples provided.

request_password_reset ~107

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]

NameTypeReqDescription
emailstringyes–
langstring–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.

No output schema declared.

No examples provided.

resend_sign_up_code ~108

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]

NameTypeReqDescription
emailstringyes–
langstring–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.

No output schema declared.

No examples provided.

reset_password ~114

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]

NameTypeReqDescription
codestringyes–
emailstringyes–
langstring–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.
passwordstringyes–

No output schema declared.

No examples provided.

retry_outreach ~153

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]

NameTypeReqDescription
cidsarray–The failed people to retry; omitted: every failed person of the generation.
confirm_creditsintegeryesThe price in credits the matching quote returned, shown to the user and confirmed by them.
generation_idstring–The outreach generation id (get_outreach campaign.generation.id); omitted: the current one.
task_idstringyesThe search id (task id), e.g. from list_searches or create_search.

No output schema declared.

No examples provided.

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.

remote · app.catchy-me.com

# add to Claude Code
claude mcp add --transport http com-catchy-me-catchy-me 'https://app.catchy-me.com/mcp'
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.