Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

WebhookTest.net

REMOTE · WEBHOOKTEST.NET · SCANNED SEP 24

Anonymous webhook capture, inspection, waiting, and response configuration for AI agents.

Available components

+55 this week 78 Trust /100

Recent critical change

Authorization (18 Sept 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 651 tokens (~81/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage86
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 52% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the WebhookTest.net MCP server?

WebhookTest.net is a hosted endpoint at https://webhooktest.net/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · webhooktest.net

# add to Claude Code
claude mcp add --transport http net-webhooktest-webhook-tester 'https://webhooktest.net/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "net-webhooktest-webhook-tester": {
      "url": "https://webhooktest.net/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "net-webhooktest-webhook-tester": {
      "type": "http",
      "url": "https://webhooktest.net/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.net-webhooktest-webhook-tester]
url = "https://webhooktest.net/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "net-webhooktest-webhook-tester": {
      "type": "remote",
      "url": "https://webhooktest.net/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add net-webhooktest-webhook-tester --url 'https://webhooktest.net/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  net-webhooktest-webhook-tester:
    url: "https://webhooktest.net/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "net-webhooktest-webhook-tester": {
      "Transport": "http",
      "Url": "https://webhooktest.net/mcp"
    }
  }
}
# add to Vellum
assistant mcp add net-webhooktest-webhook-tester -t streamable-http -u 'https://webhooktest.net/mcp'
// mcp.json
{
  "mcpServers": {
    "net-webhooktest-webhook-tester": {
      "type": "http",
      "url": "https://webhooktest.net/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 24 Sept 26 0
    • Server version: 1.0.0 → 1.0.1 functional
  • 21 Sept 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 71 → 81 ▼ functional
    • “create_webhook_bucket” added an optional parameter “controlled_test” cosmetic
  • 18 Sept 26 +55
    • Authorization: unverified → fail ▼ critical
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
  • 17 Sept 26 −55
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: pass → unverified ▼ security
    • Authorization: fail → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 2 Sept 26 +1
    • Stability: 0.97 → pass security
  • 30 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Aug 26 75
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 24 Sept 2026 · Probed https://webhooktest.net/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=webhooktest.net CN=WE1,O=Google Trust Services,C=US 22 Sept 2026 21 Dec 2026 ECDSA 256 ECDSA-SHA256 6cfd9ec38e9462ed13e4ea2d4feddb21
SANs: webhooktest.net, *.webhooktest.net
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of webhooktest.net. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
net. present 37331 13 Verified
webhooktest.net. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://webhooktest.net/mcp Verified 200
http (plaintext) http://webhooktest.net/mcp HTTPS enforced 301 https://webhooktest.net/mcp
MCP tools · 8 exposed · ~551 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
clear_webhooks ~45

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

NameTypeReqDescription
bucket_idstringyes–
confirmbooleanyesmust be true to perform this destructive action
NameTypeReqDescription
errornull|object––
successboolean––

No examples provided.

configure_webhook_response ~107

Set the status, content type, body, safe response headers, and a delay up to 10 seconds returned by the webhook endpoint.

NameTypeReqDescription
bodystringyes–
bucket_idstringyes–
content_typestringyes–
delay_msinteger–response delay in milliseconds, from 0 to 10000
headersobject–optional response headers; server-managed and hop-by-hop headers are rejected
statusintegeryes–
NameTypeReqDescription
errornull|object––
successboolean––

No examples provided.

create_webhook_bucket ~74

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

NameTypeReqDescription
controlled_testboolean–set true only for maintainer QA or automated evaluations; not for a real user's first test
namestring–optional display name for the bucket
NameTypeReqDescription
dashboard_urlstring––
errornull|object––
idstring––
inactivity_policystring––
namestring––
webhook_endpointstring––

No examples provided.

delete_webhook_bucket ~48

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

NameTypeReqDescription
bucket_idstringyes–
confirmbooleanyesmust be true to perform this destructive action
NameTypeReqDescription
errornull|object––
successboolean––

No examples provided.

get_webhook ~89

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

NameTypeReqDescription
bucket_idstringyes–
include_sensitiveboolean–return sensitive header and query values; defaults to false
max_body_bytesinteger–maximum body bytes to return; defaults to 65536 and cannot exceed 262144
webhook_idstringyes–
NameTypeReqDescription
errornull|object––
webhooknull|object––

No examples provided.

get_webhook_bucket ~32

Read a bucket name and its configured HTTP response settings.

NameTypeReqDescription
bucket_idstringyesbucket capability ID
NameTypeReqDescription
dashboard_urlstring––
errornull|object––
idstring––
namestring––
response_bodystring––
response_content_typestring––
response_delay_msinteger––
response_headersobject––
response_statusinteger––
webhook_endpointstring––

No examples provided.

list_webhooks ~62

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

NameTypeReqDescription
bucket_idstringyes–
cursorstring–opaque cursor returned by a previous call
limitinteger–number of summaries to return, from 1 to 50
NameTypeReqDescription
dashboard_urlstring––
errornull|object––
has_moreboolean––
next_cursorstring––
webhooksnull|array––

No examples provided.

wait_for_webhook ~94

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

NameTypeReqDescription
after_webhook_idstring–wait for a capture newer than this webhook ID
bucket_idstringyes–
include_sensitiveboolean––
max_body_bytesinteger––
wait_secondsinteger–seconds to wait; defaults to 20 and cannot exceed 25
NameTypeReqDescription
errornull|object––
receivedbooleanyes–
webhooknull|object––

No examples provided.

Common questions

What is the WebhookTest.net MCP server?

WebhookTest.net is an MCP server listed in the public MCP registry as net.webhooktest/webhook-tester. Anonymous webhook capture, inspection, waiting, and response configuration for AI agents. This page covers its hosted endpoint (https://webhooktest.net/mcp).

Is the WebhookTest.net MCP server safe to use?

WebhookTest.net scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the WebhookTest.net MCP server expose?

WebhookTest.net exposes 8 tools: clear_webhooks, configure_webhook_response, create_webhook_bucket, delete_webhook_bucket, get_webhook, and 3 more. Their descriptions and schemas cost roughly 551 tokens of context every time the server is loaded.

Does the WebhookTest.net MCP server require authentication?

No. We connected to WebhookTest.net without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the WebhookTest.net MCP server still maintained?

WebhookTest.net is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.