Skip to main content
Glama
216,151 tools. Last updated 2026-06-20 06:44

"namespace:dev.workers.m-zikriz.defi-webhook" matching MCP tools:

  • Runs a single end-to-end execution of an existing automation against a mock conversation, returning success/failure plus the channel target and duration. Mirrors a real production firing. Behavior: - Sends REAL messages by default: posts the configured webhook, sends the configured email, posts the Slack message, or writes the HubSpot record. Use override_email (email channels) or override_webhook (webhook channels) to redirect delivery to a safe test target. - Each call fires another real delivery. - Errors when the perspective or automation is not found, or you do not have access. Webhook URLs (configured or override) are validated. - Mock conversation defaults: trust score 85, status complete, "Test Participant" / test@example.com. Override participant_name, summary, and tags via test_data. - Returns success: true also when the automation's condition skips delivery (e.g., tag/trust filter doesn't match the mock). The error field is populated only on real delivery failures. When to use this tool: - Verifying a freshly-created automation actually delivers before relying on it (override_email / override_webhook direct the test to a safe target instead of real recipients). - Reproducing a delivery failure surfaced in automation_list (last_error). When NOT to use this tool: - Listing what's configured — use automation_list. - Changing config — use automation_update. - Removing the automation — use automation_delete.
    Connector
  • Abort an unpaid checkout and release its checkout_id. Use if the customer changes their mind after create_checkout but before completing payment. Has no effect on orders already confirmed by webhook. To restart, create a new cart and checkout from scratch.
    Connector
  • List, add, or remove webhook and digest subscriptions; configure or clear the agent's callback URL. ROUTING MODEL - Open-consultation webhooks fire to agents matched via EITHER an opt-in subscription (notification_categories) OR an existing expertise_scores row in the consultation's category. Subscriptions are therefore additive to automatic expertise-based routing — useful when you want pushes for a category before you have ranked responses there, or as a backup when you have not yet built expertise in a new domain. - Either way, the same delivery gates apply: ≥3 prior responses in category and ≥60% useful rating. A bare subscription alone (no responses, no expertise) does not produce webhook traffic. WHEN TO USE - You want push delivery of new consultations in a category where you do not yet have ranked responses (no expertise_scores row). - You want a daily summary of activity in a category, without real-time webhook overhead. - You need to set or rotate the HTTPS callback URL where Almured will POST signed webhook events. - You want to see your current subscription state (categories, callback domain, whether a webhook secret is set). WHEN NOT TO USE - For one-off browsing — use browse_consultations or browse_unanswered. - For unsubscribing entirely — call clear_callback (stops all webhook delivery) and unsubscribe from each category individually for digests. BEHAVIOR - Mutating (except action='list'). Auth required: API key as Authorization: Bearer <key>. Rate-limited to 10 req/min per agent. - Action contract: - 'list' — returns notification_categories, digest_categories, callback_url_domain, webhook_secret_set flag. - 'subscribe' — adds categories. Requires categories=comma-separated slugs and subscription_type ('notification' for real-time webhooks, 'digest' for daily summary). Validates against the live taxonomy. - 'unsubscribe' — removes categories. Same args as subscribe. - 'set_callback' — sets or rotates callback_url. Must start with 'https://'. On first set, returns a webhook_secret you must store immediately — it is shown once and used to verify HMAC-SHA256 signatures on inbound webhooks. - 'clear_callback' — removes callback_url and secret. All webhook delivery stops; digest delivery is unaffected. - Subscribing without a callback_url is allowed but no webhooks fire until one is set. - Webhook events are signed with the secret using HMAC-SHA256; verify the signature on every inbound POST. WORKFLOW - Set the callback URL first (set_callback), then subscribe to categories. - If you suspect the secret leaked, call set_callback again with the same URL to rotate. - Combine with get_expertise_badge to track how subscription-driven response volume affects your tier over time.
    Connector
  • Phase 2 of 2. Finalise a checkout and mint the payment link — Yoco for card payments or Ozow for instant EFT. Returns payment_url to share with the customer. Payment confirmation arrives via webhook; poll get_order afterwards to confirm paid status. Once called, the checkout is locked — use cancel_checkout to abort if the customer changes their mind before paying.
    Connector
  • Creates a Stripe-hosted Checkout page for a locked quote and returns a `checkoutUrl` plus a `statusUrl`. Use this as the LAST-RESORT payment rail, when the payer is a human paying by credit card (the agent cannot complete card entry itself). Hand the `checkoutUrl` to the user to open in a browser and pay; payment is asynchronous — once they finish, the letter is created automatically by Stripe's webhook. To track it without a job id, GET the returned `statusUrl` (`/v1/quotes/:quoteId/job`): it returns `found:false` with status `pending`/`processing` until the webhook creates the job, then the full job (id, status, tracking). Prefer x402 (or MPP, if available) for autonomous agent payment. Returns an error if Stripe Checkout is not enabled on the server. No charge occurs until the human completes the hosted page.
    Connector
  • 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

Matching MCP Servers

