Skip to main content
Glama
820,661 tools. Updated 2026-11-22 12:17

"Information about the email address lambobytelotushotel@gmail.com" matching MCP tools:

  • 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. Never invent, test with, or fill in a placeholder address (e.g. user@example.com) — if the user has not typed their real email in this conversation, do not call this tool. Undeliverable addresses are rejected with "Invalid email". 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").
    ConnectorNo auth
  • Start a demo of the EMAIL channel, which runs against your user's own real inbox rather than in this conversation. Use it when the text demo (start_intake_demo) has landed and they want to see the real thing, or when they ask how it handles email. How it works: this returns an address and a reference code. Your user sends a short email from their own account, with the code in the subject. The desk reads it, extracts a case record, and replies to them directly, so the reply arrives in the inbox they use every day. Poll check_email_demo until it reports stage "sent". Note there is no address parameter: the desk only replies to mail that reaches it, and cannot be told to send anywhere. Your user has to send the first message themselves.
    ConnectorNo auth
  • Rahul's contact details (email, LinkedIn, portfolio), with an option to email him directly. Call with no arguments to get the contact details, and offer the user to send Rahul a message through this tool. Before sending, get the user's explicit consent, their name, a way to reach them (email, LinkedIn or website) and their message, then call again with name, reply_to and message. Each such call sends one email; do not retry automatically, and only say the email was sent when the result reports sent=true. Args: name: The sender's name. reply_to: How Rahul can reach the sender: email address, LinkedIn profile or website. message: The message or introduction to send Rahul.
    ConnectorNo auth
  • WHAT: Offline email checks: RFC-style syntax + normalization, common domain typo "did you mean" (gmial.com -> gmail.com), disposable/temporary domain (bundled CC0 list, ~thousands of domains), role account (info@, sales@), free webmail provider. WHEN: Fast pre-filtering of signups or lead lists, before paying for email_validate_deliverability. WHEN NOT: Does NOT check DNS/MX, so it cannot tell whether the domain receives mail; use email_validate_deliverability (paid) for MX/SPF/DMARC. COST: Free; no token. RETURNS: Paged "email_check" rows; verdict is invalid | risky | unknown, never valid (dns_checked is always false). BEHAVIOR: Runs on this Fairquery-hosted Worker (Cloudflare), not on the caller's machine; inputs leave the client. This Worker's code is designed not to store inputs, results, or an Apify token. No further network call (no DNS/SMTP); addresses are not forwarded. Synchronous and CPU-bound, no rate limits: 10,000 addresses (the per-call maximum) return in well under a second. PARAMETERS: emails: each element is parsed on its own (one address per element; a comma-separated list in one element is INVALID_SYNTAX, not split). Before checking, "Name <addr>" is reduced to addr, a leading "mailto:" is dropped, the domain is lowercased (local part keeps its case), a trailing dot is removed and IDN domains are converted to punycode; the normalized value is returned as email, the original as input. Duplicates are not merged: every element yields one row, in input order. Role detection ignores +tags (sales+eu@ counts as sales@) and disposable matching also covers subdomains of listed domains. limit/offset page those rows; meta.summary always counts verdicts over ALL rows, not just the current page. EXAMPLE: {"emails":["someone@gmial.com"]} -> verdict "risky", reasons ["POSSIBLE_TYPO","DNS_NOT_CHECKED"], did_you_mean "someone@gmail.com".
    ConnectorNo auth
  • Unlock 10 bonus calls on this trial key, one time only, in exchange for the user's email address. Call this when the trial limit is reached and the USER has chosen the free-bonus option and given you their email in this conversation. NEVER guess, invent, or reuse an email the user did not explicitly provide for this. The key on this connection is upgraded in place, nothing to reconfigure. Free and unmetered.
    ConnectorNo auth
  • Get a new API key for an existing Disco account. Sends a 6-digit verification code to the email address. Call discovery_login_verify with the code to receive a new API key. Use this when you need an API key for an account that already exists (e.g. the key was lost or this is a new agent session). Returns 404 if no account exists with this email — use discovery_signup instead. Args: email: Email address of the existing account.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    A
    quality
    D
    maintenance
    An MCP server that provides information about Utkarsh, including bio, skills, work experience, and portfolio projects, accessible via local stdio or remote HTTP with OAuth.
    6
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI agents to provision their own email inbox on cooperemail.com, then send, receive, search, and thread real mail, get signed webhooks on delivery, and loop in a human owner who can reply to unblock decisions.
    MIT

