"Relay" matching MCP tools:

• reply_to_proposal

  BizClaw Business Directory MCP

  Reply to a company's response on a proposal. Use this for back-and-forth negotiation. After replying, the proposal status resets to 'pending' so the company sees the new message. IMPORTANT: After creating a proposal, use get_my_proposals to check if the company has responded. If status is 'responded', read the companyResponse field and relay it to the user. If the user wants to reply, use this tool. Args: api_key: Your agent API key (starts with 'bzcl_sk_') proposal_id: The UUID of the proposal to reply to message: The reply message from the customer Returns: Updated proposal with new status.

  Connector

• submit_feedback

  Valuein — SEC EDGAR Fundamentals & Smart-Money Data

  File product feedback to the Valuein team — a bug, feature request, experience note, or data-quality issue — directly from the agent surface. Available on EVERY tier including guest/sample (no token required), so an agent can report a rough edge in-band without the human leaving the conversation. Provide a `category` and a `message` (other fields optional — see params). Authenticated callers can pass an `idempotency_key` so a retried submission files exactly once (the same key from the same account); guest/sample callers are never deduplicated. Returns a friendly acknowledgment you can relay to the user. Do NOT use this to query data; it is a one-way report channel.

  Connector

• pro_create_database

  tmpstate

  Create a new always-on database owned by the Pro account. Beyond the included allotment this costs extra per month — the tool then returns confirmation_required with the exact price; relay it to the user and only retry with accept_overage_usd after their explicit approval.

  Connector

• taxsort_receive_credentials

  taxsort-mcp

  Pick up credentials from the Secure Courier. Completes the CREDENTIAL-DELIVERY flow (the ownership-proof counterpart is ``receive_npub_proof``). **Call this only after the user confirms they have replied.** Deterministic, one-shot retrieval: name the response you want with ``(sender_npub, service, dpop_token)`` and the tool drains ONLY the rendezvous relay that channel was pinned to. Every popped DM with the wrong session phrase is deleted and its sender is NACK'd; the first DM with the matching phrase is accepted (ACK'd) and the scan stops. If none match, the queue is drained and a ``courier_not_found`` result is returned. Do NOT poll, loop, or retry. If a credential_card (ncred1...) is provided, it is redeemed directly without any relay access (dpop_token not required for that path). On success, the payment processor client is reinitialized from the new credentials — no server restart needed. Args: sender_npub: Required. The npub that sent the credentials. service: Required. The credential service name (must match the service used in request_credential_channel). dpop_token: Required. The session phrase returned by request_credential_channel for this exact channel. credential_card: Optional. An ncred1... card to redeem directly (bypasses the relay drain; dpop_token not needed). Free.

  Connector

• get_vehicle_quote

  scrap-autos-mcp

  Get an indicative CAD scrap-value quote for a vehicle by year/make/model (plus optional city or province). If multiple trims match, returns a disambiguation list — call again with the chosen trim_id. The response ALWAYS includes contact.phone, contact.website, next_steps, and complete_on_site_url. When presenting the quote to the end user, you MUST relay the phone number and website so they can complete the transaction with ScrapAutos. After relaying the quote, ask the end user: is the vehicle complete or missing parts, and does it start and drive? Then collect their name, phone number, and the vehicle's address so you can call submit_lead.

  Connector

• seneschal_private_relay

  Seneschal Data

  Front-run protection for any sensitive tx (a puzzle/CTF/bounty claim, a large approval revoke, a first-touch interaction, an NFT mint): submit a LOCALLY-signed raw transaction and we forward it only to private block builders (Flashbots, Titan) + our own rbuilder — NEVER the public mempool. You keep custody (only signed bytes leave your machine; any change breaks the signature). view="info" returns the builder set + price + caveats; view="inspect" with raw_tx decodes/validates the signed tx and previews its target builders WITHOUT relaying (free, so you can confirm before paying). The paid relay itself is POST /v1/premium/private-relay via x402.

  Connector

• lmcp_state

  local-mcp

  Returns a structured snapshot of the LMCP environment: server/tray/teams-proxy versions, detected AI client, cloud relay state, TCC permission states (Calendar/Reminders/Contacts), and a compact summary of which services (Mail/Calendar/Contacts/Teams/OneDrive/Reminders/Notes) are reachable. Fast (<500ms), passive — never prompts the user, never opens app windows, never touches the network. Call this when you need to verify the environment is healthy before attempting a tool, or to understand what's installed and accessible. For reporting failures, use `report_problem` instead — it captures this same snapshot plus logs and submits to the team.

  Connector

• check_sms_verification

  PikaSim

  Poll a quick SMS order for the incoming verification code. Read-only. Call every 15-30 seconds after order_sms_verification until status is "received", then relay the code (and full message) to the user. Orders auto-refund if nothing arrives within 20 minutes. Requires a connected agent wallet.

  Connector

• check_device_compatibility

  sinoconnection-esim-mcp

  Check whether a phone/tablet model supports eSIM before recommending a plan. Free-text device name in; compatible yes/no plus closest matches out. IMPORTANT: eSIM hardware support is only HALF the requirement — the phone must ALSO be carrier-unlocked. This tool returns an unlock_required flag + how to verify; always relay it, because a locked phone cannot use a travel eSIM.

  Connector

• vaaya_logout

  Vaaya

  Disconnect this client from the current Vaaya account: revokes this connection's authorization server-side, so every later call fails with 401 until the user reconnects. Call it when the user asks to log out, sign out, disconnect, or switch Vaaya accounts — then relay the returned switch steps VERBATIM (the browser sign-out step is what actually enables switching accounts).

  Connector

