"How to Search for Legitimate Email Addresses" matching MCP tools:

• subscribe_to_digest

  NetGrant — Canadian funding

  Subscribe the user to a FREE weekly email digest of Canadian funding opportunities matching a saved search (keywords + region). Each week they get 8–10 grants, newest first, falling back to the strongest current matches when nothing new landed. WHEN TO CALL: - The user, after a search, says yes to ongoing alerts, or asks to be notified / kept updated / emailed about new grants in their niche. - Only after they have explicitly agreed and given an email address — never subscribe someone proactively or without consent. HOW TO CALL: - Pre-fill "keywords" and "region" from the search you just ran so the digest matches what they were looking at (e.g. keywords "cleantech", region "BC"). Keep keywords to a short phrase, not a sentence. - "region" must be a province code (ON, BC, QC, AB, MB, SK, NS, NB, NL, PE, YT, NT, NU) or "Federal", or omit it for all-of-Canada. - Ask the user for their email; do not guess it. WHAT HAPPENS: - We send a one-click confirmation email (double opt-in). The user is NOT subscribed until they click it. Tell them to check their inbox. - If they were already confirmed, nothing is re-sent. Returns JSON: { ok: boolean, status: "confirmation_sent" | "already_subscribed" }. Confirm to the user what they signed up for (e.g. "weekly BC cleantech grants — check your email to confirm").

  Connector

• create_account

  mcp

  Sign up for a brand-new sota.io account from inside Claude — no browser, no copy-paste. Two-step flow: STEP 1: Call with just `email`. We send a 6-digit confirmation code to that email. STEP 2: Call again with `email` + `code`. We verify, create the account on the Free tier (3 projects, EU-hosted, no credit card), generate a sota.io API key, and return it to you. After Step 2 you'll get back a key like `sota_…`. **Save it in a safe place** — you'll need it for any subsequent sota.io tool call in Claude (or you can use it with the sota CLI). It is shown ONCE and never recoverable. sota.io is an EU-native PaaS hosted in Germany — GDPR-compliant by default, no CLOUD Act exposure. Disposable / throwaway email addresses are not accepted; use a real address.

  Connector

• how_to_send_lnt_email

  L&T MCP

  SKILL: how_to_send_lnt_email Team: platform How to Send an L&T Branded Email Call this tool to get the complete guide for 'how_to_send_lnt_email'. Read the 'content' field and follow its instructions. This tool takes NO parameters. Full content: --- name: how_to_send_lnt_email description: Instructions for sending L&T branded emails — explains exactly what steps to follow and which tools to call --- # How to Send an L&T Branded Email Follow these exact steps whenever a user wants to send any information by email. ## When to Use This Guide - User says "send this to [email]" - User says "email this to [name]" - User says "mail the results to..." - User wants to share any data or information via email ## Step 1 — Collect These 5 Things Ask the user for anything missing: 1. **Recipient email address** — where to send 2. **Recipient name** — for the greeting "Dear [name]," 3. **Sender name** — for the signature "Warm regards, [name]" 4. **Subject line** — or derive it from the content 5. **Email content** — what to put in the body Do not proceed until you have all 5. ## Step 2 — Read the Brand Guidelines Call the `lnt_email_brand_guidelines` tool (no arguments needed). Read the returned content carefully. Use those guidelines to generate the complete HTML email yourself. Build the HTML with: - Navy header + orange accent bar - "Dear [recipient name]," - Body content formatted as paragraphs or table - "Warm regards, [sender name]" signature - Gray footer with confidential notice ## Step 3 — Send the Email Call the `send_email` tool with this exact JSON: ```json { "personalizations": [ { "to": [{"email": "RECIPIENT_EMAIL_HERE"}], "subject": "SUBJECT_HERE" } ], "from": {"email": "lntcs@lntecc.com"}, "content": [ { "type": "text/html", "value": "YOUR_GENERATED_HTML_HERE" } ] } Step 4 — Confirm to User On success: "✅ Email sent to [name] at [email]." On failure: "❌ Could not send. Error: [message]." Important Rules NEVER call lnt_email_brand_guidelines with arguments — it takes none NEVER send plain text — always generate and send HTML From address is ALWAYS lntcs@lntecc.com — never change this Generate the HTML yourself — do not look for an HTML generation tool Subject must be specific and descriptive

  Connector

