"Searching for people on Twitter by name" matching MCP tools:

• search_ens_namesA

  Name Whisper — ENS Intelligence LayerA

  Search ENS names using natural language. Supports all query types: - Filtered search: "4-letter words under 0.1 ETH" - Concept search: "ocean themed names" (semantic similarity across 3.5M indexed ENS names) - Creative search: "names for a coffee brand" (AI-generated suggestions) - Collection search: "crypto terms expiring soon" - Activity: "what sold recently?" - Availability check: "is coffee.eth taken?" - Bulk check: "check apple.eth, banana.eth, cherry.eth" - Collection/club floor: "999 club floor", "cheapest 10k club names" (returns real listings sorted by price) - Sorted pattern list: "3-letter numbers sorted by name", "4-letter words by registration date" (sorts by name, price, length, expiry or registration date) Returns structured results with name, price, owner, tags, and availability info. It searches the NAME database by pattern/length/price/club/vibe — it does NOT know who real-world people, teams, brands, athletes, musicians, or films are. For "find me NBA players / pop stars / Pixar films / presidents" use enumerate_entities instead (it returns correctly-spelled labels). Use this for "floor of <club>" / "cheapest in <collection>" (find_alpha can't — it has no collection param). For lifecycle-window lists — "which names are in premium / Dutch auction", "names in grace period", "expiring soon" — use get_expiring_names instead: its grace/premium statuses are on-chain-validated and premium rows carry live pricing. That hand-off needs a lifecycle WORD in the query. A plain pattern/length/digit list — "3-letter numbers sorted by name", "4-letter words", "5-digit names" — stays HERE even though it asks for a list with filters and a sort order; routing it to get_expiring_names answers a question the user never asked (a grace/premium dump instead of the names).

  ConnectorNo auth

• find_subjectsA

  QuillHubA

  Search for tracked subjects (people, deals, projects, clients, candidates, custom types) within a workspace. Returns lightweight cards with id, name, type, aliases, a living-note summary (`note` — free-text markdown maintained by the AI across meetings), open `commitments` (deadlines live inside the text), and mention counts. `query` matches the name AND aliases, tolerant of ru/en transliteration — «микролёрнинг» finds a subject whose alias is "Microlearning", "SDG" finds «СДГ». `type` filters by subject-type slug: builtin (deal, project, client, candidate, person) or any custom slug defined in the project (e.g. team_member, workstream) — discover available slugs with `list_subject_types`. Omit `type` to search across all types. Use this before calling `get_subject_page` to find the right subject id.

  ConnectorOAuth

• contacts_searchA

  mcpA

  Lusha: looks up 1-25 known business contacts by Lusha ID, name+company, LinkedIn URL, or email. Use when: fetching contact details for known specific contacts (single or batch up to 25). Do not use when: searching for contacts by criteria (prospecting_contact_search covers that case). Optional 'enrich' bundles reveal data; pass false for preview-only, then prospecting_contact_enrich with each result's `canReveal[].field`. Returns: Lusha contact profiles with available business data. Credits: consumes 1 Lusha credit per successful lookup; adds reveal credits when enrich is true (default). Rate limits apply per Lusha plan (per-minute/hourly/daily); exceeding returns HTTP 429. The account_usage tool returns current limits and remaining headroom.

  ConnectorOAuth

• linkedin_search_peopleA

  Veezee: LinkedIn people & company data for agentsA

  Find people on LinkedIn by keywords and filters. The right tool when you have a name, role, or 'who is the X at Y' question without a profile URL. Pass keywords (free text: name, title, or both) and any of first_name, last_name, title, school, current_company, past_company. If keywords is omitted it is derived from the name or title filters; school or company filters alone are rejected with INVALID_INPUT, so include keywords with those. Company filters accept a company name, slug, numeric id, or URN. current_company names are matched by LinkedIn's own company search: typo-tolerant and fuzzy, so results can include people whose headline merely mentions the company; when you need exact filtering, pass the numeric id or URN (linkedin_get_company returns both). past_company names are resolved to an id for you. Costs 10 credits including the first 10 results; each further 10 results add 1 credit (limit max 30; trial keys max 10). A cursor page is a NEW call priced the same way by its own limit, so one limit=30 call is much cheaper than three limit=10 pages; prefer a larger limit over paginating. Do NOT combine a past_company NAME or a company-URL filter with limit=30: resolving those spends one of the call's three internal fetches, so that combination is rejected; keep limit<=20 with them or pass the numeric id. current_company names never spend a fetch, so they combine with any limit. Returns name, position, location, urn, public_identifier per result, a cursor for the next page, and total_matches. Results with is_anonymous=true are private profiles; do not pass them to linkedin_get_profile. For one known person with a URL/slug, call linkedin_get_profile directly instead.

  ConnectorOAuth

• searchProductsA

  dm-drogerie-marktA

  Search for products available in the German dm-drogerie market (online and local stores). USE WHEN: searching dm-drogerie products by name, category, ingredient, property, or any natural language query (any language supported). Often answers questions about ingredients and properties directly. Covers: dm-drogerie markt brands, make-up, skincare, perfume, hair, health, nutrition, baby & child, household, home & living, photo, and pets. OUTPUT: Returns a maximum of 15 products. GTIN, DAN, brand, title, details, category, price, appLink (direct product URL), description, highlights/USPs, and extensive attributes including: - Dietary/Allergen: vegan, vegetarian, bio, glutenFree, lactoseFree, sugarFree, nutFree, soyFree - Cosmetic Ingredients: fragranceFree, alcoholFree, parabenFree, sulfateFree, preservativeFree, dyeFree, oilFree, siliconeFree, naturalCosmetics - Product Properties: waterproof, new, limitedEdition, sellout, onlineOnly, exclusiveDm, dmBrand, purchasable NOT FOR: nutritional information (calories, protein, carbs, fats), complete allergen lists, full ingredient details. For these, use 'getProductDetails' tool with the GTINs or DANs. LIMITATIONS: Only make claims based on EXPLICITLY stated product highlights/descriptions. Do NOT extrapolate or assume properties not mentioned in the results.

  ConnectorNo auth

• firmaradar_check_aml_pepA

  FirmaradarA

  Screen ONE natural PERSON's full name against sanctions (OFAC, EU, UN) and PEP lists. IMPORTANT — this is a PERSON tool only. Do NOT pass a company name, an organisation number (orgnr), or any non-person string here. For company-level AML risk use `firmaradar_get_aml_score` (by orgnr); to screen a company's owners/officers, first resolve the people via `firmaradar_get_company_roles` / `firmaradar_get_company_ownership`, then screen each PERSON name with this tool. Compliance-critical: PII-sensitive, requires a signed DPA and a legitimate purpose per call (free-text `purpose` parameter). Audit-logged for 60 months. Rate-limited to 50 calls / 30 min per API-key. Returns structured hits with category, sources, and match-ratio (default min 0.85).

  ConnectorNo auth

• social_searchA

  socialbridge-mcpA

  Search a single network for posts matching a query, returned as the unified Post[] schema and tagged with its platform. Keyless on TikTok, YouTube, and Pinterest. Instagram, Twitter/X, Reddit, and Facebook need operator-side credentials (returns credentials_required until set). Snapchat and Threads do not support keyless search (returns not_supported); LinkedIn is quarantined. To fan one query across every network at once, use search_all.

  ConnectorNo auth

• search_locationsA

  whentoflyA

  Resolve a city or airport name or code before searching flights. Returns typed values such as city:SHA to search every catalog airport in Shanghai or airport:SHA for Hongqiao only. Pass the selected value unchanged to search_flights. Ask the traveler when multiple results are plausible.

  ConnectorNo auth

• random_usersA

  Synthetic Data — Random UserA

  Generate synthetic / fake user profiles via the MwVideos random_users API (POST /mwvideos/api/random_users). Returns name, gender, location, email, login, dob, phone, picture, and nat. Use when the user asks for random users, fake people, sample contacts, demo personas, UI fixtures, or test profiles. Pass `results` for how many profiles (default 1, minimum 1) and `isPro` as 0 or 1 when relevant (default 0). Authenticated user_id is injected server-side — do not invent profiles; always call this tool. These are FAKE people for demos and testing, not real PII.

  ConnectorOAuth

• screen_names_by_partyA

  Court DeltaA

  Triage a SHORT list of people for North Carolina (NC) court cases. Built for the "here is a list of names, which ones have cases?" question — a CSV of applicants, tenants, or bond clients. **This server cannot accept file uploads:** read the file yourself and pass the names as an array. Returns COUNTS AND FACETS PER NAME, not case detail — `matched`, `case_count`, `counties`, `case_types`, `case_numbers` (first few), `portal_truncated`. That keeps a 5-name response readable. Once you know which names are interesting, call `search_cases_by_party` (full rows) or `lookup_court_case` (one case) on those. LIMITS, and why they are low: each name runs a LIVE portal search, and the upstream session token is shared by every user of this service — a wide fan-out risks blocking it for everyone. Max 5 names per call, 3 at a time. Split a longer list across calls. SLOW BY NATURE: measured ~60s for 3 names and ~2 minutes for 5. Tell the user you're checking and roughly how long it takes; don't retry on a slow response, and don't treat the wait as an error. If your client's timeout is tight, send fewer names. PARTIAL RESULTS ARE NORMAL: one name failing (portal hiccup, timeout) does not fail the batch — that entry comes back with an `error` and the rest still return. Report which names were checked and which weren't; never present a failed name as "no cases found", because those mean completely different things. `portal_truncated: true` on a name means the portal hit its statewide 200-case cap, so that person's count is a LOWER BOUND — narrow with `county`, `case_status`, or a filed date range and re-run that name. Dates: ISO `YYYY-MM-DD` or `MM/DD/YYYY` — both accepted. `file_date_*` bounds when the case was FILED, not when a hearing is scheduled. Matching is exact on last + first name (no soundex here — it broadens results and would make a screening list noisier). A common name will match multiple different people; `case_count` is "cases matching this name", NOT "cases belonging to one person". There is no DOB or identity confirmation in this tool — do not treat a hit as identifying a specific individual. Read-only. NC only. Public records. Informational, not legal advice.

  ConnectorNo auth

• x_get_profileA

  Veezee: LinkedIn people & company data for agentsA

  Fetch one X account's profile: name, bio, location, website, follower/following counts, tweet and media counts, verification state, and join date. identifier accepts a screen name without the @ (e.g. 'nasa'), a full x.com or twitter.com profile URL, or the numeric account id; numeric strings are treated as ids, and the rare all-digit handle can be forced with by='screen_name'. Costs 4 credits. The returned platform_fields.id is stable across handle changes; store it for repeat lookups. To find accounts by topic use x_search type=people, and to read what an account posts use x_get_tweets; this tool returns no tweets.

  ConnectorOAuth

• send_feedbackA

  agtrepo-memoryB

  Free. Sends a message to the human operators of this service: a bug report, a problem with these tools or the documentation, or a suggestion. It is read by people, not processed by software, and nothing is returned beyond an acknowledgement. Do NOT use it for status updates, progress notes, task narration, error logs, or as a fallback when another tool is unavailable or a payment cannot be made -- it cannot complete, retry or work around any task. Name is optional (omit for anonymous feedback); message is limited to 1000 characters.

  ConnectorNo auth

• lookup_taxpayerA

  StackinA

  Look up one taxpayer by exact tax id, to confirm who it is. Use it to check a recipient's name before issuing against them. It takes the id exactly — punctuation is fine, but there is no search by name, by prefix or by state, and there will not be: the registry holds the names and addresses of real people. A 404 does not mean the company does not exist. The registry reloads monthly from the RFB's dump, so a recently registered CNPJ is simply not in it yet. Say that to the user rather than reporting the tax id as invalid, and never turn a 404 here into a validation rule.

  ConnectorNo auth

• add_lead_finder_prospectsA

  EmailchaserA

  SPENDS CREDITS, AND BY DEFAULT METERED EMAIL VERIFICATION. Adds people from the Lead Finder contact database to a campaign as leads, revealing their contact details, in the background. Pass refs (from search_lead_finder results; up to 1,000 different people by default) to add exactly those people, or pass filters and count (1 to 5,000 by default) to add count people matching the filters who are not in the workspace yet. A filters add always walks the matches from the top and skips anyone already a lead, free and not counted, so repeating the same add adds the NEXT count people and charges again. Never repeat an add to retry: after an error or a timeout, call list_lead_finder_imports to see whether it started. A filters add stops early when the audience runs out or once it has looked at five people for every one requested (at least 1,000). People already added count toward that limit even though skipping them is free, so after an add of more than about 1,000 people a small follow-up can stop with nobody added. Every person a filters add looks at, added or skipped, also uses the account's daily allowance for filters adds (25,000 people by default). Each person added costs 1 credit ($0.033 at list), reported as creditsPerProspect; the response reports estimatedCredits, the most the add can cost in credits, and the wallet must hold that much for it to start. People already in the workspace, blocklisted, without a usable address, on a personal mailbox when the campaign only takes business addresses, or marked invalid by verification are skipped and cost no credits. verifyEmails (on by default) checks every screened address with the paid email verification waterfall, including the ones it marks invalid: one or two checks per address, billed as metered usage on the next invoice (price per check: GET /email-verification/rates in the REST API), within the account's monthly verification spend limit. Catch-all and unconfirmed addresses are added and charged, and so is every address once that limit is reached; verification.limitReached and verification.unknown on get_lead_finder_import count them. Leads added to a running or paused campaign get their emails at once (a paused campaign sends them when resumed); adding to a completed campaign resumes it, so it starts sending again; in a draft campaign the emails are created at launch. At most 3 adds run at once in a workspace. A refusal names its reason, and a 429 also says when to retry (reason running_imports, daily_import_limit, daily_budget, monthly_budget or fair_use_floor). Poll get_lead_finder_import with the importId until finishedAt is set. Check get_credit_balance first; buy credits with purchase_credits.

  ConnectorNo auth

• get_apartment_detailsA

  Das Landhaus Apartments PrägantA

  Describe one or all apartments: size, bedrooms, maximum guests, description and page link. Use for questions about the apartments themselves ("how big is #16?", "which apartment has 2 bedrooms?", "which apartments fit 5 people?"). It contains no prices or availability — use check_availability for dates and prices, or get_rates for a month overview. Studio #17 is only listed when asked for by number and is marked as bookable on request. Visual version with photos: render_apartment_gallery. Behaviour: read-only; facts as maintained on praegant.net (synced hourly), answers in milliseconds. Returns text plus structuredContent.apartments (nr, name, m2, bedrooms, max_guests, description, url, on_request, images, and where maintained: beds, outdoor, notes, recommended_for). An unknown number returns the list of existing apartment numbers.

  ConnectorNo auth

• search_contactsA

  AccountHubA

  Search the user's Google Contacts (saved contacts + Google's auto-collected "other contacts") across all connected Google accounts, by name (or partial name/email). Returns each match's name, primary email, full email list (for people with several addresses), and source ('contact' = saved, 'other' = auto-collected). Use this to resolve a person's NAME to an email address before composing/sending a message — on 0 matches, fall back to searching past message history or ask the user directly; on multiple matches, ask the user which one before proceeding. Accounts without the contacts scope are skipped and reported in `errors` with a reconnect hint. Call list_accounts to learn account labels. Read-only — no contact writes.

  ConnectorOAuth

