Skip to content

catchy-me MCP server

com.catchy-me/catchy-mecatchy-me.comstreamable-httpv1.0.0Scanned

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

66 tools: 2 can delete or cancel things, 1 do something that can't be undone, 43 change things and 20 only read.

Tools: 2 delete, 1 irreversible, 43 write, 20 read.
  • Reads private data · 5
  • Reads text others write · 4
  • Can send data out · 4
  • 3 findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here can delete or cancel things and 1 does something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the catchy-me MCP server can do

The catchy-me MCP server is published by catchy-me.com, a domain the MCP Registry verified. It has 66 tools. It can delete or cancel things (2 tools: cancel_subscription and delete_search), do things that cannot be undone, such as sending, paying or publishing (resend_sign_up_code) and create or change data (43 tools: catchy_info, sign_up, confirm_sign_up, sign_in and 39 more). 20 tools only read.

5 tools read private data (get_account, list_plans, get_lead and 2 more); 4 tools bring in text other people can write (get_account, get_lead, get_outreach_lead and 1 more); 4 tools can send data out of your system (resend_sign_up_code, suggest_company_description, edit_outreach_message and 1 more). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 3 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 17, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

66 tools

Deletes or cancels 2Claude Code: deny
  • cancel_subscriptionStops the renewal of a LavaTop subscription: the plan stays until the period's end and the credits stay on the balance after it.No findings

    Why it is in this group

    • The name "cancel_subscription" says "cancel": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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]

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
    • title: Cancel the subscription
Can't be undone 1Claude Code: ask
  • resend_sign_up_codeSends a new code for a pending registration (at most once a minute; the answer is the same whether or not one is pending).Can send data outNo findings

    Why it is in this group

    • The name "resend_sign_up_code" says "resend": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • outboundThe name "resend_sign_up_code" says "resend": it sends or publishes something to other people.
    Description, as the server wrote it
    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]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Send the sign-up code again
