Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/lestertww/webhookstudioWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/lestertww/webhookstudio/webhooks)<a href="https://agentmods.dev/mcp/lestertww/webhookstudio/webhooks"><img src="https://agentmods.dev/badge/mcp/lestertww/webhookstudio/webhooks/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/lestertww/webhookstudio/webhooks"><img src="https://agentmods.dev/badge/mcp/lestertww/webhookstudio/webhooks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
webhooks scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"webhooks": {
"url": "https://webhook-studio.com/mcp",
"type": "streamable-http"
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 6 lines scan A 9cba61acb3dd
webhooks is an MCP server published in the GitHub repository lestertww/webhookstudio (0 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
webhook
Send, validate, debug webhooks for AI agents. Runs locally from the @rog0x/mcp-webhook-tools npm package.
developers-mcp
Access Mastercard Developers APIs, documentation, and API specifications through MCP. Runs locally from the @mastercard/developers-mcp npm package.
stitchapi-docs
StitchAPI documentation search, running locally over MCP stdio. Bundled docs, no network calls per query — the offline/air-gapped counterpart to the hosted stitchapi.dev/api/mcp server. Runs locally from the @stitchapi/docs-mcp npm package.
bankapi-v1-azurecontainerapps
MCP server "bankapi-v1-azurecontainerapps", hosted remotely at app.bravestone-75bd2261.germanywestcentral.azurecontainerapps.io, as configured in erwinkramer/bank-api.
bankapi-v1-local
MCP server "bankapi-v1-local", hosted remotely at localhost, as configured in erwinkramer/bank-api.
mcp
Moved to net.anyhook/anyhook. Webhook relay for agents: keyless quickstart, replay, mock. Runs locally from the anyhook-mcp npm package. Needs 2 environment variables to run.