• leads_search_peopleA

  Manifold MCPA

  People matching title, seniority and company filters. No email. Use when: "find heads of marketing at fintech startups", building a target list by role, prospecting by ICP. Not for: someone to email at a specific website about a link, use leads_get_domain_emails (keyed by domain). One person's full record, use leads_get_person. An email for a named person, use leads_get_email. Returns: List. rows[]: id (the LinkedIn profile URL; null when the person has no profile, so look them up by name and domain), first_name, last_name, headline, title, title_start (YYYY-MM, so time in the role), company, company_domain, company_id, company_linkedin_url, company_employees, company_industry, location, linkedin_url. rows_available is the provider's total. Give at least one of titles, seniority, company_domains, industries, locations or keywords. A page holds at most 100 rows whatever the limit; page on with meta.cursor. Cost: 12 credits per 100 rows asked for (limit), rounded up. Default 12 credits. Cached 7 days. Example: {"titles": ["head of marketing"], "industries": ["fintech"], "locations": ["London"], "limit": 50}

  ConnectorAPI key

• get_profileA

  teas.co.ukA

  Use this to confirm which teas.co.uk account is linked, for example before my_orders, my_subscriptions or rewards_balance, or when the customer asks which account they are signed in with. It takes no input: the account comes from the sign in. It returns an opaque account id that stays the same across sign ins and reconnections, with a display name and email for showing to the customer. Without a linked account it returns an error, with a sign in prompt where the host supports one. Not needed for shopping: searching, the basket and checkout work without an account.

  ConnectorNo auth

