Webhook MCP Server
MCP to Capture HTTP requests, emails, and DNS lookups test webhooks, debugg API callbacks
Is Webhook MCP Server safe? Promising trust profile, but some evidence still deserves review.
Compare Webhook MCP Server
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: Webhook MCP Server scores 68.3/100 (Grade B), ranked #373 of 1343 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 4.3/10; 11% of recent commits are signed; no published advisory affects its latest release (webhook-mcp-server); last pushed 2026-09-03. Every point is earned from checkable signals — never paid placement. How scoring works →
How Webhook MCP Server could raise its score
Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.
- Raise the OSSF Scorecard from 4.3 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Code-Review 0 +9.8 → 78.1 B · #99 of 778
- Sign every commit11% signed today +4.5 → 72.8 B · #163 of 778
How Webhook MCP Server compares in MCP Servers
- #225 Idea Reality MCP 68.4 +0.1
- #226 Edinet MCP 68.3 ±0
- #227 Webhook MCP Server 68.3 this agent
- #228 MCP Probe Kit 68.3 ±0
- #229 MCP Accessibility Scanner 68.0 −0.3
Bars show each HVTrust score; the tick marks Webhook MCP Server’s 68.3.
Where the 68.3 comes from
HVTrust dimensions vs the MCP Servers average
68.3 / 100 · 100.0% confidenceWebhook MCP Server MCP Servers average (778 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
46.8 / 100Supply Chain Trust
Common questions about Webhook MCP Server
Does Webhook MCP Server publish package provenance?
Does Webhook MCP Server have an OpenSSF Scorecard?
Is Webhook MCP Server actively maintained?
What license does Webhook MCP Server use?
Are Webhook MCP Server's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Webhook MCP Server's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain Webhook MCP Server?
For maintainers
HVTrust scores Webhook MCP Server from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/webhook-mcp-server)
<a href="https://hvtracker.net/agents/webhook-mcp-server"><img src="https://hvtracker.net/badge/webhook-mcp-server.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON