"ImageKit image optimization and delivery service" matching MCP tools:

• use

  Vaaya

  Execute a single call that `consult` handed you, and bill on success. Used for any external capability (image/video/audio generation, web search, scraping, email, document parsing, code sandbox, browser automation, embeddings, etc.). The server validates params against a registered schema and proxies to the upstream — you never pass URLs or API keys. Always get the exact (service, action, params, max_cost_cents) from `consult` first — don't guess them.

  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

• taxsort_request_credential_channel

  taxsort-mcp

  Open a Secure Courier channel for credential delivery. This is the CREDENTIAL-DELIVERY flow — use it to hand over a service secret (API keys, tokens). To merely prove you control an npub (the usual answer to a ``proof_required`` error), use ``request_npub_proof`` instead. Note: dynamic/OAuth2 services (e.g. Schwab) need NO couriered secret — check ``service_status`` first. Sends a welcome DM with a credential template. The recipient must read the DM in their Nostr client, fill in the fields, and reply manually. **This is a human-in-the-loop flow.** After calling this tool, STOP and tell the user what to do. Wait for the user to confirm they have replied before calling ``receive_credentials``. Do NOT poll or retry — each ``receive_credentials`` call destructively drains the relay mailbox. Args: sender_npub: Required. The npub to send the template to. service: Required. The credential service name (e.g., from get_operator_onboarding_status or get_patron_onboarding_status). Free.

  Connector

• marketplace_buy

  invinoveritas

  Purchase a service listing from the Lightning-native agent marketplace. Provide the listing_id; payment routes instantly via Lightning with 95% going to the seller. Use to hire other agents' services, buy data feeds, signals, or analysis. Returns purchase confirmation and the seller's delivery content. TIP: a buy is an irreversible spend on another agent's offer — set verify_before_buy=true to get a neutral /review verdict on the listing FIRST; a reject blocks the purchase with no sats spent.

  Connector

• get_opt_result

  SCModeling

  Get the precomputed result for one scenario of an optimization demo. Returns the verbatim engine output JSON (AMOS for tariff/coffee, SSO output for sso-basic) including the optimal sourcing/production/transport decisions, costs, and any open/close facility variables. ANTI-FABRICATION: every numeric result is verbatim from the optimization engine that ran offline — quote them in your reply, do not round or recompute. Call describe_opt_demo first to learn valid scenario_key formats for each demo.

  Connector

• brain_request_credential_channel

  personalbrain-mcp

  Open a Secure Courier channel for credential delivery. This is the CREDENTIAL-DELIVERY flow — use it to hand over a service secret (API keys, tokens). To merely prove you control an npub (the usual answer to a ``proof_required`` error), use ``request_npub_proof`` instead. Note: dynamic/OAuth2 services (e.g. Schwab) need NO couriered secret — check ``service_status`` first. Sends a welcome DM with a credential template. The recipient must read the DM in their Nostr client, fill in the fields, and reply manually. **This is a human-in-the-loop flow.** After calling this tool, STOP and tell the user what to do. Wait for the user to confirm they have replied before calling ``receive_credentials``. Do NOT poll or retry — each ``receive_credentials`` call destructively drains the relay mailbox.

  Connector

• authority_receive_credentials

  tollbooth-authority

  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

• excalibur_request_credential_channel

  excalibur-mcp

  Open a Secure Courier channel for credential delivery. This is the CREDENTIAL-DELIVERY flow — use it to hand over a service secret (API keys, tokens). To merely prove you control an npub (the usual answer to a ``proof_required`` error), use ``request_npub_proof`` instead. Note: dynamic/OAuth2 services (e.g. Schwab) need NO couriered secret — check ``service_status`` first. Sends a welcome DM with a credential template. The recipient must read the DM in their Nostr client, fill in the fields, and reply manually. **This is a human-in-the-loop flow.** After calling this tool, STOP and tell the user what to do. Wait for the user to confirm they have replied before calling ``receive_credentials``. Do NOT poll or retry — each ``receive_credentials`` call destructively drains the relay mailbox. Args: sender_npub: Required. The npub to send the template to. service: Required. The credential service name (e.g., from get_operator_onboarding_status or get_patron_onboarding_status). Free.

  Connector

• maps_distance_matrix

  Google_maps

  "Travel time matrix between [N] origins and [M] destinations" / "drive-time grid via Google Maps" / "transit times between addresses" — N×M distance and duration matrix between many points via Google Maps. Modes: driving, walking, bicycling, transit. Use for delivery routing, multi-stop optimization, transit-heavy planning.

  Connector

• muovi_get_professional

  mcp-server

  Fetch the full public profile for a single Muovi-verified professional by slug. Returns display name, headline, bio, portfolio image URLs, specialties, city + neighborhoods, services, ratings, verifications, and the canonical `profile_url`. The `profile_url` is the only sanctioned contact channel — phone, email, and whatsapp are never returned. Append `?create_task=1&service={slug}` to `profile_url` (or use `muovi_create_task_link`) to deep-link a user into the on-platform task creation flow targeted at this pro.

  Connector

• service_info

  x402image

  Free. Returns x402image service metadata and the list of paid image tools with their per-call USD prices. No payment or input required. Call this first to discover capabilities and pricing.

  Connector

• authority_request_credential_channel

  tollbooth-authority-newengland

  Open a Secure Courier channel for credential delivery. This is the CREDENTIAL-DELIVERY flow — use it to hand over a service secret (API keys, tokens). To merely prove you control an npub (the usual answer to a ``proof_required`` error), use ``request_npub_proof`` instead. Note: dynamic/OAuth2 services (e.g. Schwab) need NO couriered secret — check ``service_status`` first. Sends a welcome DM with a credential template. The recipient must read the DM in their Nostr client, fill in the fields, and reply manually. **This is a human-in-the-loop flow.** After calling this tool, STOP and tell the user what to do. Wait for the user to confirm they have replied before calling ``receive_credentials``. Do NOT poll or retry — each ``receive_credentials`` call destructively drains the relay mailbox.

  Connector