• apione_people_searchA

  ApiOne B2B Enrichment (GCC and MENA)A

  Finds people by current company, title, country (ISO-2) or location and returns name, title, company and profile link, up to 25 results. Use to identify who to contact at a company. Work emails are not included: call apione_email_find for each person you want. Give at least one filter. Set count to cap spend. Not for details on one named person (use apione_people_enrich). Cost: 3 credits per result returned, so a full page of 25 results costs 75. No results, no charge.

  ConnectorNo auth

• well_create_custom_columnA

  WellA

  Create a new custom column on the current view in the workspace. Use this tool when the user asks to add, create, or set up a new column on the active grid (e.g. "add an Industry column", "create an AI column that scores risk"). REQUIRED: name, type - type: one of text, number, amount, date, boolean, single_select, multi_select, record_reference, ai - a `record_reference` column also REQUIRES the root its values point at: one root in `reference_target`, or two or more in `reference_targets` when a cell may name records of several roots (for example people and companies). Send one of the two, never both. A column of people is how a person is held, so "an owner column" or "who handles it" is type=record_reference with reference_target=people. No other type takes a reference target. OPTIONAL: icon, rules_config, formula_config, format_config, reference_target, reference_targets, is_multiple - is_multiple: for a `record_reference` column only. Pass true when one cell holds a list of records (for example "the people on this deal"); leave it out when a cell holds one record. On a grid, the column is always created on the user's currently mounted view: you do not (and cannot) choose a different one, and you do not ask which view. With no grid (an assistant app, or a creation off-grid), pass `root`: the view the user named, one of companies, people, invoices, transactions, account_balances, projects. If the user named no view, ask which one before calling. If the user named a table that is not in that list (for example products or tasks), do not call this tool and never put the column on another table: say in one line that this table cannot take a custom column yet, and name the tables that can. Naming: `name` must be unique within the current view. If a name conflict is likely, ask the user to disambiguate before calling rather than retrying after a failure response. Position: the new column is auto-placed at the end of the view. You cannot set position via this tool. Side effect: creating a column on a populated view automatically schedules an asynchronous recompute of all rows. You will not receive a tracking handle — values appear in the grid as workers finish. Returns { success: true, custom_column_id, name, root, type } on success, or { success: false, error } on failure.

  Connector

  Destructive

  No auth

• list_contactsA

  IgnixA

  List and filter the CRM contacts (people who have written to or interacted with the connected accounts), each with `id`, `name`, `email`, `tags`, `subscribed` and `platform`, plus `count` with the total that matched before the limit. Use it to find a person or a segment; for one person's channels, custom fields and notes use get_contact, and for their messages list_conversations. Returns 40 by default and at most 200: if `count` is higher, narrow with tag, search, platform or accountId. The `id` is what get_contact, update_contact, set_contact_field and enroll_in_sequence take.

  ConnectorOAuth