"How to send OS notifications" matching MCP tools:

• notifications

  DC Member API

  GET /notifications — Get your notification preferences Returns your push + email preferences per notification category. Defaults are applied for any preference you have never explicitly set. Email is `null` for `reaction` / `myReaction` because email is not supported for those categories. For the Friday locator email digest, see `GET /locator/settings` — that's a separate concern (outbound digest, not per-event push/email).

  Connector

• linux_os

  ZEN SecDB

  List supported Linux operating systems and their corresponding versions for use with the `linux_audit` tool. ## What this tool does Returns an array of supported OS/version pairs, each in the form: {"os":"name", "versions":["version or codename"]} This allows the LLM and the user to know exactly which inputs are valid for the `linux_audit` tool. ## When to use this tool Use this tool when: - the user does not know which OS names or versions are supported - the user provides unclear or ambiguous OS information - you need to validate `os`/`version` before performing a Linux audit This tool should typically be called **before `linux_audit`** whenever parameters are uncertain. ## Inputs This tool does not require any input. ## Outputs Returns an array of objects: - **os**: supported Linux distribution identifier - **versions**: corresponding list of supported release or codename Example: [ {"os": "ubuntu", "versions": ["noble","focal"]}, {"os": "debian", "versions": ["bookworm","sid"]}, {"os": "redhat", "version": ["redhat-9.0"]} ] ## LLM usage guidelines - Use this tool to validate or suggest correct OS/version combinations before calling `linux_audit`. - If the user provides invalid or misspelled OS names, retrieve the official list here and ask them to select one. - Do not guess operating system identifiers-always rely on this tool to confirm correctness.

  Connector

• create_job_offer

  Human Pages

  Send a job offer to a specific human. IMPORTANT: Always confirm the price, task details, and payment method with the user before calling this tool — never create offers autonomously. The human gets notified via email/Telegram and can accept or reject. Requires agent_key from register_agent. Rate limit: PRO = 15/day. Prices in USD, payment method flexible (crypto or fiat, agreed after acceptance). After creating: poll get_job_status or use callback_url for webhook notifications. On acceptance, pay via mark_job_paid. Full workflow: search_humans → get_human_profile → create_job_offer → mark_job_paid → approve_completion → leave_review.

  Connector

• create_alert_rule

  BorealHost

  Create an alert rule to monitor CPU, memory, or disk usage. When the metric crosses the threshold, a notification is sent via email and/or webhook. Max 10 rules per site. Requires: API key with write scope. Args: slug: Site identifier metric: "cpu", "memory", or "disk" (percentage-based) threshold: Threshold value 0-100 (e.g. 90 for 90%) operator: "gt" (greater than) or "lt" (less than). Default: "gt" severity: "warning" or "critical". Default: "warning" cooldown_minutes: Min minutes between repeated alerts. Default: 30 notify_email: Send email notification. Default: true notify_webhook: Optional webhook URL for POST notifications Returns: {"id": "uuid", "metric": "disk", "threshold": 90, ...}

  Connector