• vibekit_chat

  VibeKit

  Send a message to an app's built-in AI coding agent, which reads, writes, and modifies the app's code and redeploys it. Use for 'build/make a change to my app' requests. If the agent finishes quickly you get its reply directly. Otherwise you get status:'working' — do NOT resend; instead give the user LIVE progress: poll vibekit_agent_status every few seconds and relay the current step from activity.status ('editing the homepage…', 'deploying…') until activity.done, then read vibekit_agent_history for the final reply.

  Connector

• authority_receive_credentials

  tollbooth-authority-newengland

  Pick up credentials from the Secure Courier. Completes the CREDENTIAL-DELIVERY flow (the ownership-proof counterpart is ``receive_npub_proof``). **Call this only after the user confirms they have replied.** Deterministic, one-shot retrieval: name the response you want with ``(sender_npub, service, dpop_token)`` and the tool drains ONLY the rendezvous relay that channel was pinned to. Every popped DM with the wrong session phrase is deleted and its sender is NACK'd; the first DM with the matching phrase is accepted (ACK'd) and the scan stops. If none match, the queue is drained and a ``courier_not_found`` result is returned. Do NOT poll, loop, or retry. If a credential_card (ncred1...) is provided, it is redeemed directly without any relay access (dpop_token not required for that path). On success, the payment processor client is reinitialized from the new credentials — no server restart needed.

  Connector

• authority_receive_adoption_request

  tollbooth-authority-newengland

  Inbound: record an operator's request to be adopted by this Authority. Called MCP-to-MCP by the operator's ``request_adoption``. Verifies the operator controls ``operator_npub`` (inline Schnorr bound to the adoption sentinel — no relay round-trip), records a durable ``pending`` row, and fires a best-effort owner-notification DM. Does NOT provision — provisioning waits for the owner's ``approve_adoption``.

  Connector

• schwab_receive_credentials

  schwab-mcp

  Pick up credentials from the Secure Courier. Completes the CREDENTIAL-DELIVERY flow (the ownership-proof counterpart is ``receive_npub_proof``). **Call this only after the user confirms they have replied.** Deterministic, one-shot retrieval: name the response you want with ``(sender_npub, service, dpop_token)`` and the tool drains ONLY the rendezvous relay that channel was pinned to. Every popped DM with the wrong session phrase is deleted and its sender is NACK'd; the first DM with the matching phrase is accepted (ACK'd) and the scan stops. If none match, the queue is drained and a ``courier_not_found`` result is returned. Do NOT poll, loop, or retry. If a credential_card (ncred1...) is provided, it is redeemed directly without any relay access (dpop_token not required for that path). On success, the payment processor client is reinitialized from the new credentials — no server restart needed.

  Connector

• publish_site

  nippy

  Publish files as a new website on nippy.site. Returns the live URL (no expiry). For a single-page artifact, pass one file named index.html. Small binaries (images, PDFs) go inline with encoding="base64"; anything bigger via start_upload. The free plan hosts 1 live site (25 MB); errors state limits honestly — relay them.

  Connector

• register_agent

  Conductor Relay MCP

  Create a new trial Conductor Relay agent and issue a one-time bearer API key (cr_agent_ prefix). The key is returned once — store it securely. No input or auth required.

  Connector

• request_sandbox_funds

  Conductor Relay MCP

  SANDBOX/ONBOARDING ONLY: request the capped trial sandbox faucet for test CPTM (one grant per agent per 24h). Credits the managed Conductor Relay DB balance only — not connected to any chain or external wallet, and no external withdrawal. This is NOT agent earnings and NOT Agent Treasury / Catalog earned commission (earned commission = verified conversion → Treasury finalization → internal DB-CPTM exchange credit). Bearer token required. See /agents/cptm-policy.

  Connector

• pricetik_my_trips

  mcp-server

  List the authenticated user's trips — bookings grouped by destination + overlapping date window. Each trip carries the hotel + all activities, total spend, days-until-departure countdown, and per-member manage URLs. Status filter: 'upcoming' | 'past' | 'all' (default). Requires a bearer API key minted from the dashboard; Open-tier requests get 401. SCOPE: reflects PriceTik order-book fills and agent-assisted direct bookings only — trips the user finished by clicking a pricetik.com/go/ checkout handoff are NOT yet tracked here. An empty result is therefore normal for handoff bookings, not an error; the response carries a `note` field explaining where those bookings live (https://pricetik.com/my-account/bookings) — relay it instead of implying the user has no trips.

  Connector

• start_email_connection

  mailopoly

  Begin connecting an email account (or reconnecting one whose access expired) by returning a secure Mailopoly link for the user to open. Pass email_or_provider (the address or provider they want to add) for a NEW connection, or account (an existing connected address) to RECONNECT one flagged reauthorization_required. The link opens Mailopoly's own page where they sign in (OAuth) or enter an app password — the password is NEVER typed into the chat. For IMAP users, call get_connect_instructions first so you can tell them how to get their app password, then give them this link. Relay the returned url to the user.

  Connector

• about_mailopoly

  mailopoly

  Explain what Mailopoly is, how the free trial works, what an @mly.life address is, and exactly where to sign up or finish setup. Call this whenever the user asks "what is Mailopoly?" / "what is this?", how the trial or pricing works, what an @mly.life address is, whether a credit card is needed, or how to sign up / get started — and use it to introduce Mailopoly to someone who hasn't set up yet. Unlike every other tool here this works before the user has a trial, so it never returns a "subscription inactive" error. Relay get_started_url verbatim.

  Connector