MCP tool reference · #309 of 563 by publishers
test_webhook
Exposed by 11 servers from 11 publishers, read from the live servers by the Serverdex check; most of them sit in Crypto & Web3; 45.5% of them take a webhook_id parameter; the most-starred is Lightning Wallet (11 stars).
test_webhook(webhook_id: string, id: string, …)Parameters
share = % of the 11 servers whose schema has it · required = % of those that mark it required| Parameter | Type | Share | Required | Usual description |
|---|---|---|---|---|
| webhook_id | string | 45.5% | 100% | ID of the webhook to test |
| id | string | 27.3% | 100% | Identifier of the endpoint to ping. |
| api_key | string | 9.1% | 0% | Your api_key from register_agent (mx_...). Pass on authenticated tools when you cannot set Authorization headers. Never send this key to any host except https:/ |
| endpoint_id | string | 9.1% | 100% | — |
| idempotency_key | string | 9.1% | 0% | Optional: any unique string for this action; send the same one when retrying the same call and the first result comes back instead of the action running twice |
| project_id | string | 9.1% | 100% | Project (website) id from list_projects, create_project, or bootstrap_site. |
Source: the input schema each server returns for test_webhook, aggregated over the 11 index-tier servers; type and description are the values most servers use. Rebuilt every 6 hours.
Servers with test_webhook
11 of 11 · 11 publishers · 11 answering live · most-starred first, 3 per publisher| # | Server | Publisher | Category | ★ | Live | How it describes test_webhook |
|---|---|---|---|---|---|---|
| 1 | Lightning Walletlightningfaucet · Crypto & Web3 | lightningfaucet | Crypto & Web3 | 11 | yes | Send a test event to a webhook to verify it works. REQUIRES AGENT KEY. |
| 2 | SimianX AIsimianx-ai · Crypto & Web3 | simianx-ai | Crypto & Web3 | 8 | yes | POST a signed test event to the webhook now, right after creating or changing one, to confirm the user's endpoint receives and verifies it. |
| 3 | EchoCallechocall-llc · AI & Agents | echocall-llc | AI & Agents | 1 | yes | Send a test delivery Sends one signed `webhook.test` payload to the endpoint and reports what happened, synchronously and with no retry. This is a real delivery: it is signed with the endpoint's secret, so it is the right way to check your signature verification. It updates `lastDeliveryAt` and `lastDeliveryStatus` and nothing else: a failed test never counts towards the automatic disabling that |
| 4 | NicheDBprofullstack · Content & Publishing | profullstack | Content & Publishing | 1 | yes | Send a webhook.test event to one of your endpoints now and report the HTTP status. Needs a key. |
| 5 | Furrow Formsuseburrow · Developer Tools | useburrow | Developer Tools | 1 | yes | Use to POST a signed webhook.test event to the project's webhook URL. Available on free and yearly. Do not use this to inspect past deliveries — that is REST GET /api/projects/:id/webhook-deliveries. Fails if no webhook URL and secret are set. |
| 6 | Vectorial Data Terminal: Hyperliquid, Polymarket & yield for AI agentsvectorialdata · Crypto & Web3 | vectorialdata | Crypto & Web3 | — | yes | Send a synchronous signed test event to a webhook and report the receiver's response — verify your endpoint + HMAC handling before relying on real events. |
| 7 | TextKittextkithq · Communication | textkithq | Communication | — | yes | Send a signed test.ping to a webhook endpoint and see what it answered. |
| 8 | BorealHostalainsvrd · Cloud & DevOps | alainsvrd | Cloud & DevOps | — | yes | Send a test event to a webhook endpoint (async). Poll list_webhooks afterwards for last_status. Requires: API key with write scope. Returns: {"id", "message"} |
| 9 | dmarc-examiner MCPdmarc-examiner · Data & Analytics | dmarc-examiner | Data & Analytics | — | yes | Send a synchronous webhook.test event to verify connectivity. Returns the delivery status. Test events do NOT update last_triggered_at, last_status or failure_count. |
| 10 | Kamykamy-development · Documents & Knowledge | kamy-development | Documents & Knowledge | — | yes | Send a real test.ping event to a registered webhook endpoint — an actual outbound HTTP POST to whatever URL the user configured, signed like a genuine delivery. Use it to prove an endpoint is reachable and that signature verification works before relying on it. Delivery is dispatched in the background, so the { message: 'Test ping dispatched' } you get back means accepted for sending, not that the |
| 11 | Duamimjbf5g7y8m-byte · Files & Storage | mjbf5g7y8m-byte | Files & Storage | — | yes | Send a signed webhook.test event to your webhook_url right now (with your custom headers) and report the HTTP status. Use after update_agent to confirm your endpoint receives pushes. |
Stars from GitHub as stored in the Serverdex index (re-read every 7 days per server); live = answered the last daily check of its hosted endpoint.