"A guide to finding people on LinkedIn by their name" matching MCP tools:

• create_lead_gen_site

  WebZum - The Hosting Layer for AI-Generated Web Content

  Create a third-party LEAD-GENERATION page about a business (NOT a site for that business itself). Use this when the goal is to drive qualified search traffic to someone else's business — affiliate pages, review/guide pages, niche directories. The page is branded as an outside guide (e.g. "Best Roofers in San Diego"), refers to the business in the third person, and routes CTAs to the business's existing website. Differences from create_site: - Slug + page brand are SEO-vanity (e.g. "best-roofers-sandiego"), not the candidate's brand name. - Voice is third-party guide/reviewer — never first person. - Primary CTA is "visit their website"; phone/email demoted. - No specific pricing quoted; differentiators emphasized. - Locality is judged by category, not just address (IT/SaaS/agency stays category-wide even when a city is on file). Pass a business candidate object from search_businesses — that business is the one being PROMOTED. Requires authentication via API key (Bearer token). Generate an API key at webzum.com/dashboard/account-settings. The page generation happens in the background. Use get_site_status to check progress. Returns the businessId (a vanity slug) which can be used to access the page at /build/{businessId}.

  Connector

• manage_fuses

  Name Whisper — ENS Intelligence Layer

  Manage fuses on a wrapped ENS name. Fuses are permission bits that can be permanently burned to restrict what can be done with a name. Three modes: 1. **read** — Check which fuses are currently burned on a name 2. **burn_owner_fuses** — Burn fuses on a name you own (CANNOT_UNWRAP must be burned first) 3. **burn_child_fuses** — As a parent, burn fuses on a subname (e.g. burn PARENT_CANNOT_CONTROL on sub.parent.eth) Owner-controlled fuses: - CANNOT_UNWRAP — prevents unwrapping (MUST be burned first before any other fuse) - CANNOT_BURN_FUSES — prevents burning additional fuses - CANNOT_TRANSFER — prevents transfers - CANNOT_SET_RESOLVER — prevents resolver changes - CANNOT_SET_TTL — prevents TTL changes - CANNOT_CREATE_SUBDOMAIN — prevents creating new subnames - CANNOT_APPROVE — prevents approving operators Parent-controlled fuses (for subnames): - PARENT_CANNOT_CONTROL — parent permanently gives up control over the subname - CAN_EXTEND_EXPIRY — allows the subname owner to extend their own expiry WARNING: All fuse burning is IRREVERSIBLE. Fuses expire when the name expires.

  Connector

• match-prospects

  mcp-explorium

  Retrieves Explorium prospect IDs that are REQUIRED as input parameters for all prospect enrichment operations (enrich-prospects, fetch-prospects-events). **Input Requirements:** - Email OR (full name + company name) - Optional: phone number, LinkedIn URL, business ID **Returns:** Prospect IDs that MUST be provided to enrichment tools **Technical Requirements:** - enrich-prospects REQUIRES prospect IDs from this tool or fetch-entities - fetch-prospects-events REQUIRES prospect IDs from this tool or fetch-entities - Prospect IDs cannot be used interchangeably with business IDs **Use Cases:** Questions about specific people: - "Who is [Name] at [Company]?" - "Get me [Person's] contact information" - "Tell me about [Specific Person]" - Professional background of named individuals - Contact details, work history, social profiles of specific people **Data Characteristics:** - Provides verified, current professional data - Returns structured contact info (emails, phones) - Gives comprehensive B2B intelligence **Note:** fetch-entities returns include prospect IDs, so this tool is not needed after fetch-entities

  Connector

• contact_broker

  Venturu

  Send a contact message to a broker on Venturu by their profile slug. Requires an authenticated Venturu account. Set inquiryType to "buying" (default) for buyer representation or "selling" for seller representation. Provide the broker slug and the message to send. Use search_brokers to find broker slugs.

  Connector

• xmp4_guide

  xmp4 — Semantic code knowledge for your stack

  Usage guide for xmp4 tools — read this first to learn the correct workflow

  Connector

• get_guide

  Octodamus Intelligence Oracle

  Purchase the Build the House trading system guide via x402 on Base. Returns step-by-step x402 payment instructions. After completing the EIP-3009 payment ($29 USDC on Base), the API returns a download_url valid for 30 days. No API key required to purchase.

  Connector

• contact_broker

  mcp-server

  Send a contact message to a broker on Venturu by their profile slug. Requires an authenticated Venturu account. Set inquiryType to "buying" (default) for buyer representation or "selling" for seller representation. Provide the broker slug and the message to send. Use search_brokers to find broker slugs.

  Connector