Changes things 43Claude Code: ask
  • apply_message_variantReplaces the person's messages with that variant (free); result_id and expected_result_revision from get_outreach_lead.Can send data outNo findings

    Why it is in this group

    • The name "apply_message_variant" says "apply": a word for a change.

    What it can reach

    • outboundThe name "apply_message_variant" says "apply" and "message": it writes something other people read.
    Description, as the server wrote it
    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]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Apply an AI variant
  • catchy_infoWhat 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 i…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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 Policy. No sign-in needed.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: About Catchy
  • confirm_sign_upConfirms the registration with the emailed code and the signup_token of sign_up, and returns an API key for this MCP server (shown once).No findings

    Why it is in this group

    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    Description, as the server wrote it
    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]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Confirm the account and get an API key
  • demote_leadAfter a search: moves chosen fit people to partial («в частично подходящие»), e.g.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Move fit leads to partial
  • edit_counter_signalBefore the run: the counter-signals («контрсигналы») that make a lead partial or a miss.No findings

    Why it is in this group

    • The name "edit_counter_signal" says "edit": a word for a change.
    Description, as the server wrote it
    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]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Remove or restore a counter-signal
  • edit_criterionBefore 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…No findings

    Why it is in this group

    • The name "edit_criterion" says "edit": a word for a change.
    Description, as the server wrote it
    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]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Add, reword, remove or restore a criterion
  • edit_outreach_messageSaves the user's own text of one message step (free).Can send data outNo findings

    Why it is in this group

    • The name "edit_outreach_message" says "edit": a word for a change.

    What it can reach

    • outboundThe name "edit_outreach_message" says "edit" and "message": it writes something other people read.
    Description, as the server wrote it
    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}]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
    • title: Edit a message by hand
  • edit_painBefore the run: the pains («боли») the search looks for in a lead's facts.No findings

    Why it is in this group

    • The name "edit_pain" says "edit": a word for a change.
    Description, as the server wrote it
    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]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Edit, remove or restore a pain
  • edit_search_specBefore 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…No findings

    Why it is in this group

    • The name "edit_search_spec" says "edit": a word for a change.
    Description, as the server wrote it
    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]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
    • title: Change criteria roles / proof
  • edit_sender_cardCorrect the sender's card the analysis made (name, role, company, voice = how they write, summary, background, interests).No findings

    Why it is in this group

    • The name "edit_sender_card" says "edit": a word for a change.
    Description, as the server wrote it
    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]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
    • title: Edit the sender card
  • export_outreachA download link for the whole outreach as one Excel sheet (every person with the messages by touch, the route, the facts).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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})]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Export the outreach (download link)
  • extract_site_file_textWhen 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=...).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Read the company text from a file
  • new_outreachA fresh outreach generation of the search: empty, or with this search's previous setup (reuse_previous) or a saved one (preset_id).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Start a new outreach setup
  • 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…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    «Исключить уже знакомых»: 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]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Read people to exclude from a file
  • quote_facts_on_requestAfter 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).No findings

    Why it is in this group

    • The name "quote_facts_on_request" says "request": a word for a change.
    Description, as the server wrote it
    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]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Price of facts on request / move to fit
  • quote_message_rewriteThe price in credits of rewriting one message by AI (mode).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Price of an AI rewrite
  • quote_outreachThe 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.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Price of the outreach
  • quote_outreach_retryThe price in credits of retrying the people whose messages failed, from where they stopped.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Price of retrying failed people
  • request_password_resetEmails a code to reset the password of an account (the answer is the same whether or not the account exists).No findings

    Why it is in this group

    • The name "request_password_reset" says "request": a word for a change.
    Description, as the server wrote it
    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]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Forgot the password
  • reset_passwordSets a new password with the emailed code (every session of the account ends).No findings

    Why it is in this group

    • The name "reset_password" says "reset": a word for a change.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    Description, as the server wrote it
    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]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Set a new password
  • retry_outreachSPENDS CREDITS: quote_outreach_retry first, show the price, after the user's yes pass its `credits` as confirm_credits.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Retry failed people (spends credits)
  • rewrite_messageSPENDS CREDITS: quote_message_rewrite first, show the price, after the user's yes pass its credits, result_id and expected_revision.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Rewrite a message by AI (spends credits)
  • set_outreach_essence«Суть»: offer (what we offer), ask (what we want from the person), optional tone and client_rules, and the message language.No findings

    Why it is in this group

    • The name "set_outreach_essence" says "set": a word for a change.
    Description, as the server wrote it
    «Суть»: 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]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
    • title: Set the 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).No findings

    Why it is in this group

    • The name "set_outreach_funnel" says "set": a word for a change.
    Description, as the server wrote it
    «Аккаунты»: 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]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
    • title: Set the accounts
  • set_outreach_senderWho 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.No findings

    Why it is in this group

    • The name "set_outreach_sender" says "set": a word for a change.
    Description, as the server wrote it
    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]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Set the sender
  • set_search_strategyBefore 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…No findings

    Why it is in this group

    • The name "set_search_strategy" says "set": a word for a change.
    Description, as the server wrote it
    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]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
    • title: Change the search method
  • sign_inAn existing Catchy account: email and password -> an API key for this MCP server (shown once).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Sign in and get an API key
  • sign_upRegisters a new Catchy account and emails a 6-digit code to confirm it (then confirm_sign_up).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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 / privacy_policy) — ask them first. Without a password one is generated and returned once: give it to the user. Returns signup_token for confirm_sign_up. [REST: POST /api/auth/register/start]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Create a Catchy account
  • start_facts_on_requestSPENDS CREDITS: quote_facts_on_request first, show the price to the user and after their yes pass its `credits` as confirm_credits.No findings

    Why it is in this group

    • The name "start_facts_on_request" says "start": a word for a change.
    Description, as the server wrote it
    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]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Start facts on request (spends credits)
  • start_outreachSPENDS CREDITS: quote_outreach first, show the price to the user and after their yes pass its `credits` as confirm_credits.No findings

    Why it is in this group

    • The name "start_outreach" says "start": a word for a change.
    Description, as the server wrote it
    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]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Write the messages (spends credits)
  • subscribeCreates a LavaTop payment for a monthly plan (start, growth, scale; prices in list_plans) and returns its payment_url and order id.No findings

    Why it is in this group

    • The name "subscribe" says "subscribe": a word for a change.
    Description, as the server wrote it
    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 LavaTop's page by card, SBP or PayPal (an agent cannot). Currency is also the method: RUB — Russian cards and SBP; USD — foreign cards, PayPal, Apple Pay (Russian cards pay only in RUB); EUR is not available. A USD link lives 15 minutes, a RUB link 24 hours. Then poll get_payment_status every 15-30 s until paid; the plan's credits and briefs arrive with the payment and renew monthly until cancel_subscription. [REST: POST /api/billing/checkout]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Buy a plan (payment link)
  • suggest_audiencesStep 3 («Кому пишем»): three customer profiles (ICP) to search for, from the company and the goal; each with a short title, the profile text and why.No findings

    Why it is in this group

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

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Suggest audiences (onboarding step 3)
  • suggest_company_descriptionStep 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…Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

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

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Describe the company (onboarding step 1)
  • suggest_goalsStep 2 («Цель»): four goals for the outreach to the people found (e.g.No findings

    Why it is in this group

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

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Suggest outreach goals (onboarding step 2)
  • suggest_outreach_essenceA draft of «Что предлагаем» (the offer) from the search's onboarding.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Draft the offer
Only reads 20Show 20 read-only tools
  • get_accountThe 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…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_account" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "email": it reads mail.
    • untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    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 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]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Account, plan and balance
  • get_balance_historyThe 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.No findings

    Why it is in this group

    • The name "get_balance_history" says "get": a word for reading.
    Description, as the server wrote it
    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]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Balance history
  • get_leadOne 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)…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_lead" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "message": it reads messages.
    • untrusted-inputThe description's first sentence says "message": it reads messages, which other people can write.
    Description, as the server wrote it
    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}]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: A lead's dossier
  • get_message_variantA finished AI variant of a person's messages that was not applied because the text was edited meanwhile (its id from get_outreach_lead).Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_message_variant" says "get": a word for reading.

    What it can reach

    • private-dataThe name "get_message_variant" says "get" and "message": it reads messages.
    • private-dataThe description's first sentence says "message": it reads messages.
    • untrusted-inputThe name "get_message_variant" says "get" and "message": it reads messages, which other people can write.
    • untrusted-inputThe description's first sentence says "message": it reads messages, which other people can write.
    Description, as the server wrote it
    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}]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: An AI variant not applied
  • get_onboarding_prefillThe 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…No findings

    Why it is in this group

    • The name "get_onboarding_prefill" says "get": a word for reading.
    Description, as the server wrote it
    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}]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Fill from an earlier onboarding
  • get_outreachThe outreach («Рассылка») of a finished search: the campaign (sender with its card, essence = offer / ask / tone / rules / language, the accounts, counts, the current generation, c…No findings

    Why it is in this group

    • The name "get_outreach" says "get": a word for reading.
    Description, as the server wrote it
    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]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Outreach desk
  • get_outreach_leadOne 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…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_outreach_lead" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "message": it reads messages.
    • untrusted-inputThe description's first sentence says "message": it reads messages, which other people can write.
    Description, as the server wrote it
    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}]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: One person's messages
  • get_payment_statusThe status of a payment order made by subscribe: pending, paid, failed, expired, cancelled.No findings

    Why it is in this group

    • The name "get_payment_status" says "get": a word for reading.
    Description, as the server wrote it
    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}]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Payment status
  • get_search_funnelA finished search's funnel in plain words: how many people were seen, checked, rejected and why, and how many became leads.No findings

    Why it is in this group

    • The name "get_search_funnel" says "get": a word for reading.
    Description, as the server wrote it
    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]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Search funnel
  • get_search_requirementsThe requirements of a search as the results sheet shows them (how each criterion is checked, where the facts come from).No findings

    Why it is in this group

    • The name "get_search_requirements" says "get": a word for reading.
    Description, as the server wrote it
    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]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Requirements as checked
  • get_subscriptionThe 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…No findings

    Why it is in this group

    • The name "get_subscription" says "get": a word for reading.
    Description, as the server wrote it
    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]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Current subscription
  • list_exclusion_sourcesThe 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.No findings

    Why it is in this group

    • The name "list_exclusion_sources" says "list": a word for reading.
    Description, as the server wrote it
    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]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Earlier searches to exclude
  • list_leadsThe people of a search by kind: fit («Подходят»: the leads, in their order), partial («Частично»: some requirement not proven, with what was assumed), miss («Не подходят», with the…No findings

    Why it is in this group

    • The name "list_leads" says "list": a word for reading.
    Description, as the server wrote it
    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=]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Leads of a search
  • list_outreach_presetsThe 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…No findings

    Why it is in this group

    • The name "list_outreach_presets" says "list": a word for reading.
    Description, as the server wrote it
    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]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Saved outreach setups
  • list_plansThe tariff catalog: each plan's monthly price (USD, RUB, EUR), credits and briefs a period, and the Enterprise contact.Reads private dataNo findings

    Why it is in this group

    • The name "list_plans" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "contact": it reads contacts.
    Description, as the server wrote it
    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. [REST: GET /api/plans]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Plans (tariffs)
  • list_previous_onboardingsThe user's earlier search onboardings (company, goal, audience), newest first.No findings

    Why it is in this group

    • The name "list_previous_onboardings" says "list": a word for reading.
    Description, as the server wrote it
    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]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Earlier onboardings
  • list_searchesThe user's searches («Мои поиски»), newest first: id, title, status, leads / partial found, target, credits charged, progress of a running one.No findings

    Why it is in this group

    • The name "list_searches" says "list": a word for reading.
    Description, as the server wrote it
    The user's searches («Мои поиски»), newest first: id, title, status, leads / partial found, target, credits charged, progress of a running one. [REST: GET /api/tasks]

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: My searches

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