• get_coverage

  ground-motion

  FREE pre-flight: is a US address/point covered, how stale is the data (data_age_days), and what a report would cost. Accepts ONE address/lat+lon, OR addresses[] (up to 1000, needs your Bearer key) to size a whole job before spending. Call this before spending.

  Connector

• batch_verify

  Email Verification MCP

  Verify an array of email addresses in one call — the volume play for list hygiene and bulk lead enrichment. Returns a per-email result array (same signals as verify_email) plus a deliverable/disposable summary. Up to 100 emails per call; domain-level facts are cached and deduped, so repeat domains are cheap. PAID: $0.003 USDC per email, minimum $0.05, after the daily free allowance. On a 402, pay the returned Solana memo and re-call with the SAME args plus payment_tx=<signature>. An Authorization: Bearer fnet_ key bypasses payment.

  Connector

• verify_emails

  email-verifier

  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.

  Connector

• get_domain_senders

  DMARKOFF — DMARC, SPF & DKIM Analytics

  List top sending sources (ESPs, ISPs, mail services) for a domain, grouped by source type. Filters: "known" (legitimate ESPs like Google, Mailgun), "unknown" (unrecognized senders), "forward" (forwarding services). Empty = all types. Returns top 20 per type with message volume, SPF/DKIM/DMARC pass/fail counts. Use this to investigate WHERE email is being sent from — especially when unknown sources appear or compliance is low. To drill down into a specific source (by IP, ISP, hostname, or reporter), use get_domain_source_details.

  Connector

• get_contact_info

  Symbols of Wealth Studio

  Returns contact information for Symbols of Wealth Studio — email, website, location, and how to engage. Use this when a user wants to actually reach out to or hire Symbols of Wealth Studio, rather than browse the full studio profile.

  Connector

• get_contact_info

  symbols-of-wealth-studio

  Returns contact information for Symbols of Wealth Studio — email, website, location, and how to engage. Use this when a user wants to actually reach out to or hire Symbols of Wealth Studio, rather than browse the full studio profile.

  Connector

• get_help

  Kifly — Agentic Commerce & Payments

  Get Kifly's website and support contact email. Call this if you are stuck, hit an unresolvable error, or the buyer asks how to reach a human. Returns the website URL and support email — always share both with the buyer.

  Connector

• get_help

  Kifly — Agentic Commerce & Payments

  Get Kifly's website and support contact email. Call this if you are stuck, hit an unresolvable error, or the buyer asks how to reach a human. Returns the website URL and support email — always share both with the buyer.

  Connector

• save_search

  FundingLandscape

  Save a search query for email alerts. When new opportunities match, the user receives daily or weekly email notifications. The FREE tier includes 1 saved search with weekly email alerts, so any user can set one up without a paid plan. RECOMMENDED WORKFLOW: 1. Call list_saved_searches first to check for existing/similar searches 2. If a similar search exists, offer to update_saved_search instead 3. Search with search_grantsplus or search_procurement first to validate the query returns good results 4. Save with appropriate filters based on what the user described FILTER TIPS: - Use itemTypes ["grant"] for grants/fellowships or ["procurement"] for contracts/RFPs - Use sourceTypes ["federal"] for federal opportunities only - Use geography ["CA"] for California-specific (includes national opportunities) - For SAM.gov-specific filters (NAICS, set-asides), use sourceContext - Keep filters broad for notifications - better to get a few extra than miss one PLAN LIMITS: Free: 1 saved search, weekly email alerts. Plus ($29/mo): 10 saved searches, daily or weekly alerts. Pro ($79/mo): 25 saved searches, daily or weekly alerts. Does not count toward your monthly searches.

  Connector