• list_themes

  Slidev MCP

  Get a list of all available themes with style descriptions and recommendations. Call this to decide which theme to use. Returns a guide organized by style (dark, academic, modern, playful, etc.) with "best for" recommendations. After picking a theme, call get_theme with the theme name to read its full documentation (layouts, components, examples) before rendering. This tool does NOT display anything to the user — it is for your own reference when choosing a theme.

  Connector

• list_brands

  Real Real Genuine

  [BROWSE] List all active brands on the platform. Returns name, slug, headline, description, and product/brief counts. Use a brand slug with list_drops or list_briefs to filter by brand.

  Connector

• suggest_entity

  connect

  Search for existing entities (people, galleries, museums, auction houses, institutions, foundations, collectors) by name. Use this before creating a new entity to check for duplicates — the system includes ~2,500 major galleries, museums, and auction houses. Returns matching entities for autocomplete-or-create flow. If no match is found, create a new entity via create_entity.

  Connector

• list_brands

  Real Real Genuine

  [BROWSE] List all active brands on the platform. Returns name, slug, headline, description, and product/brief counts. Use a brand slug with list_drops or list_briefs to filter by brand.

  Connector

• get_author

  Exploit Intelligence Platform — CVE, Vulnerability and Exploit Database

  Get an exploit author's profile with all their exploits. Returns author name, handle, total exploit count, activity start date, and a paginated list of their exploits with CVE context. Use this when asked about a specific researcher like 'show me all exploits by Chocapikk'.

  Connector

• suggest_domains

  instadomain

  Generate domain name ideas from a keyword and check their availability. Args: keyword: A keyword or short business name (e.g. "taskflow").

  Connector

• contacts_add_channel

  dialogbrain

  🔗 Link a new channel identity (email, phone, LinkedIn, etc.) to an existing contact. When to use: - User learns a contact's email or phone and wants to save it - User wants to link a LinkedIn/Instagram profile to an existing contact - Adding a second channel for an existing person Requires contact_id (entity_id) from contacts.find.

  Connector

• move_rows

  Dock

  Atomically move N rows from their current sheet(s) to a target sheet inside the same workspace. Use for programmatic data migration: dropping a batch of agent-produced drafts onto the right sheet, reorganizing content across LinkedIn / Twitter / Substack tabs, etc. All-or-nothing: if any rowId doesn't belong to this workspace, the entire batch fails before any write fires. Idempotent: rows already on the target sheet are skipped (returns `skipped` count). Rows land at the destination sheet's tail in the order rowIds was supplied. Emits one `row.moved_surface` event per row that actually moved. Up to 500 rows per call.

  Connector

• fulltext_search_graph

  RationalBloks

  Search across ALL string properties of ALL nodes in a deployed graph using free-text queries. Unlike search_graph_nodes (which filters by specific property), this searches every text field at once. Perfect for finding knowledge when you don't know which property contains the answer. Example: query "quantum" searches name, description, summary, notes, and all other string fields. Returns nodes with _match_fields showing which properties matched. Optionally filter by entity_type to narrow results.

  Connector

• chieflab_connect_publish_account

  ChiefLab

  USE WHEN the user wants to connect a social account (LinkedIn / X / Threads / Instagram / Facebook / Bluesky / TikTok) so chiefmo_publish_approved_post can post to it. Returns a Zernio OAuth URL — surface to user → they click → connect their account → it appears in chieflab_list_publish_accounts. Standard agent flow: call this with platform='linkedin' → get authUrl → surface to user → user connects → call chieflab_list_publish_accounts to confirm + grab accountId → pass accountId to chiefmo_publish_approved_post. NOTE: Zernio requires a profileId (the workspace container). If you don't pass one, the call fails with 'Profile ID required'. Get it from app.zernio.com/settings/profile, or call chieflab_list_publish_accounts first — the accounts response includes profileId on each item.

  Connector

• ateam_get_workflows

  ateam-mcp

  Get the builder workflows — step-by-step state machines for building skills and solutions. Use this to guide users through the entire build process conversationally. Returns phases, what to ask, what to build, exit criteria, and tips for each stage.

  Connector

• web_search_exa

  exa

  Search the web for any topic and get clean, ready-to-use content. Best for: Finding current information, news, facts, people, companies, or answering questions about any topic. Returns: Clean text content from top search results. Query tips: describe the ideal page, not keywords. "blog post comparing React and Vue performance" not "React vs Vue". Use category:people / category:company to search through Linkedin profiles / companies respectively. If highlights are insufficient, follow up with web_fetch_exa on the best URLs.

  Connector

• openmandate_verify_contact

  OpenMandate

  Verify a contact by submitting the OTP code sent to it. The user must check their email for the 8-digit code. After verification, the contact can be used on mandates.

  Connector