"Developing a Bulk Email System" matching MCP tools:

• verify_bulkA

  ClearBounce Email VerificationA

  Verify a list of email addresses (2 to 10,000) as one bulk job using the full ClearBounce bulk pipeline — per-domain caching and greylist retries give better accuracy than verifying one by one. Costs 1 credit per unique address; duplicates are removed for free. Returns a jobId immediately (the job runs in the background, roughly 1-10 minutes depending on size). Use check_bulk_status with the jobId to get progress and the final summary. Before starting a large list, confirm with the user that spending that many credits is intended.

  ConnectorNo auth

• create-design-systemA

  Better DesignA

  Starts generating a custom design system from a description of the product and its look, and returns the project id and project URL at once. Generation runs in the background and typically takes 1 to 3 minutes. get-design-system-status reports progress and returns the install command when it finishes. `baseDesignSystemId` starts from a catalog system the user picked, `userConfirmedCustom` records that the user chose fully custom, and `brandCss` builds from an existing brand token sheet, such as the output of extract-design-system. With none of the three, it generates nothing and returns the top catalog matches to show the user. Each call uses one credit from the user's Better Design account. Anyone with the registry or preview URL can view the generated source and previews.

  ConnectorOAuth

• chieflab_send_approved_emailA

  ChiefLabA

  [chieflab_* alias of chiefmo_send_approved_email] Send an approved launch email through the email sending rail (current adapter: resend). USE WHEN the user has approved an email publishAction from chiefmo_launch_product and you need to fire the send. Strict approval gate (same shape as chiefmo_publish_approved_post). `from` MUST be on a domain verified at the adapter (resend.com) — check chieflab_list_email_senders first. Single recipient or short list (≤50). Money/external-system action — once sent cannot be unsent.

  ConnectorNo auth

• chieflab_send_approved_emailA

  ChiefLabA

  [chieflab_* alias of chiefmo_send_approved_email] Send an approved launch email through the email sending rail (current adapter: resend). USE WHEN the user has approved an email publishAction from chiefmo_launch_product and you need to fire the send. Strict approval gate (same shape as chiefmo_publish_approved_post). `from` MUST be on a domain verified at the adapter (resend.com) — check chieflab_list_email_senders first. Single recipient or short list (≤50). Money/external-system action — once sent cannot be unsent.

  ConnectorNo auth

• manage_email_outreach_queueA

  SliqA

  <summary>Manage the email outreach queue. Email outreach items are queued and sent at staggered intervals. Use this tool to check status, update/cancel items, or approve pending items. Bulk operations (status, approve-all, cancel_all) act on the current agent's queue when run inside an agent, and across the whole account from account-level chat — except a bulk cancel_all or approve-all, which from account-level chat is rejected unless agent_id names the campaign, so it can't hit every campaign at once. Targeting one person by recipient_email reaches them in any agent. The next send time and per-mailbox usage stay account-wide (the send rate is per-mailbox). For pausing/resuming the campaign, use update_agent to set the agent status to 'paused' or 'active' instead.</summary> <returns> <description>Dict with action result and current queue status</description> </returns>

  Connector

  Destructive

  OAuth

• batch_modify_labelsA

  gmailA

  Add and/or remove the same labels on many email messages at once in a single Gmail API call (wraps users.messages.batchModify). Use this for bulk operations such as marking multiple specific emails as read (remove ['UNREAD']), archiving (remove ['INBOX']), or starring (add ['STARRED']). Use list_labels to find label IDs (Gmail requires IDs, not names). Common system label IDs: INBOX, STARRED, IMPORTANT, UNREAD, SPAM, TRASH. Provide 1-1000 email IDs and at least one of `add` or `remove`. The same label changes are applied to every listed message. Gmail returns no per-message status, so a successful call means Gmail accepted the request; an invalid email ID or label ID typically causes Gmail to reject it.

  ConnectorOAuth

• move_emailA

  Local MCPB

  Moves an email to another mailbox (nested target folders are found by name). Pass account= (returned by list_emails/search_emails) so the message lookup targets one account instead of scanning all of them — without it, multi-account Macs are slow and can time out on bulk moves. If you know the folder the message is in, also pass mailbox= (the `mailbox` field from the listing) so the lookup searches it first.

  Connector

  Destructive

  OAuth

• v3_breaking_nowA

  V³ NewsA

  Get events V³ is currently tracking in BREAKING tempo — fast- moving stories under near-real-time monitoring right now. Use when the user asks "what's breaking", "any breaking news", or about a developing situation. Returns an empty list when nothing is in breaking tempo (a quiet news moment), which is itself a signal.

  ConnectorNo auth

• verify_listA

  Qualisend Email VerificationA

  Verify a large list of up to 1000 email addresses. This runs ASYNCHRONOUSLY: it creates ONE bulk job, returns a job_id immediately, and the mailbox probes run in the background. Poll get_verification with the job_id for progress and a result summary (counts by verdict). Consumes 1 credit per address. For lists larger than 1000, use the Qualisend dashboard or bulk API.

  ConnectorNo auth

• bulk-manage-space-suggestionsA

  docuwriterA

  Use this when the user wants to apply or discard multiple Autopilot/repository-sync suggestions at once. Destructive state-changing action: bulk apply can update multiple Space documents, and bulk discard removes suggestions from active review after authorization. Requires suggestion IDs from list-space-suggestions; bulk apply requires Enterprise access.

  Connector

  Destructive

  OAuth