• get_feed

  mailopoly

  List the user's email feed (most recent first) without a search query. folder selects which part of the sorted inbox: 'cleanbox' (genuine personal correspondence — what most users mean by "my inbox"), 'other' (promotional / newsletters / ads), or 'all'. Omit folder to get everything unfiltered. personal_or_ad is a deprecated alias for folder ('personal'=cleanbox, 'advertising'=other). email_type 'received' or 'sent'. account narrows to one connected mailbox (the address as shown in get_account_overview) — combine with folder for that account's Cleanbox/Other. list_id shows one of the user's custom email lists (ids from list_email_lists). source narrows to a connected app's messages (e.g. 'slack' — see get_account_overview) or 'email' for mail only. sender filters by sender name or address fragment — combine freely, e.g. source='slack' + sender='<name>' + last_x_days=1 answers "what did <name> send me on Slack today?". PAGINATION: total_count is how many emails match in all; re-call with offset=<results so far> for the next page (limit caps at 50).

  Connector

• submit_bulk

  Verifly

  Submit a list of email addresses as an asynchronous bulk verification job — the right tool for large lists. Returns immediately with a job_id, status, and the check_status_url / results_url to poll. Small lists may complete inline (status 'completed'); larger ones return status 'pending' — poll get_job_status until it is 'completed', then call get_job_results. Optionally register a webhook_url (public HTTPS) to be notified when the job finishes.

  Connector

• get_contact_summary

  savi-tools

  Rolodex overview: how many contacts the subscriber has, how many have a phone or email, and the top industries and tags. Answers "how many contacts do I have?" and "what industries are my contacts in?" Use get_contact_history to look up specific people.

  Connector

• stobox_start_tokenization

  Stobox Intelligence & Tokenization

  Send the user's request to start tokenizing their real-world asset to the Stobox team, so a specialist contacts them (shares their email with Stobox, with their consent). Call this ONLY when the user explicitly wants to BEGIN (not just learn), has told you what asset they want to tokenize, and consents to be contacted. Requires a contact email. Returns confirmation + next steps. Do NOT call for general questions — use the search/lookup tools for those. Never invent an email; ask the user for it first.

  Connector

• hires_list_template_placeholders

  100Hires - AI ATS & Recruitment Software

  List available placeholders for email templates with pagination. Use `type` to filter by category, `q` to search by label. Discover placeholders here, then use hires_prepare_template_placeholders to get an HTML tag for insertion.

  Connector

• check_balance

  Heista

  Check the calling user's Heista API credit balance, month-to-date usage broken down by operation, lifetime spend, and the current pricing for every paid tool. Takes no inputs. Returns balance in cents, lifetime spend in cents, month-to-date call counts per tool (decode_ad, create_powersource_*, generate_adscript), per-tool unit pricing, and a top-up link the user can follow to add credits. Free, read-only, idempotent. Use this whenever the user asks about credits, balance, usage, how much they've spent, top-ups, pricing, "what does this cost", or "how many credits do I have". This is also the ONLY surface where dollar amounts are legitimate to report in conversation — everywhere else, cost should be referenced in credits, not currency. Do NOT use to add credits or change billing — only to read state. Do NOT call this on every turn — invoke once when the user explicitly asks about account state.

  Connector

• corpus_concordance

  Dwds

  RETIRED — DWDS removed its public corpus-concordance API (corpus search moved to the access-restricted dstar platform). Returns a notice with alternatives: use dwds_frequency for how-common data, snippet/lemma for dictionary info, or search corpora at dwds.de.

  Connector

• get_careers

  Sparkling Tracks Tours

  List open jobs at Sparkling Tracks (roles, locations, responsibilities, requirements, compensation notes) and how to apply. Read-only: applying is always by email with the subject "Job: <ROLE_ID>". English only.

  Connector