Endpoints: 76,849MCP servers: 32,723Payout addresses: 3,825Paid calls: 6,107Letters: 83Defects: 3,886counted 2 min ago
teppi

MCP servercom.catchy-me/catchy-me

Find B2B leads on LinkedIn that match your ICP, with verified facts and a first message for each.
UNRATEDActivestreamable-httpapp.catchy-me.com

Overview

Score?
UNRATED 0.143
of what a free look can see, on 1 looks
Looks
1
last 14 hr ago
Tools
66

More info

URL
app.catchy-me.com/mcp
streamable-http
Says it is
catchy-me 2.0
protocol 2025-06-18
In the record since
15 hr ago

Among servers32,723 with a card

0median 0.547 · this server 0.143 · highest on record 0.8351

Toolsfrom sha256:eb5db942d6…c9ffb9

The tools this server lists, read out of the definition it returned
ToolSchema
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 too
input · no output
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/
input · no output
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. [RES
input · no output
catchy_info
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 b
input · no output
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]
input · no output
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 p
input · no output
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 ext
input · no output
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 onboardi
input · no output
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: DEL
input · no output
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]
input · no output
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 propos
input · no output
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]
input · no output
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 w
input · no output
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}/ou
input · no output
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|r
input · no output
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 = nee
input · no output
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]
input · no output
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 use
input · no output
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;
input · no output
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 onbo
input · no output
get_account
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
input · no output
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/a
input · no output
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)
input · no output
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/{
input · no output
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
input · no output
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, c
input · no output
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 re
input · no output
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}]
input · no output
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`). d
input · no output
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]
input · no output
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]
input · no output
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 br
input · no output
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]
input · no output
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
input · no output
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 gen
input · no output
list_plans
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
input · no output
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 /
input · no output
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]
input · no output
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 generatio
input · no output
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 o
input · no output
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
input · no output
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
input · no output
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` i
input · no output
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
input · no output
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 cha
input · no output
rename_search
The name a search card shows (1-80 characters). [REST: PUT /api/tasks/{id}/title]
input · no output
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]
input · no output
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]
input · no output
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]
input · no output
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]
input · no output
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`.
input · no output
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_outrea
input · no output
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
input · no output
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]
input · no output
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
input · no output
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
input · no output
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 o
input · no output
sign_in
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 · no output
sign_up
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
input · no output
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
input · no output
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. Ru
input · no output
subscribe
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
input · no output
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` o
input · no output
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 matte
input · no output
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 onboard
input · no output
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]
input · no output
Verify it yourselfnpx teppi-check https://app.catchy-me.com/mcpcurl -s https://api.teppi.xyz/v1/trust/mcp/mcs_01M7PK724DRH9FDWF85JPKJA3K