webhooks.cc runs on your own machine — the client starts it, so there is no endpoint to ping. 23 installs a week from npm. Last commit 24 Oct 2026.
Capture, inspect, send and assert on webhooks and inbound email from your coding agent.
We read the source, 1 h ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const indexPath = path.join(CONTENT_DIR, slug, "index.mdx");
question: "What are the best RequestBin alternatives in 2026?",
"path": "/aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa…
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
NEXT_PUBLIC_SUPABASE_URL: ${{ secrets.NEXT_PUBLIC_SUPABASE_URL || 'https://ci-placeholder.supabase.co' }}
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add webhooks-cc -- npx -y @webhooks-cc/mcp
{
"mcpServers": {
"webhooks-cc": {
"command": "npx",
"args": [
"-y",
"@webhooks-cc/mcp"
]
}
}
}
[mcp_servers.webhooks-cc]
command = "npx"
args = ["-y", "@webhooks-cc/mcp"]
{
"mcpServers": {
"webhooks-cc": {
"command": "npx",
"args": [
"-y",
"@webhooks-cc/mcp"
]
}
}
}
{
"servers": {
"webhooks-cc": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@webhooks-cc/mcp"
]
}
}
}
Optional settings from the registry entry, left out of the block above:
WHK_API_KEY (webhooks.cc API key (whcc_...). Without one, the server offers the keyless agent sandbox).
Send email, manage domains, DNS, webhooks, templates, and inbound routing on MailKite
Capture HTTP, email, and DNS callbacks with webhook.site from MCP clients.
Webhook, email and DNS inboxes for AI agents to capture callbacks and test integrations.
MailDev MCP server. Manage Docker containers and inspect emails from your AI editor or MCP client.
Email for agents: domains, aliases, IMAP mailboxes, DNS, sending and webhooks via one API key.
Read, arrange, and build agents on your Hedwig email board from any AI client. Nothing ever sends.
Send and read WhatsApp messages on your Leporis account from AI coding agents, via your own API key.
Let your AI agent notify you by email, Slack, Discord, or webhook. One tool: send_notification.
Answers built from our own checks of this server.