Skip to content
Free Online Webhook Tester logo

Free Online Webhook Tester MCP server

Which MCP servers are Free Online Webhook Tester's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-19

← Back to Free Online Webhook Tester

Whose server it is
  • Registry namenet.webhooktest/webhook-testerverified in the MCP registry

The registry name sits under webhooktest.net. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-19
  • Stateanswerschecked 2026-10-19
  • Tools8
  • Server calls itselfnet.webhooktest/webhook-tester
  • Server version1.0.1
  • Protocol version2025-06-18

On 2026-10-19 the server answered initialize and tools/list without a sign-in. First answer in 197 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.

Once connected

  • create_webhook_bucket, delete_webhook_bucket change data without a sign-in: anyone with the address can call them.
  • Parameters are untyped or undescribed in 6 of 8 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 9, the first on 2026-10-19
  • INITE MCP score77 of 100answers 100 · definitions 88 · context 100 · connects 100 · lowered by the warning signs below
  • Answered100% of days9 of 9 daily checks
  • Median first answer540 ms
  • Space in an agent's context≈ 1,017 tokensthe definitions of all its tools (8), which an agent carries on every turn
  • Tool definitionsB · 88 of 100
  • Typed results8 of 8 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 6 of 8

What an agent can do with it

  • not sure · inspect headers and JSON bodies of incoming webhook requests
  • can do · return custom status codes to test sender retry behaviour
  • not sure · verify webhook payloads before writing the receiving code

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

  • Tools that change data, on a server that answers without a sign-in: create_webhook_bucket, delete_webhook_bucket

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers8 tools · read 2026-10-19
  • clear_webhooks

    Permanently delete every capture in a bucket. Requires confirm=true.

  • configure_webhook_response

    Set the status, content type (JSON, plain text, XML, or form-encoded), body, optional Retry-After or X-Hook-Secret header, and a delay up to 10 seconds returned by the webhook endpoint. Browser visits always receive plain text.

  • create_webhook_bucket

    Create an anonymous temporary webhook capture bucket. The returned bucket ID is a bearer capability and expires after 15 days of inactivity.

  • delete_webhook_bucket

    Permanently delete a bucket and all of its captures. Requires confirm=true.

  • get_webhook

    Read one webhook capture scoped to its bucket. Sensitive headers and query values are redacted by default.

  • get_webhook_bucket

    Read a bucket name and its configured HTTP response settings.

  • list_webhooks

    List webhook capture summaries in newest-first order using cursor pagination.

  • wait_for_webhook

    Return the latest capture, wait for a newer capture, or report received=false after the timeout.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "webhook-tester": {
      "type": "http",
      "url": "https://webhooktest.net/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http webhooktest https://webhooktest.net/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://webhooktest.net/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.