• generate-cold-emailA

  GigSoul x402A

  Write a first-touch cold email for a product and audience: subject line, preview text, and a 100-150 word body. Use for the opening message. For the follow-ups after no reply, use generate-follow-up-sequence. To check spam risk before sending, use check-email-deliverability. Pay-per-call: $0.05 USDC on Base via x402. Without a payment-signature header the call returns an error whose data carries the payment terms.

  ConnectorNo auth

• analyze-email-deliverabilityA

  GigSoul x402A

  Full deliverability audit of email copy: 0-100 score, every flagged phrase with its reason, subject-line risk, concrete rewrites, and SPF/DKIM/DMARC reminders. Use when a draft failed or warned in check-email-deliverability, or before an important send. For a quick pass/fail on many emails, use check-email-deliverability. Content signals only; no inbox-placement guarantee. Pay-per-call: $0.04 USDC on Base via x402. Without a payment-signature header the call returns an error whose data carries the payment terms.

  ConnectorNo auth

• check-email-deliverabilityA

  GigSoul x402A

  Fast, cheap spam-risk gate for one email: pass/warn/fail, a 0-100 score, and up to 3 flagged phrases. Use for a go/no-go before sending or for bulk screening of many drafts. No rewrites. For a full audit with reasons, subject-line risk, and rewritten copy, use analyze-email-deliverability. Content signals only; no inbox-placement guarantee. Pay-per-call: $0.005 USDC on Base via x402. Without a payment-signature header the call returns an error whose data carries the payment terms.

  ConnectorNo auth

• generate_emailA

  GenerectA

  Find and verify a work email. BILLABLE — about $0.02 per VALID email found (a miss is free) (Tier 0 list price; your account may pay a different rate — call get_balance for your real prices, and read cost.amount_charged in every response for what was actually spent). Identify the person by lead_id (best), LinkedIn URL, or first+last+domain. `candidates` resolves several people in one call; more than 10 is routed to an async bulk job instead, which returns a job_id for get_bulk_job.

  ConnectorOAuth

• verify_emailsA

  email-verifierA

  Bulk-verify a LIST of email addresses. Submits the whole list, waits for completion, and returns one result per email (same fields as verify_email). Best for cleaning lead lists. Charges 1 Fox Credit per email. Large lists that don't finish quickly return a jobId to poll with get_job.

  ConnectorNo auth

• create_agentA

  Fine StructureB

  Create an autonomous AI agent on the user's Fine Structure account: a standing worker, not a chat session. It gets the platform's default safe tool policy and its own email address, it can read and write the app database, and once the owner phone is verified (see get_agent_whatsapp) it can message its owner on WhatsApp and by email through the platform system channels. Pair it with schedule_agent_task for recurring work such as following up new leads on WhatsApp each morning, watching an app for runtime errors, or sending a weekly summary. Messaging anyone other than the verified owner requires a channel the owner connects in the Fine Structure Studio.

  ConnectorNo auth

• get_test_addressA

  email-spam-testerA

  Reserve a single-use address to send a draft email to, for a full check. Returns the address and the URL its report will appear at. The address accepts exactly one message and expires after an hour. The email has to be sent by the person, from the platform or mailbox they really send from: half the checks read what that platform adds. The report covers 42 checks (SPF, DKIM, DMARC, reverse DNS, TLS, blocklists, content, links, the Gmail and Yahoo bulk-sender rules) and a plan of what to fix. lang is decided now because the message arrives minutes later over SMTP, which carries no hint of who is waiting for it. What wait_for_report returns quotes check lines in English whatever it is set to; the person following report_url sees their own language.

  ConnectorNo auth

• oryksa_set_allowed_domainsA

  ORYKSA AI EmployeesA

  Restricts the chat widget to the site's domains (subdomains included), so the widget token cannot be used on other sites. Send the production domain and any staging domain, e.g. ["example.com", "example.vercel.app"]. Send an empty list to allow any site (useful while developing on localhost).

  ConnectorOAuth

• create_quote_requestA

  MaterialHandling.comA

  Create a real quote request in the MaterialHandling.com sales system. A human equipment specialist prices it (volume pricing + freight) and emails the finished quote, usually within one business day. Use when the customer wants formal/volume pricing. Requires the customer's real name and email — always confirm these with the customer before calling. Returns the quote number. Rate-limited to 5/hour.

  ConnectorNo auth

• meisa_send_emailA

  MeisaA

  Send a triggered (transactional) email to a single email address via a pre-configured Meisa email trigger. Use this when the user wants to send a one-off email to a specific person (e.g. a verification code, password reset, or notification). The trigger_key must already exist in Meisa (use meisa_list_triggers to find available triggers). This sends a real email immediately. Do NOT use for bulk/broadcast emails — use meisa_send_broadcast for that instead.

  ConnectorOAuth

• compass_links_createA

  ZeroWidth CompassA

  Creates a typed, directed edge between two pages — the knowledge graph's connective tissue. Canonical directions: PERSON owns WORKFLOW/SYSTEM, PERSON involved_in WORKFLOW, WORKFLOW uses SYSTEM, SYSTEM uses SYSTEM, PAIN_POINT affects WORKFLOW/SYSTEM/PERSON, DOCUMENT documents anything, relates_to as fallback. Idempotent on (from, to, kind) — re-creating an existing edge returns it. May return `needs_confirmation`; tell the user what you're proposing, wait for their approval, then re-call with the approvalId.

  ConnectorNo auth