80 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 4 outbound tools breaks every one.

Reads private data5
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out4
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__catchy-me__apply_message_variant",
      "mcp__catchy-me__edit_outreach_message",
      "mcp__catchy-me__resend_sign_up_code",
      "mcp__catchy-me__suggest_company_description"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 17, 2026, 15:18 UTC, unchanged since Nov 17, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
46
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://app.catchy-me.com/.well-known/oauth-protected-resource/mcp
Authorization servers
https://app.catchy-me.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 46 tools that change things (2 destructive, 1 irreversible, 43 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://app.catchy-me.com/mcp: tools/list returned 66 tools to an anonymous client, including cancel_subscription (destructive), delete_search (destructive), resend_sign_up_code (irreversible), catchy_info (write), sign_up (write) and 41 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

3 warn
  • The server marks "diagnose_search" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "diagnose_search" says "search": a word for reading.

    What this check looks for
  • The server marks "continue_search" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "continue_search" says "search": a word for reading.

    What this check looks for
  • The server marks "control_search" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "control_search" says "search": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__catchy-me__get_account",
      "mcp__catchy-me__get_balance_history",
      "mcp__catchy-me__list_plans",
      "mcp__catchy-me__list_previous_onboardings",
      "mcp__catchy-me__get_onboarding_prefill",
      "mcp__catchy-me__list_exclusion_sources",
      "mcp__catchy-me__get_subscription",
      "mcp__catchy-me__get_payment_status",
      "mcp__catchy-me__list_leads",
      "mcp__catchy-me__get_lead",
      "mcp__catchy-me__get_search_funnel",
      "mcp__catchy-me__export_search",
      "mcp__catchy-me__get_outreach",
      "mcp__catchy-me__list_outreach_presets",
      "mcp__catchy-me__get_outreach_lead",
      "mcp__catchy-me__get_message_variant",
      "mcp__catchy-me__list_searches",
      "mcp__catchy-me__get_search",
      "mcp__catchy-me__get_search_requirements",
      "mcp__catchy-me__quote_search"
    ],
    "ask": [
      "mcp__catchy-me__catchy_info",
      "mcp__catchy-me__sign_up",
      "mcp__catchy-me__resend_sign_up_code",
      "mcp__catchy-me__confirm_sign_up",
      "mcp__catchy-me__sign_in",
      "mcp__catchy-me__request_password_reset",
      "mcp__catchy-me__reset_password",
      "mcp__catchy-me__accept_legal",
      "mcp__catchy-me__suggest_company_description",
      "mcp__catchy-me__suggest_goals",
      "mcp__catchy-me__suggest_audiences",
      "mcp__catchy-me__parse_exclusions_file",
      "mcp__catchy-me__extract_site_file_text",
      "mcp__catchy-me__create_search",
      "mcp__catchy-me__subscribe",
      "mcp__catchy-me__quote_facts_on_request",
      "mcp__catchy-me__start_facts_on_request",
      "mcp__catchy-me__demote_lead",
      "mcp__catchy-me__diagnose_search",
      "mcp__catchy-me__revise_search",
      "mcp__catchy-me__new_outreach",
      "mcp__catchy-me__set_outreach_sender",
      "mcp__catchy-me__edit_sender_card",
      "mcp__catchy-me__suggest_outreach_essence",
      "mcp__catchy-me__set_outreach_essence",
      "mcp__catchy-me__set_outreach_funnel",
      "mcp__catchy-me__quote_outreach",
      "mcp__catchy-me__start_outreach",
      "mcp__catchy-me__quote_outreach_retry",
      "mcp__catchy-me__retry_outreach",
      "mcp__catchy-me__edit_outreach_message",
      "mcp__catchy-me__quote_message_rewrite",
      "mcp__catchy-me__rewrite_message",
      "mcp__catchy-me__apply_message_variant",
      "mcp__catchy-me__export_outreach",
      "mcp__catchy-me__edit_search_spec",
      "mcp__catchy-me__edit_criterion",
      "mcp__catchy-me__edit_pain",
      "mcp__catchy-me__edit_counter_signal",
      "mcp__catchy-me__set_search_strategy",
      "mcp__catchy-me__run_search",
      "mcp__catchy-me__continue_search",
      "mcp__catchy-me__control_search",
      "mcp__catchy-me__rename_search"
    ],
    "deny": [
      "mcp__catchy-me__cancel_subscription",
      "mcp__catchy-me__delete_search"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as catchy-me. Review it before you use it.

Capability tags behind 9 rules
  • mcp__catchy-me__resend_sign_up_code outbound
  • mcp__catchy-me__get_account private-data, untrusted-input
  • mcp__catchy-me__list_plans private-data
  • mcp__catchy-me__suggest_company_description outbound
  • mcp__catchy-me__get_lead private-data, untrusted-input
  • mcp__catchy-me__get_outreach_lead private-data, untrusted-input
  • mcp__catchy-me__edit_outreach_message outbound
  • mcp__catchy-me__get_message_variant private-data, untrusted-input
  • mcp__catchy-me__apply_message_variant outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.catchy-me/catchy-me/verify?hash=d32cdafccb90ec566542d4036645203fd0d8fc0e3718e599225d31a20129387c" | jq -e '.changed == false'

Pinned hash d32cdafccb90, from Nov 17, 2026, 12:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.catchy-me/catchy-me/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.catchy-me/catchy-me
[![Anlyon Radar](https://radar.anlyon.com/badge/com.catchy-me/catchy-me.svg)](https://radar.anlyon.com/servers/com.catchy-me/catchy-me)

Source: MCP Registry. Synced Nov 17, 2026, 12:18 UTC.

catchy-me MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the catchy-me MCP server safe?

No scan can promise that. What its definitions show: 66 tools, 46 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the catchy-me MCP server delete data?

Yes. 2 tools can delete, cancel or revoke something: cancel_subscription and delete_search.

Can the catchy-me MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: resend_sign_up_code.

What tools does the catchy-me MCP server have?

66 tools: 2 destructive, 1 irreversible, 43 write, 20 read. cancel_subscription, delete_search, resend_sign_up_code, catchy_info, sign_up, confirm_sign_up, sign_in, request_password_reset and 58 more.

Does the catchy-me MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the catchy-me MCP server send data to outside services?

4 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): resend_sign_up_code, suggest_company_description, edit_outreach_message and apply_message_variant.

Has the catchy-me MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 17, 2026.