list_webhook_requests — thenetworkery MCP Tool Read-only
list_webhook_requests
(list webhook requests) is one of 28 tools on the
thenetworkery
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call list_webhook_requests from your client
- Claude Code thenetworkery list_webhook_requests run in your project directory
- Claude Desktop thenetworkery list_webhook_requests ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor thenetworkery list_webhook_requests ~/.cursor/mcp.json
- VS Code thenetworkery list_webhook_requests .vscode/mcp.json
- Zed thenetworkery list_webhook_requests ~/.config/zed/settings.json
- Windsurf thenetworkery list_webhook_requests ~/.codeium/windsurf/mcp_config.json
- Cline thenetworkery list_webhook_requests ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI thenetworkery list_webhook_requests ~/.gemini/settings.json
- Grok thenetworkery list_webhook_requests .mcp.json (in your project root)
- ChatGPT thenetworkery list_webhook_requests Settings → Connectors → Advanced → Developer mode
- Claude.ai thenetworkery list_webhook_requests Settings → Connectors → Add custom connector
- LangChain thenetworkery list_webhook_requests pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http network-tools https://thenetworkery.com/mcpOther tools on this server
- domain_report
- dns_lookup
- dnssec
- nameserver_check
- email_auth
- email_headers
- email_record_builder
- blacklist
- ssl_check
- http_headers
- ct_search
- network_report
- whois
- bgp
- rpki
- peeringdb
- reverse_dns
- port_check
- subnet_calculator
- mcp_server_test
- jwt_decoder
- mac_lookup
- dn42_registry
- dn42_free
- dn42_peering_config
- create_webhook_url
- get_webhook_request
This list was read from the server itself, by connecting to it and calling tools/list on 11 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.