List your agent

catchy-me

MCP server● Hosted · onlinev1.0.0

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

What you can do with it

Share of each task's required capabilities it covers

Prefer a ready-made agent?

An MCP server is a connector for your own assistant. These finished products do the job for you: find leads.
All AI agents to find leads, ranked →

Similar tools

Listed for the same task: find leads

Reviews

No review yet. Used catchy-me? Be the first to help others choose.

What it does

catchy-me is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

From the publisher's description, Electra Index matched it to 2 capabilities: lead generation and social media management. That makes it a candidate for tasks such as find leads or find B2B partners.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version1.0.0
PriceNot in the registry
First seen17 Nov 2026
Last checked3h ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 3h ago (live check)

Hosted endpoint

  • https://app.catchy-me.com/mcp streamable-http

In Claude Code: claude mcp add --transport http catchy-me https://app.catchy-me.com/mcp

MCP settings (Claude Desktop, Cursor and other MCP clients)

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

Live check

Electra Index connected to the hosted endpoint 3h ago

ONLINE catchy-me answered an MCP connection on 17 Nov 2026 and introduced itself as catchy 2.0 (MCP protocol 2025-06-18).

66 tools offered to AI assistants

  • catchy_info · What Catchy 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 Pol
  • sign_up · Registers a new Catchy 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 /
  • resend_sign_up_code · 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]
  • confirm_sign_up · 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]
  • sign_in · An existing Catchy account: email and password -> an API key for this MCP server (shown once). The web's login limits apply. [REST: POST /api/auth/login]
  • request_password_reset · 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]
  • reset_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]
  • get_account · The signed-in Catchy 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 w
  • accept_legal · 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
  • get_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]
  • list_plans · The tariff catalog: each plan's monthly price (USD, RUB, EUR), credits and briefs a period, and the Enterprise contact. A subscription is bought with subscribe (a LavaTop payment link) or arranged with Catchy (Enterprise). No sign-in needed
  • suggest_company_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
Show 54 more
  • suggest_goals · 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 br
  • suggest_audiences · 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 firs
  • parse_exclusions_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
  • extract_site_file_text · 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
  • list_previous_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 · 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}]
  • list_exclusion_sources · 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 · 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
  • get_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 subsc
  • subscribe · Creates a LavaTop payment for a monthly plan (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 LavaTo
  • get_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}]
  • cancel_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]
  • list_leads · 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
  • get_lead · 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/task
  • quote_facts_on_request · 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_cre
  • start_facts_on_request · 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]
  • demote_lead · 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]
  • diagnose_search · 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 t
  • revise_search · 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
  • get_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]
  • export_search · 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
  • get_outreach · 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 (paginat
  • list_outreach_presets · 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]
  • new_outreach · 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
  • set_outreach_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
  • edit_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]
  • suggest_outreach_essence · 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]
  • set_outreach_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]
  • set_outreach_funnel · «Аккаунты»: 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 fro
  • quote_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/ta
  • start_outreach · 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-6
  • quote_outreach_retry · 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]
  • retry_outreach · 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]
  • get_outreach_lead · 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 re
  • edit_outreach_message · 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}]
  • quote_message_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]
  • rewrite_message · 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}/st
  • get_message_variant · 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}]
  • apply_message_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]
  • export_outreach · 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 l
  • list_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]
  • get_search · 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
  • get_search_requirements · 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]
  • edit_search_spec · 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
  • edit_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 criterio
  • edit_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]
  • edit_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]
  • set_search_strategy · 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
  • quote_search · 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
  • run_search · 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 a
  • continue_search · «Продолжить поиск»: 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 conf
  • control_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
  • rename_search · The name a search card shows (1-80 characters). [REST: PUT /api/tasks/{id}/title]
  • delete_search · 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}]

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Hosted endpointhttps://app.catchy-me.com/mcpDECLAREDSRC-001 Official MCP Registry3h ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry3h ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry3h ago
Websitehttps://catchy-me.com/mcpDECLAREDSRC-001 Official MCP Registry3h ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry3h ago
Version1.0.0DECLAREDSRC-001 Official MCP Registry3h ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry3h ago

Change history

  • NEW17 Nov 2026
    first seen in the index

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run catchy-me? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor catchy-meLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of catchy-me?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedIn
Listed on Electra IndexListed on Electra Index
<a href="https://electraindex.com/mcp/catchy-me?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/catchy-me/card" width="260" height="72" alt="Listed on Electra Index"></a>

Questions about catchy-me

How do I connect catchy-me?

Use the hosted endpoint https://app.catchy-me.com/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

What tools does catchy-me offer?

When Electra Index connected on 17 Nov 2026, it listed 66 tools: catchy_info, sign_up, resend_sign_up_code, confirm_sign_up, sign_in, request_password_reset, reset_password, get_account and more. The full list is in "Live check" above.

Is catchy-me online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 3h ago.

What can I use catchy-me for?

Based on its description, it is most relevant to: find leads, find B2B partners, manage social media accounts, monitor brand mentions.