WebhookTest.net MCP server
net.webhooktest/webhook-testerwebhooktest.netstreamable-httpv1.0.1Scanned
Anonymous webhook capture, inspection, waiting, and response configuration for AI agents.
8 tools: 2 can delete or cancel things, 2 change things and 4 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here can delete or cancel things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the WebhookTest.net MCP server can do
The WebhookTest.net MCP server is published by webhooktest.net, a domain the MCP Registry verified. It has 8 tools. It can delete or cancel things (2 tools: clear_webhooks and delete_webhook_bucket) and create or change data (2 tools: configure_webhook_response and create_webhook_bucket). 4 tools only read.
1 tool brings in text other people can write (get_webhook_bucket).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 18, 2026, version 1.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
8 tools
Deletes or cancels 2Claude Code: deny
clear_webhooksPermanently delete every capture in a bucket.No findings
Why it is in this group
- The description's first verb is "delete": a word for removing or ending something.
- The description says "Permanently delete".
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Permanently delete every capture in a bucket. Requires confirm=true.
Annotations the server declares
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
- readOnlyHint: false
- title: Clear captured webhooks
delete_webhook_bucketPermanently delete a bucket and all of its captures.No findings
Why it is in this group
- The name "delete_webhook_bucket" says "delete": a word for removing or ending something.
- The description says "Permanently delete".
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Permanently delete a bucket and all of its captures. Requires confirm=true.
Annotations the server declares
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
- readOnlyHint: false
- title: Delete webhook bucket
Changes things 2Claude Code: ask
configure_webhook_responseSet 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 endp…No findings
Why it is in this group
- The description's first verb is "set": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
- readOnlyHint: false
- title: Configure webhook response
create_webhook_bucketCreate an anonymous temporary webhook capture bucket.No findings
Why it is in this group
- The name "create_webhook_bucket" says "create": a word for a change.
Description, as the server wrote it Create an anonymous temporary webhook capture bucket. The returned bucket ID is a bearer capability and expires after 15 days of inactivity.
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
- readOnlyHint: false
- title: Create webhook bucket
Only reads 4Show 4 read-only tools
get_webhookRead one webhook capture scoped to its bucket.No findings
Why it is in this group
- The name "get_webhook" says "get": a word for reading.
Description, as the server wrote it Read one webhook capture scoped to its bucket. Sensitive headers and query values are redacted by default.
Annotations the server declares
- idempotentHint: false
- openWorldHint: false
- readOnlyHint: true
- title: Get captured webhook
get_webhook_bucketRead a bucket name and its configured HTTP response settings.Reads text others writeNo findings
Why it is in this group
- The name "get_webhook_bucket" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "read" and "http": it reads web pages, which anyone can write.
Description, as the server wrote it Read a bucket name and its configured HTTP response settings.
Annotations the server declares
- idempotentHint: false
- openWorldHint: false
- readOnlyHint: true
- title: Get webhook bucket
list_webhooksList webhook capture summaries in newest-first order using cursor pagination.No findings
Why it is in this group
- The name "list_webhooks" says "list": a word for reading.
Description, as the server wrote it List webhook capture summaries in newest-first order using cursor pagination.
Annotations the server declares
- idempotentHint: false
- openWorldHint: false
- readOnlyHint: true
- title: List captured webhooks
wait_for_webhookReturn the latest capture, wait for a newer capture, or report received=false after the timeout.No findings
Why it is in this group
- The name "wait_for_webhook" says "wait": a word for reading.
Description, as the server wrote it Return the latest capture, wait for a newer capture, or report received=false after the timeout.
Annotations the server declares
- idempotentHint: false
- openWorldHint: false
- readOnlyHint: true
- title: Wait for a webhook
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:16 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 4
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (2 destructive, 2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://webhooktest.net/mcp: tools/list returned 8 tools to an anonymous client, including clear_webhooks (destructive), delete_webhook_bucket (destructive), configure_webhook_response (write), create_webhook_bucket (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http webhook-tester https://webhooktest.net/mcpclaude mcp add --transport http webhook-tester https://webhooktest.net/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__webhook-tester__get_webhook",
"mcp__webhook-tester__get_webhook_bucket",
"mcp__webhook-tester__list_webhooks",
"mcp__webhook-tester__wait_for_webhook"
],
"ask": [
"mcp__webhook-tester__configure_webhook_response",
"mcp__webhook-tester__create_webhook_bucket"
],
"deny": [
"mcp__webhook-tester__clear_webhooks",
"mcp__webhook-tester__delete_webhook_bucket"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as webhook-tester. Review it before you use it.
Capability tags behind 1 rule
- mcp__webhook-tester__get_webhook_bucket untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/net.webhooktest/webhook-tester/verify?hash=0c321707e496413eda91c49b2e62cf39ea2d4f94ad8b78b519b0ce1ce1f26283" | jq -e '.changed == false'Pinned hash 0c321707e496, from Nov 18, 2026, 21:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/net.webhooktest/webhook-tester/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/net.webhooktest/webhook-tester)Source: MCP Registry. Synced Oct 21, 2026, 18:53 UTC.
WebhookTest.net MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the WebhookTest.net MCP server safe?
- No scan can promise that. What its definitions show: 8 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the WebhookTest.net MCP server delete data?
- Yes. 2 tools can delete, cancel or revoke something: clear_webhooks and delete_webhook_bucket.
Can the WebhookTest.net MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the WebhookTest.net MCP server have?
- 8 tools: 2 destructive, 2 write, 4 read. clear_webhooks, delete_webhook_bucket, configure_webhook_response, create_webhook_bucket, get_webhook, get_webhook_bucket, list_webhooks and wait_for_webhook.
Does the WebhookTest.net MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the WebhookTest.net MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the WebhookTest.net MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.