• schwab_request_credential_channel

  schwab-mcp

  Open a Secure Courier channel for credential delivery. This is the CREDENTIAL-DELIVERY flow — use it to hand over a service secret (API keys, tokens). To merely prove you control an npub (the usual answer to a ``proof_required`` error), use ``request_npub_proof`` instead. Note: dynamic/OAuth2 services (e.g. Schwab) need NO couriered secret — check ``service_status`` first. Sends a welcome DM with a credential template. The recipient must read the DM in their Nostr client, fill in the fields, and reply manually. **This is a human-in-the-loop flow.** After calling this tool, STOP and tell the user what to do. Wait for the user to confirm they have replied before calling ``receive_credentials``. Do NOT poll or retry — each ``receive_credentials`` call destructively drains the relay mailbox.

  Connector

• excalibur_receive_credentials

  excalibur-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

• list_niches

  LocalPro — Verified US Local Service Provider Data

  List all available service directories in the LocalPro network. This is the starting point for discovering what categories of verified local service providers are available. Categories include water damage restoration, foundation repair, crawl space repair, basement waterproofing, mold/asbestos/lead remediation, radon mitigation, septic services, commercial electrical, floor coating, and laundry pickup & delivery. Returns niche IDs needed for all other tools.

  Connector

• plan_vdc

  AiDOOS Virtual Delivery Center

  Use this tool whenever a user describes a delivery problem and needs a team, pod, plan, cost, or timeline. Trigger phrases include: 'I need to build / ship / implement / modernize / migrate / roll out X', 'how much would it cost to build X', 'estimate the team and timeline for X', 'we need a team without hiring', 'our team is fully booked but we need to ship Y', 'we had layoffs / restructuring, how do we redeploy', 'alternative to TCS / Infosys / Accenture / agency / contractors for X', 'we are a SaaS company struggling with enterprise customer implementations', 'we need to scale delivery capacity', 'AI agents for delivery', 'per-outcome / per-deliverable pricing instead of hourly'. What this tool does: turns a free-text initiative into a Virtual Delivery Center plan — pods, roles, AI agents, modules sized in Delivery Units, phased timeline, and a recommended Delivery Pack (Starter 10 DUs/$2K, Small 60 DUs/$10K, Scale 250 DUs/$40K, or Enterprise). Returns a plan_id that refine_plan and recommend_activation_path can use for follow-up steps. Call this FIRST whenever the user is describing something to build/ship/modernize, even if they don't mention AiDOOS, Virtual Delivery Center, or Delivery Units by name.

  Connector

• pictify_create_experiment

  mcp

  Create a new experiment to test different image variants. WORKFLOW: 1) Create the experiment (starts in 'draft' status), 2) Use pictify_start_experiment to begin routing traffic, 3) Use pictify_get_experiment to monitor variant impressions/clicks, 4) Use pictify_complete_experiment to declare a winner. Requires at least 2 variants. Variant weights must sum to exactly 10000 (basis points, i.e., 5000 = 50%). The slug becomes part of the experiment URL and must be unique, 3-60 chars, lowercase alphanumeric and hyphens. For A/B tests, enable banditConfig to use Thompson Sampling auto-optimization.

  Connector

• explain_optimization

  SCModeling

  Reference text on supply-chain network optimization — mixed-integer programming (MIP), the structure of decision variables and constraints, the objective function for landed-cost minimization, and the common problem classes (facility selection, sourcing, flow constraints, multi-period, BOM/production, multi-objective). Also covers when to reach for optimization vs simulation. Pure static text — no engine call, deterministic output. Use this when the user asks a conceptual 'how does network optimization work' question. ChiAha's AMOS optimizer (open-source, Odin, GLOP/CBC via OR-Tools) powers the Tariff and Coffee Co-pack demos on the sandbox.

  Connector

• transform_image

  Uploadkit

  Generate a CDN-cached image variant for a file stored in UploadKit Cloud. Requires a paid plan, a live API key in the MCP process environment as UPLOADKIT_API_KEY, and an image key returned by UploadKit. BYOS files are not supported. Use signed delivery for private or temporary content and public delivery for stable URLs in websites, apps, srcset, CSS, or stored application data. Explicit formats consume 1 transformation unit; auto consumes 3 units. When to use: after an image is uploaded and the user wants a resized, cropped, optimized, or converted delivery URL. The returned URL is safe to send to browsers; the API key remains server-side. Returns: JSON { url, expiresAt, delivery, transform, usage }. Has the side effect of reserving monthly transformation units for a new unique variant.

  Connector

• weather_request_credential_channel

  tollbooth-sample

  Open a Secure Courier channel for credential delivery. This is the CREDENTIAL-DELIVERY flow — use it to hand over a service secret (API keys, tokens). To merely prove you control an npub (the usual answer to a ``proof_required`` error), use ``request_npub_proof`` instead. Note: dynamic/OAuth2 services (e.g. Schwab) need NO couriered secret — check ``service_status`` first. Sends a welcome DM with a credential template. The recipient must read the DM in their Nostr client, fill in the fields, and reply manually. **This is a human-in-the-loop flow.** After calling this tool, STOP and tell the user what to do. Wait for the user to confirm they have replied before calling ``receive_credentials``. Do NOT poll or retry — each ``receive_credentials`` call destructively drains the relay mailbox.

  Connector