mcpbeat

Webhook Relay MCP Server

com.agishub/webhook-relay
answering

Webhook Relay is answering right now. Last checked 13 min ago. It exposes 2 tools. Last commit 31 Jul 2026.

Fire-and-forget webhooks for agents with guaranteed, retried delivery and status polling. x402

Uptime history 42 hours of history
42 hours agonow
100.0%
Uptime 24h
91 of 91 checks
2
Tools
read from the server
976 ms
Response time
average over 24h
1
Stars
last commit 31 Jul 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

run in your terminal
claude mcp add webhook-relay --transport http https://api.agishub.com/mcp/webhook
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "webhook-relay": {
      "url": "https://api.agishub.com/mcp/webhook"
    }
  }
}
~/.codex/config.toml
[mcp_servers.webhook-relay]
url = "https://api.agishub.com/mcp/webhook"
.cursor/mcp.json
{
  "mcpServers": {
    "webhook-relay": {
      "url": "https://api.agishub.com/mcp/webhook"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "webhook-relay": {
      "url": "https://api.agishub.com/mcp/webhook"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

relay
relay
Deliver a webhook (POST/PUT/PATCH a JSON payload to a URL) with guaranteed, retried delivery. Returns immediately with a job_id; AgisHub keeps retrying in the background until it succeeds.
status
status
Check the delivery status of a webhook job (queued / retrying / delivered / failed) by its job_id.

Endpoints

URLTransportStateLatencyChecked
https://api.agishub.com/mcp/webhook streamable-http answering 1165 ms 13 min ago

Webhook Relay — questions

Answers built from our own checks of this server.

What can Webhook Relay do?
It exposes 2 tools, read directly from the server on our last check. Among them: relay, status. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Webhook Relay working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 976 ms. The bar chart above shows every period we have measured.
How do I connect Webhook Relay?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Webhook Relay need an API key?
No. Webhook Relay completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Webhook Relay?
It answers our handshake in 976 ms on average, which is faster than 5% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Webhook Relay open source?
Yes — it is published under the MIT licence, written in TypeScript and 1 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.