Matching MCP Connectors

  • Ai Solana Service

  • Webhook delivery to internal and public destinations, transform payloads, integrate any service

  • List webhook endpoints registered on an org. Returns each webhook's id, url, subscribed events, active flag, and an 8-char `secretPreview` of the signing secret (full secret is only returned at create / rotate-secret time). Any org member (user or agent) can list. Use to audit what's subscribed before adding or removing endpoints.
    Connector
  • Phase 2 of 2. Finalise a checkout and mint the payment link — Yoco for card payments or Ozow for instant EFT. Returns payment_url to share with the customer. Payment confirmation arrives via webhook; poll get_order afterwards to confirm paid status. Once called, the checkout is locked — use cancel_checkout to abort if the customer changes their mind before paying.
    Connector
  • List the agent's active webhook subscriptions. WHAT IT DOES: returns every webhook the calling agent has registered, in creation order. Read-only, no side effects. WHEN TO USE: to audit subscriptions before adding more, or to find the id of a webhook you want to delete. RETURNS: { webhooks: [{ id, url, events, gameId?, created_at, last_delivered_at?, last_status? }] }. Secret values are NOT returned (issued only at register time). RELATED: register_webhook (create), delete_webhook (remove).
    Connector
  • Poll the status of an async job (extract, indexing, batch). Free — no credits consumed. Jobs are created when you POST /v1/extract with a webhook, or when add_document_to_collection triggers async indexing. Poll until status is "complete" or "failed". Completed jobs include the bundle_id or result. Returns: { id, type: "extract"|"extract_batch"|"index_collection", status: "queued"|"processing"|"complete"|"failed"|"cancelled", progress_pct: number (0–100), progress_message, bundle_id (when complete), result_json (when complete), error (when failed), created_at, completed_at }
    Connector
  • Send a test event to a webhook endpoint. WHEN TO USE: - Verifying webhook endpoint is working - Testing integration during development - Debugging webhook delivery issues RETURNS: - success: Boolean indicating delivery success - response_code: HTTP response code from endpoint - response_time_ms: Response time in milliseconds - error: Error message if delivery failed EXAMPLE: User: "Test my webhook with a device.online event" test_webhook({ webhook_id: "wh_mmmpdbvj_8b7c5a59296d", event: "device.online" })
    Connector
  • Buy more credits to fund test runs that TestMyVibes' agents will execute on your behalf. Returns a Stripe Checkout URL the user must open to complete payment (Stripe requires human payment completion per their agentic-commerce policy). Once the user pays, the credits are added automatically by the Stripe webhook — poll get_credit_balance to confirm.
    Connector
  • List all webhook subscriptions for the partner account. WHEN TO USE: - Viewing all configured webhooks - Auditing webhook subscriptions - Finding a webhook to update or delete RETURNS: - webhooks: Array of webhook objects with: - webhook_id: Unique identifier - url: Endpoint URL - events: Subscribed events - enabled: Whether webhook is active - created_at: Creation timestamp - last_delivery: Last successful delivery time EXAMPLE: User: "Show me all my webhooks" list_webhooks({})
    Connector
  • Creates a Stripe-hosted Checkout page for a locked quote and returns a `checkoutUrl` plus a `statusUrl`. Use this as the LAST-RESORT payment rail, when the payer is a human paying by credit card (the agent cannot complete card entry itself). Hand the `checkoutUrl` to the user to open in a browser and pay; payment is asynchronous — once they finish, the letter is created automatically by Stripe's webhook. To track it without a job id, GET the returned `statusUrl` (`/v1/quotes/:quoteId/job`): it returns `found:false` with status `pending`/`processing` until the webhook creates the job, then the full job (id, status, tracking). Prefer x402 (or MPP, if available) for autonomous agent payment. Returns an error if Stripe Checkout is not enabled on the server. No charge occurs until the human completes the hosted page.
    Connector
  • Delete webhook by id (irreversible). Pass confirmed=true to actually delete; otherwise returns a no-op confirmation preview.
    Connector
  • List all webhook endpoints registered for the authenticated account. Secrets are never returned by this tool.
    Connector
  • Poll the status of an async job (extract, indexing, batch). Free — no credits consumed. Jobs are created when you POST /v1/extract with a webhook, or when add_document_to_collection triggers async indexing. Poll until status is "complete" or "failed". Completed jobs include the bundle_id or result. Returns: { id, type: "extract"|"extract_batch"|"index_collection", status: "queued"|"processing"|"complete"|"failed"|"cancelled", progress_pct: number (0–100), progress_message, bundle_id (when complete), result_json (when complete), error (when failed), created_at, completed_at }
    Connector
  • Permanently delete a webhook endpoint. The URL stops receiving events immediately and the secret is destroyed; recreate from scratch if you need to re-add it. To pause without losing config, use update_webhook with active:false instead.
    Connector
  • Query the current state of any in-flight async operation by operation_id. WHEN TO USE: Use to poll the state of a pending_async operation when no webhook callback has arrived or to check progress. WHEN NOT TO USE: Do not poll more frequently than once per 10 seconds — use webhook delivery for real-time updates instead. COST: $0.001 per_call LATENCY: ~50ms
    Connector
  • Fallback/non-widget tool for starting external Stripe Checkout after the user accepts a pay-per-use quote. Payment authorization is required before PromptFax can send; PromptFax treats webhook-confirmed authorization, not browser redirect, as payment truth. In ChatGPT widget sessions, do not call this after start_session because the widget's Pay & send step opens Checkout.
    Connector