authority-webhook-mcp
Authority Webhook MCP
A small, public-ready Node.js MCP server with one consequential boundary: publishing a normalized release notice to a configured webhook.
The server deliberately separates four concerns:
MCP input validation.
Exact action and target normalization.
The host-owned
ReleaseProviderboundary.Provider result evidence.
With no configuration it uses a deterministic dry-run provider. Set RELEASE_WEBHOOK_URL to use the HTTP provider; HTTPS is required except for localhost test endpoints. No production credential is needed to run or test the project.
Why this repository exists
Agent tools often place review or approval logic too early, before the final target and payload are known. Here the exact seam is explicit in ReleasePublisher.publish():
MCP request
-> validate
-> normalize action class + webhook target + exact input
-> ReleaseProvider.send(action) <-- consequential provider call
-> correlate provider resultThat seam makes the project suitable for evaluating a single-use authority gate without using a live external service.
Related MCP server: Change Trace MCP
Requirements
Node.js 20 or newer
npm
Run the checks
npm install
npm run ciRun as an MCP server
Dry-run mode:
npm run build
npm startLocal webhook sandbox:
RELEASE_WEBHOOK_URL=http://127.0.0.1:8787/releases npm startThe exposed tool is publish_release_notice:
{
"repository": "example/agent-tools",
"tag": "v1.2.0",
"summary": "Add a sandboxed release-notification tool."
}Run a deterministic evidence demo
The demo exercises the real normalization and provider boundary with the in-memory dry-run provider. It performs no network request and prints the exact action, its SHA-256 fingerprint, and the correlated provider result:
npm run demoThe dry-run provider request ID is derived from the action fingerprint, making the output reproducible and easy to compare without exposing credentials.
Current safety properties
Repository identifiers are normalized to
owner/name.Release tags and summaries have bounded formats.
Webhook URLs reject embedded credentials and non-HTTPS remote targets.
The action fingerprint covers the action class, exact target, and exact normalized input.
Invalid input fails before the provider runs.
Tests use an injected recording provider and make no external calls.
This baseline does not yet implement human approval, single-use consumption, tamper rejection, or replay protection. Those controls belong immediately before ReleaseProvider.send() and should be added only as a deliberate authority-gate integration, with tests that prove the provider remains untouched on every rejected path.
License
MIT
Available Tools
1 toolpublish_release_noticePublish release noticeA
Normalize and publish a release announcement to the configured webhook. Without RELEASE_WEBHOOK_URL, the provider is a local dry run.
Inputs: tag (required), summary (required), repository (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Remote MCP for Kiro release readiness, evidence binders, signoff, and CI approval receipts.
Deploy & release tracking with native MCP — ask Claude what's in production and cut the release.
Create, update, and publish changelog entries on your Patchlog changelog from any MCP client.
Generate changelogs, release emails, help-center articles, banners, and social posts from commits.
Related MCP Servers
- 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
- 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