• wait_for_update

  cnvs.app

  Long-poll: blocks until the next edit lands on this board, then returns. WHEN TO CALL THIS: if your MCP client does NOT surface `notifications/resources/updated` events from `resources/subscribe` back to the model (most chat clients do not — they receive the SSE event but don't inject it into your context), this tool is how you 'wait for the human' inside a single turn. Typical flow: you draw / write what you were asked to, then instead of ending your turn you call `wait_for_update(board_id)`. When the human adds, moves, or erases something, the call returns and you refresh with `get_preview` / `get_board` and continue the collaboration. Great for turn-based interactions (games like tic-tac-toe, brainstorming where you respond to each sticky the user drops, sketch-and-feedback loops, etc.). If your client DOES deliver resource notifications natively, prefer `resources/subscribe` — it's cheaper and has no timeout ceiling. BEHAVIOUR: resolves ~3 s after the edit burst settles (same debounce as the push notifications — this is intentional so drags and long strokes collapse into one wake-up). Returns `{ updated: true, timedOut: false }` on a real edit, or `{ updated: false, timedOut: true }` if nothing happened within `timeout_ms`. On timeout, just call it again to keep waiting; chaining calls is cheap. `timeout_ms` is clamped to [1000, 55000]; default 25000 (leaves headroom under typical 60 s proxy timeouts).

  Connector

• senado_servidores

  Dados Abertos Senado BR MCP

  Lista servidores do Senado por `situacao` (ativos, efetivos, comissionados ou inativos), com filtros opcionais por `nome`, `lotacao` e `cargo`. Retorna `{ situacao, count, total, servidores[] }`, cada item com `nome`, `vinculo`, `situacao`, `cargo`, `funcao`, `lotacao`, `anoAdmissao` etc. Aplica `limite` (padrão 50, máx 500) e inclui `aviso` quando há truncamento — refine os filtros. Também conta e lista TODOS os servidores de TODA a estrutura subordinada a uma diretoria/secretaria (não só a lotação direta), cruzando a lotação de cada servidor com o organograma até o nível de serviço: informe a unidade (sigla ou nome, ex.: 'DGER') em `subordinadasA` — use isso para 'quantas pessoas estão sob a Diretoria-Geral', pois filtrar `lotacao` pela sigla-mãe retorna 0 (os servidores ficam em serviços/núcleos subordinados). Nesse modo o retorno traz a unidade resolvida, o total (um piso), os servidores, as unidades não reconhecidas no organograma (`naoClassificados`, com nota explicativa) e os afastados/em trânsito (`afastadosOuEmTransito`); ao responder, verbalize esses conceitos em português corrente — não cite nomes de parâmetros ou campos. Para o organograma em si use `senado_estrutura_organizacional`; para remuneração use `senado_remuneracoes_servidores`.

  Connector

• aicom_agora_message

  aicomglobal

  The Agora's one paid action: pay tiny x402 postage to DELIVER a PRIVATE direct message into another agent's inbox. Everything conversational is FREE (browse, post, reply in public threads, read your inbox); you pay only for private, targeted reach (the postage is what makes a private message get read, not spam-filtered). If a public answer works, use the free aicom_agora_reply instead. This returns the QUOTE only (price, asset, network, how to send); to actually send, GET /agora/message for a nonce then POST /agora/message with {nonce, signal_id|to, body}.

  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

• 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

• 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

• send

  Apuchat

  Send a message to another agent on the channel you joined, or to 'all' to broadcast. Requires a prior join() in this session. The 'to' field accepts: a callsign ('front'), an index ('#1' or '1') from roster(), or 'all'. If omitted, defaults to 'all' (broadcast — walkie-talkie default). Optional `priority` tags urgency (min|low|default|high|urgent). Optional `suggested_replies` hints up to 4 canned replies that human-in-the-loop UIs (like the /remote phone view) render as tappable chips — agent receivers can read them too and pick one. Optional `attachments` carries up to 4 small inline files (≤512KB base64 total) — designed for sporadic screenshots / PDFs; bigger files should be hosted externally and pasted as a URL. Optional `kind`: set 'status' to send an ephemeral 'working on it' signal instead of a normal message (see the `kind` field).

  Connector

• list_plans

  eqvps

  List all available VPS plans (catalog) with pricing, specs and the OS images each plan can boot. No authentication needed. Use this first to pick a `product` slug and an `os_id` for `order_vps`.

  Connector

• linux_audit

  ZEN SecDB

  Perform a Linux package vulnerability audit using SecDB. ## What this tool does Analyzes the installed packages of a Linux system-identified by OS and OS version-and returns vulnerability information plus a Markdown summary. The audit results are based exclusively on the package list provided by the user. ## When to use this tool Use this tool when the user wants to determine: - whether installed packages contain known vulnerabilities - whether a host, VM, container, or base image is affected by security advisories - which packages require patching or upgrading If the user does not know the valid values for `os` or `version`, first call the `linux_os` tool to retrieve the exact supported combinations. ## Inputs - **os**: Linux distribution identifier supported by SecDB (use `linux_os` to obtain allowed values). - **version**: OS version or codename corresponding to the selected distribution. - **packages**: list of installed packages, **one per line**, generated using the appropriate system command: ### For RPM-based distributions (RHEL, CentOS, Rocky, Alma, SUSE) rpm -qa --qf '%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}\n' ### For DEB-based distributions (Ubuntu, Debian) dpkg-query -W -f='${Package} ${Version} ${Architecture}\n' ### For Alpine Linux apk list -I The raw output of these commands can be passed directly as the `packages` input (one package per line). ... python3 3.12.3-0ubuntu2.1 amd64 systemd 255.4-1ubuntu8.10 amd64 tmux 3.4-1ubuntu0.1 amd64 ... ## Outputs - **report**: structured objects describing the advisories affecting the audited packages. - **summary**: Markdown summary including total vulnerabilities, severity breakdown, and key findings. ## LLM usage guidelines - Never guess whether a package is vulnerable-always call this tool for Linux audits. - If `os` or `version` is unclear or missing, call `linux_os` and ask the user to choose a valid combination. - Normalize the package list to “one entry per line” if the user provides unstructured output. - The `summary` is already Markdown and can be shown directly. - Use `report` when deeper technical analysis is required.

  Connector

• how-to

  Fast.io

  Built-in product help — ask a natural-language "how do I…" question about Fastio and get a grounded, product-aware answer (or a short clarifying question) back in one call. EXPLAIN-ONLY / ADVISORY: it returns GUIDANCE TEXT and performs NO platform action (it will not create shares, move files, or change anything) — read the guidance, then act with the other tools. Answers are grounded in Fastio's own how-to knowledge AND phrased in terms of these MCP tools — they name the concrete `<tool> action="…"` calls to make — so prefer this over guessing endpoints or burning exploratory calls. For Q&A over YOUR uploaded files (RAG) use the `ai` tool instead — `how-to` answers questions about Fastio ITSELF. FREE and requires only an authenticated user (no org, no plan gate, no billing). Call action='describe' for the full action/param reference.

  Connector

• create_webhook

  domani

  Register a new webhook endpoint to receive event notifications. The URL must use HTTPS. Choose which events to subscribe to (e.g. domain.purchased, transfer.completed). The webhook secret is returned only once - save it to verify incoming payloads with HMAC-SHA256.

  Connector

• store-item-tool

  clippy

  Post a piece of text to a Clippy room so it appears on every device and agent watching that room. The room is created automatically if it does not exist yet. Subscribed devices receive a push notification. This is how you "send" something to a user or leave a note for another agent. Returns the stored item.

  Connector

• ecwid_update_order

  ecwid

  UPDATES an order — its payment status, fulfillment status, and/or tracking number. This MODIFIES live store data and may trigger customer notifications. Ecwid REST: PUT /orders/{orderNumber}. Provide only the fields you want to change. Returns {updateCount}.

  Connector

• search_tools

  Relaystation

  Search the full Relaystation tool catalog by keyword and get back the best matches. Use this first to find a tool, then `describe_tool` for its schema and `call_tool` to run it (or call a named hot tool directly). `query` is free text (e.g. "merge pdf", "csv to json", "send telegram"). `detail` controls how much is returned per match: "name" | "summary" (default) | "full" (with inputSchema). `limit` defaults to 5. FREE. Example: search_tools {query:"merge pdf", limit:5}

  Connector

• colony_send_group_message

  The Colony

  Send a message to a group conversation. The caller must already be a member — use ``colony_list_group_conversations`` to find the ``conversation_id``. The send reuses the shared SSE-fanout pipeline, so every other member's open client gets the new message live. Requires authentication.

  Connector

• send_draft

  gmail

  Send a previously created draft email. Use this after draft_email or draft_reply when ready to send. The draft will be moved from Drafts to Sent folder automatically. This action cannot be undone.

  Connector