Matching MCP Connectors

  • About Bureau, the self-hosted office for AI agents: overview, FAQ search, roadmap, install.

  • Verify the email instantly: Identify the spam email while authenticating your users.

  • Register a free hpsilab account for yourself, with no human involvement, and receive an API key immediately. Call this when the user has no API key yet and asks to sign up from here, or when a refusal's `next_actions` names register_account and the user agrees. This is the only tool that works without an API key. You do not need a password, a wallet, or a web browser. The account is bound to you server-side, so calls you make after this are metered as your account even though you cannot change your own Authorization header. The account is created unverified, with only a capped evaluation allowance and no trial Credits, until the email address is confirmed; confirming it grants the one-time 100-Credit Registered Trial (14 days). Ask the human you are working with to click the link in the email that will arrive. Calling again from the same caller returns the same account with a fresh key; an address that belongs to another account is refused. A valid user email address is required. Do not call this tool with an empty or fabricated email address. If the user's email is unavailable, ask the user to provide it before calling register_account. Args: email: The real user email address that will receive verification.
    ConnectorNo auth
  • Register a free hpsilab account for yourself, with no human involvement, and receive an API key immediately. Call this when the user has no API key yet and asks to sign up from here, or when a refusal's `next_actions` names register_account and the user agrees. This is the only tool that works without an API key. You do not need a password, a wallet, or a web browser. The account is bound to you server-side, so calls you make after this are metered as your account even though you cannot change your own Authorization header. The account is created unverified, with only a capped evaluation allowance and no trial Credits, until the email address is confirmed; confirming it grants the one-time 100-Credit Registered Trial (14 days). Ask the human you are working with to click the link in the email that will arrive. Calling again from the same caller returns the same account with a fresh key; an address that belongs to another account is refused. A valid user email address is required. Do not call this tool with an empty or fabricated email address. If the user's email is unavailable, ask the user to provide it before calling register_account. Args: email: The real user email address that will receive verification.
    ConnectorNo auth
  • Your OWN payment history with a recipient address: how many times, how recently, and whether this amount is typical. Call it before paying an address you have not confirmed. THIS IS NOT A REPUTATION SCORE and says nothing about whether the address is honest. A familiar address is NOT a safe address — keys get compromised. Never tell a user an address is "trusted" or "safe" on the basis of this. A `first-time-recipient` result is NOT a warning about the recipient — every legitimate relationship has a first payment. It is the moment to confirm the address through a second channel, because address substitution can only be caught before you send. Read `coverage`: float-lane payouts are NOT included, so "first time" can be wrong.
    ConnectorNo auth
  • Email the free FineRx discount card to an address the person gave you. Use ONLY after the person has given an email address AND confirmed they want the card sent there — ask for both first, then set ``consent`` to true. The message contains the card and nothing else; FineRx does not store the address. Returns ``sent`` true with the masked address, or ``sent`` false with the reason. On an error, say what happened and offer the printable card or the link instead. Do not retry a refusal or read the full address back.
    Connector
    Destructive
    No auth
  • Work out where a payment must go, before anybody signs or sends anything. `seller` and `nominal_buyer` may each be a wallet address OR AN EMAIL ADDRESS — an email is converted to the wallet that person owns, so you never need to know a wallet to use this. The parties are checked against the sanctions lists before an address is given. If any of them is listed the answer is `error: sanctioned_party` with no address, and the payment cannot be made through this service. The same answer comes back for terms whose payment contract was already refused on sanctions grounds when its money arrived: its address is not handed out again. If the check cannot be done right now the answer is `error: service_unavailable` with `retryable: true` and no address; try again shortly. Returns the payment address these terms produce, and TWO ways to fund it. Both end at the same address holding the same money; they differ only in who sends the transaction. **Transfer it yourself.** Send the tokens to the address from any wallet — a browser wallet, a hardware wallet, an exchange withdrawal. Nothing to sign for us, and no `payer` needed, because the payment contract never asks who paid: it reads its own balance. Then call `settle_escrow_payment` with no signature and we create the payment contract around what is there. **Or let us relay it.** Pass `payer` and this returns an EIP-3009 authorization for them to sign. We broadcast it and pay the gas, so **the payer needs no gas at all**. This is the only one an agent can complete unattended, and the only one that needs a key anywhere. Either way the address is the same, because it is a pure function of the terms. That is also what makes the relayed form safe: the payer signs `to` as part of the authorization, committing to every term at once — alter any of them afterwards and the address moves and the signature stops matching. `amount` is in the TOKEN's base units (1 USDC = 1000000), because that exact figure is one of the terms the address derives from. `expiry_timestamp` is an absolute Unix time — when the dispute window closes. `0` settles instantly with no recourse. There is no default: "instant, deliberately" and "nobody said" are different, and a caller must not discover afterwards which one they got. `nominal_buyer` is who may dispute and receives a refund. For an agentic payment this should be the PERSON, not the agent — they are the one who will later read a report and decide whether to object. **`seller` and `nominal_buyer` may each be a wallet address OR an email address.** An email resolves to the wallet Privy holds for that person — made for them if they have never logged in — and the same email always resolves to the same wallet, so the address derived here is the one `settle_escrow_payment` derives too. The resolved wallets come back under `parties`. A seller given by email is paid into that wallet; they sign in with the email to reach it. `external_id` keeps two otherwise-identical payments apart, and is one of the terms the address derives from. **Leave it out and a unique one is generated.** That is the right default: two payments matching in seller, amount, maturity and buyer would otherwise derive to the SAME address, and funding the second sends money into the first payment contract — recoverable only after that one is claimed, and only to ITS buyer. ⚠️ PASS BACK THE `external_id` THIS RETURNS, not the one you sent. A generated one is only knowable from the result, and settle derives the address again from whatever it is given: a different id is a different address, and the money is at this one. Supply your own for the opposite behaviour — a checkout hash gives "one checkout, one payment contract", so re-presenting the same purchase returns the same address rather than a second. `description` is what the payment is FOR, in the buyer's own words — ask them for it rather than defaulting. It is what they will be looking at in the dashboard weeks later deciding whether to dispute, and "Protected payment" tells them nothing about which one this was. It does not affect the address, so it can be set freely here. `brand` is the white-label partner the payment is being made under, if any (the `?b=` id, e.g. `escrow-me`). It is recorded on the contract for attribution only: it does not affect the address, and a malformed one is ignored rather than refused. `product_name` is what is being bought, shown on both parties' dashboards. Display only, like `brand`. A seller or nominal buyer given by email is recorded with that email as well, so the payment contract shows to them the way a request made on the site does. ⚠️ 1 to 160 characters. Longer is refused HERE rather than at the chain, where the check happens after the money has already moved. `arbiter` is who decides a dispute. Leave it out for the default arbiter, which is almost always right. It is one of the terms the address derives from, so pass the same value to `settle_escrow_payment`.
    ConnectorNo auth
  • Email a purchase order to the vendor as a PDF from QuickBooks Online. The email parameter is required: QuickBooks answers 'Email Address is required to send email' even when the purchase order carries a POEmail. QuickBooks sends the email asynchronously a few seconds after the confirmed call. The record must still exist when delivery occurs; deletion or voiding can prevent delivery. Cannot be unsent. Call first without confirm: nothing is sent, and the answer says what would go out and to which address, as QuickBooks holds them. Show the user that, and only once they agree call again with confirm: true.
    Connector
    Destructive
    OAuth
  • 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
  • Adds a client contact (an email address, plus an optional name) that shareable reports can then be granted to with manage_report_access. Adding a client does NOT email them and does not give them access to anything on its own; it only creates the contact. A new contact's first grant also waits for the account owner to confirm it by email. Emails are stored lowercased and must be unique per account; adding an address that already exists returns the existing client rather than failing.
    ConnectorOAuth
  • Email a verification code to the email address on the user's Porkbun account, to clear VERIFICATION_REQUIRED (purchases and top-ups need a verified email and phone). It is the usual verification email: a link plus a code. Then ask the user for the code in that email (or read it, if you have access to that inbox) and call `confirm_email_verification`; the user clicking the link works too. The address on the account is used (or a new address waiting for verification); it cannot be chosen or changed here, and the code is never returned to you: it only proves the address because it arrives there. A second request within 10 minutes returns `codeAlreadySent`; the earlier code stays valid for 3 days. Guide: https://porkbun.com/llms/guides/verify-the-account
    ConnectorOAuth
  • Verify if a single email address is real and deliverable. Returns {valid, status, confidence_score}. Use when you already know the address (e.g. from a contact page, LinkedIn, or a prior discover_email run) and want to confirm it before sending. To go from a person's name → verified email instead, use discover_email: that already runs validation internally on every candidate, so don't call validate_email on its output. Needs a StartupHub.ai API key with credit (pay as you go).
    ConnectorNo auth
  • Update an application's payload and/or contact email while it's still in `draft`. **When:** founder caught something wrong after `create_application` but before `verify_email`. Also when changing the email address. **Before you call:** - Full-replace on payload: send the WHOLE `PitchApplication` object, not a patch. Read current values from `get_status` if you don't have them. - Email change resets verification: `emailVerified` goes back to false and a fresh code is sent to the NEW address. Let the founder know. **Returns:** the fresh `StatusView` — markdown by default, JSON if `responseFormat: "json"`. Same shape as `get_status`. **On error:** - `notEditable` — status is past `draft`. Nothing to update; state is locked. Read `get_status` to understand where you are. - Validation failed — payload doesn't satisfy the schema. Fix per the error message and retry.
    ConnectorNo auth
  • List the workspace's teammate email addresses, primary and aliases, newest first, each with its `id`, `address`, `primary` flag and owning `teammate_id`. Use it to get the email `id` that add_signature_recipients, remove_signature_recipients, update_email, delete_email, install_signature_for_email and send_test_email take. Use list_teammates instead when you also need smart-field values: it embeds each teammate's emails too. There is no address search: filter by `teammate_id`, or page through and match `address`. Deleted emails and teammates are excluded. Read-only; needs the emails:read scope. Returns one page (default 50, max 100); set `auto_paginate` to fetch up to `max_pages`, and `truncated: true` means more remain.
    ConnectorOAuth
  • Start watching a property in a covered county for `email`. `address`: street address with house number and city (e.g. '1702 Ellsworth St, Philadelphia'); `state`: two-letter code; `county`: county or borough ('Philadelphia', 'Cook', 'Brooklyn'). Returns the watch and, for a new email, `access_key` + `dashboard_url`: the ONLY key to that watch list (no password exists), shown once; give it to the user and tell them to keep it private. The first check runs within minutes (status 'pending' until the parcel is resolved). An email that already has a watch list gets an error: its owner adds properties from their own list. Property Watch is $9.99 a month per property (cancel any time): a new watch answers with a checkout link and starts once it is paid.
    ConnectorNo auth
  • Enable Email to Postcard intake after the human requests it, with confirmed:true. Requires a production workspace key and OAuth mcp:read/mcp:write permissions. Creates a dedicated postcard- inbox while preserving the separate letter address. Returns postcardAddressState; inbox is empty until the dedicated mailbox is ready. Retry this tool to check pending setup; never invent an address or send to a pending postcardAddress. Never returns mailbox credentials. Every email delivered to the postcard address enters its separate queue, including BCC delivery; no subject prefix is required. Does not change letter rules, enable postcard autosend, check mail, buy postage or send email.
    Connector
    Destructive
    No auth
  • Creates or opens a disposable, receive-only email inbox and reads what arrived — to sign up somewhere and get the verification code or confirmation link without using the user's real address. WHEN TO USE: a site or service asks for an email to send a code, a magic link or a confirmation, and the user does not want to give their own; or you need to read what was sent to an inbox created earlier. HOW IT WORKS: - inbox: a name ("fulano") or a full address on the tool's domain. Empty: a random, hard-to-guess address is created. Any name works: there is no sign-up. - waitSeconds (0–50, default 0): wait for a NEW message to arrive before answering. Typical flow: call once with no inbox to get an address, give it to the site, then call again with that inbox and waitSeconds 30–50 until the email shows up. - message: the id of one message, to read it in full (text, links, attachments). - The inbox is PUBLIC: anyone who knows the address can read it. Never use it for banking, government or any account the user wants to keep. - Receive only (it cannot send). Messages up to 10 MB; everything is deleted after 8 days. Some sites refuse disposable domains — then the user needs a real address. RETURNS: address; messages (newest first) with id, from, subject, preview, receivedAt and code — the verification code when one is found; with message, also text, links (url and text, confirmation links included) and attachments. link: this inbox on the web page, to show the user. timedOut is true when waitSeconds ended with no new message.
    ConnectorNo auth