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/rog0x/mcp-webhook-toolsWrote 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/rog0x/mcp-webhook-tools/webhook)<a href="https://agentmods.dev/mcp/rog0x/mcp-webhook-tools/webhook"><img src="https://agentmods.dev/badge/mcp/rog0x/mcp-webhook-tools/webhook/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/rog0x/mcp-webhook-tools/webhook"><img src="https://agentmods.dev/badge/mcp/rog0x/mcp-webhook-tools/webhook.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
webhook 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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 · 10 lines scan A dd4b5ec7608e
webhook is an MCP server published in the GitHub repository rog0x/mcp-webhook-tools (0 stars, last pushed 7mo ago), with no licence file. 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
toolport-openapi-mcp
Turn any OpenAPI/Swagger spec into an MCP server: one tool per endpoint. A showcase for Toolport (toolport.app). Runs locally from the toolport-openapi-mcp npm package.
webhooks
Keyless webhook endpoints: capture, wait, replay, forward, and generate types from real traffic. Remote server at webhook-studio.com.
api2mcp
Serve any OpenAPI 3.x / Swagger 2.x API as a local MCP (Model Context Protocol) server over stdio, proxying tool calls to the upstream HTTP API. Runs locally from the @swayam5342/api2mcp npm package.
mendapi
Detect API breaking changes, scan your codebase for impact, and draft the fix. Runs locally. Runs locally from the mendapi npm package.
resend-mcp-server
MCP server for Resend — transactional email API for AI assistants... Runs locally from the @supernova123/resend-mcp-server npm package. Needs 1 environment variable to run.
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.