{"id":"com.catchy-me/catchy-me","slug":"com-catchy-me-catchy-me","title":"catchy-me","description":"Find B2B leads on LinkedIn that match your ICP, with verified facts and a first message for each.","version":"1.0.0","publisher":{"kind":"domain","id":"catchy-me.com","label":"catchy-me.com","url":"https://catchy-me.com"},"website":"https://catchy-me.com/mcp","repository":"","remotes":[{"type":"streamable-http","url":"https://app.catchy-me.com/mcp","headers":[{"description":"Optional. A catchy-me API key from Settings (catchy_...), sent as a Bearer token. Without it, clients that support MCP OAuth sign in through the browser when an account tool is called; public tools work without sign-in.","value":"Bearer {api_key}","isSecret":true,"variables":{"api_key":{"description":"catchy-me API key (Settings > API keys)","isSecret":true,"placeholder":"catchy_..."}},"name":"Authorization"}]}],"packages":[],"published":"2026-11-17","updated":"2026-11-17","status":"online","auth":"","latency_ms":1180,"checked":"2026-11-19","uptime":100,"checks":3,"tools":[{"name":"catchy_info","title":"About catchy-me","description":"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.","read_only":true},{"name":"sign_up","title":"Create a catchy-me account","description":"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. [RES","read_only":false},{"name":"resend_sign_up_code","title":"Send the sign-up code again","description":"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]","read_only":false},{"name":"confirm_sign_up","title":"Confirm the account and get an API key","description":"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]","read_only":false},{"name":"sign_in","title":"Sign in and get an API key","description":"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]","read_only":false},{"name":"request_password_reset","title":"Forgot the password","description":"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]","read_only":false},{"name":"reset_password","title":"Set a new password","description":"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]","read_only":false},{"name":"get_account","title":"Account, plan and balance","description":"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 ","read_only":true},{"name":"accept_legal","title":"Accept the updated Terms and Privacy Policy","description":"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 afte","read_only":false},{"name":"get_balance_history","title":"Balance history","description":"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]","read_only":true},{"name":"list_plans","title":"Plans (tariffs)","description":"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]","read_only":true},{"name":"suggest_company_description","title":"Describe the company (onboarding step 1)","description":"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 as","read_only":false},{"name":"suggest_goals","title":"Suggest outreach goals (onboarding step 2)","description":"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 ","read_only":false},{"name":"suggest_audiences","title":"Suggest audiences (onboarding step 3)","description":"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 th","read_only":false},{"name":"parse_exclusions_file","title":"Read people to exclude from a file","description":"«Исключить уже знакомых»: 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 assistan","read_only":false},{"name":"extract_site_file_text","title":"Read the company text from a file","description":"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: PO","read_only":false},{"name":"list_previous_onboardings","title":"Earlier onboardings","description":"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]","read_only":true},{"name":"get_onboarding_prefill","title":"Fill from an earlier onboarding","description":"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}]","read_only":true},{"name":"list_exclusion_sources","title":"Earlier searches to exclude","description":"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]","read_only":true},{"name":"create_search","title":"Create a lead search","description":"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: PO","read_only":false},{"name":"get_subscription","title":"Current subscription","description":"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]","read_only":true},{"name":"subscribe","title":"Buy a plan (payment link)","description":"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 (Russ","read_only":false},{"name":"get_payment_status","title":"Payment status","description":"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}]","read_only":true},{"name":"cancel_subscription","title":"Cancel the subscription","description":"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]","read_only":false},{"name":"list_leads","title":"Leads of a search","description":"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=]","read_only":true},{"name":"get_lead","title":"A lead's dossier","description":"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}]","read_only":true},{"name":"quote_facts_on_request","title":"Price of facts on request / move to fit","description":"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]","read_only":false},{"name":"start_facts_on_request","title":"Start facts on request (spends credits)","description":"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]","read_only":false},{"name":"demote_lead","title":"Move fit leads to partial","description":"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]","read_only":false},{"name":"diagnose_search","title":"Why the leads are dear or ran out","description":"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]","read_only":false},{"name":"revise_search","title":"Apply criteria changes (spends credits)","description":"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]","read_only":false},{"name":"get_search_funnel","title":"Search funnel","description":"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]","read_only":true},{"name":"export_search","title":"Export the leads (download link)","description":"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})]","read_only":true},{"name":"get_outreach","title":"Outreach desk","description":"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]","read_only":true},{"name":"list_outreach_presets","title":"Saved outreach setups","description":"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]","read_only":true},{"name":"new_outreach","title":"Start a new outreach setup","description":"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]","read_only":false},{"name":"set_outreach_sender","title":"Set the sender","description":"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]","read_only":false},{"name":"edit_sender_card","title":"Edit the sender card","description":"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]","read_only":false},{"name":"suggest_outreach_essence","title":"Draft the offer","description":"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]","read_only":false},{"name":"set_outreach_essence","title":"Set the essence","description":"«Суть»: 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]","read_only":false},{"name":"set_outreach_funnel","title":"Set the accounts","description":"«Аккаунты»: 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]","read_only":false},{"name":"quote_outreach","title":"Price of the outreach","description":"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]","read_only":false},{"name":"start_outreach","title":"Write the messages (spends credits)","description":"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]","read_only":false},{"name":"quote_outreach_retry","title":"Price of retrying failed people","description":"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]","read_only":false},{"name":"retry_outreach","title":"Retry failed people (spends credits)","description":"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]","read_only":false},{"name":"get_outreach_lead","title":"One person's messages","description":"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}]","read_only":true},{"name":"edit_outreach_message","title":"Edit a message by hand","description":"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}]","read_only":false},{"name":"quote_message_rewrite","title":"Price of an AI rewrite","description":"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]","read_only":false},{"name":"rewrite_message","title":"Rewrite a message by AI (spends credits)","description":"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]","read_only":false},{"name":"get_message_variant","title":"An AI variant not applied","description":"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}]","read_only":true},{"name":"apply_message_variant","title":"Apply an AI variant","description":"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]","read_only":false},{"name":"export_outreach","title":"Export the outreach (download link)","description":"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})]","read_only":true},{"name":"list_searches","title":"My searches","description":"The user's searches («Мои поиски»), newest first: id, title, status, leads / partial found, target, credits charged, progress of a running one. [REST: GET /api/tasks]","read_only":true},{"name":"get_search","title":"A search: state and next step","description":"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 ","read_only":true},{"name":"get_search_requirements","title":"Requirements as checked","description":"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]","read_only":true},{"name":"edit_search_spec","title":"Change criteria roles / proof","description":"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]","read_only":false},{"name":"edit_criterion","title":"Add, reword, remove or restore a criterion","description":"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}/ed","read_only":false},{"name":"edit_pain","title":"Edit, remove or restore a pain","description":"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]","read_only":false},{"name":"edit_counter_signal","title":"Remove or restore a counter-signal","description":"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]","read_only":false},{"name":"set_search_strategy","title":"Change the search method","description":"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]","read_only":false},{"name":"quote_search","title":"Price of a search run","description":"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/","read_only":true},{"name":"run_search","title":"Start a search (spends credits)","description":"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}/r","read_only":false},{"name":"continue_search","title":"Find more leads (spends credits)","description":"«Продолжить поиск»: 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]","read_only":false},{"name":"control_search","title":"Pause, resume, stop or answer a search","description":"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]","read_only":false},{"name":"rename_search","title":"Rename a search","description":"The name a search card shows (1-80 characters). [REST: PUT /api/tasks/{id}/title]","read_only":false},{"name":"delete_search","title":"Delete a search (destructive)","description":"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}]","read_only":false}],"server_info":{"description":"B2B leads on LinkedIn with facts, and AI outreach messages to them.","name":"catchy-me","title":"catchy-me","version":"2.0","websiteUrl":"https://app.catchy-me.com"},"category":"sales","tags":["web-search","communication","social"],"kind":"remote","source":"registry","submitted":{},"first_party":true,"domain_rank":null,"score":100,"indexable":true,"first_seen":"2026-11-17","stars":0,"badges":["new"],"sponsor":null,"page":"https://agentsindex.org/agents/com-catchy-me-catchy-me/"}