authority-webhook-mcp
Related Servers
Alternatives to authority-webhook-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables verifying whether a release actually shipped by comparing one expected version across git tags, GitHub releases, npm, the MCP Registry, and GHCR, returning GO/NO-GO verdicts with per-surface evidence. It also supports focused npm and MCP Registry checks.60 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables automated semantic release notes, PR tagging, and changelog verification by integrating GitHub, GitLab, and Jira MCP servers.-
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to preflight MCP server submissions against store rejection causes, publish where automation is allowed, prepare form-based store submissions, and detect listing drift.273 npm3MIT
- AlicenseAqualityCmaintenanceEnables users to upload Android .aab files to Google Play test tracks and iOS .ipa files to TestFlight, then promote or release them to production through fastlane. Also supports rollout updates, release status checks, and confirmation-gated publishing actions.7Apache 2.0
- FlicenseNot gradedqualityCmaintenanceEnables triggering Jenkins release and patch pipelines through natural language, with support for MCP and web interfaces.-
- AlicenseAqualityDmaintenanceA local-first, model-neutral MCP server for collecting and normalizing change-scoped release evidence. It provides deterministic Git change summaries, evidence collection, and review bundles for agent review.77 npmApache 2.0
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion between tools. The single tool's purpose is clearly described, so agents can unambiguously select it.
The sole tool follows a clear verb_noun pattern (publish_release_notice), making it predictable and consistent within the set.
A single tool is minimal, which feels thin for a server named 'authority-webhook-mcp'. However, the tool is narrowly scoped to release notices, so the count is borderline rather than egregiously insufficient.
The tool covers the core action of normalizing and publishing a release notice, with a dry-run fallback. Missing are operations like configuration validation or history, but the primary workflow is complete.