anyhook-mcp
# AnyHook client packages
Source for the npm packages that go with [AnyHook](https://anyhook.net), a webhook relay: change one URL and your webhooks get automatic retries, a full event log, and one-click replay.
| Package | npm | What it is |
|---------|-----|------------|
| [`anyhook-mcp`](packages/mcp) | [](https://www.npmjs.com/package/anyhook-mcp) | MCP server — lets a coding agent set up and operate webhook infrastructure by itself |
| [`anyhook-verify`](packages/verify) | [](https://www.npmjs.com/package/anyhook-verify) | Verify `AnyHook-Signature` headers on your server (HMAC-SHA256, retry-safe) |
| `@anyhook/core` | not published | Shared internals (signature logic, provider fixtures), bundled into the two above |
## The 30-second version
```json
{ "mcpServers": { "anyhook": { "command": "npx", "args": ["-y", "anyhook-mcp"] } } }
```
No API key needed up front. The `anyhook_quickstart` tool provisions a live webhook endpoint and key on its own (no account, 7-day TTL, claimable into a free account later). 12 tools: quickstart, apps, events, inspect, replay, mock/simulate for testing, signature verification.
Prefer plain HTTP? The same bootstrap is one curl:
```bash
curl -X POST https://anyhook.net/api/v1/quickstart
```
## Development
pnpm workspace. Node 20+.
```bash
pnpm install
pnpm test # vitest across all packages
pnpm build # tsup
```
The hosted relay itself (ingress, forwarder, dashboard) is a separate closed-source service — this repo is the client tooling. API reference: [openapi.json](https://anyhook.net/openapi.json) · agent docs: [llms.txt](https://anyhook.net/llms.txt) · pricing: [pricing.md](https://anyhook.net/pricing.md)
## License
Apache-2.0
TDQS
Scored across 13 tools
Most tools target distinct lifecycle stages (create, list, inspect, replay, verify, mock), and descriptions clearly delineate summary vs detail and local vs remote. A few pairs overlap—replay/replay_failed and mock/simulate—but the descriptions are explicit enough that an agent can pick correctly.
All names share an anyhook_ prefix and avoid camelCase, but the grammatical pattern is inconsistent: verbs (replay, inspect, mock), nouns (events, providers, inbox), adjectives (undelivered), and noun-first compounds (apps_create, apps_list) are mixed. This is readable but not predictable enough to infer an unlisted tool's name.
Thirteen tools is squarely in the well-scoped range and maps to distinct steps in the webhook workflow: bootstrap/create, list/inspect, replay/verify/mock. None feel like filler, and the count supports a coherent utility without bloating the surface.
Core webhook lifecycle is covered: creating endpoints, listing events, inspecting payloads, replaying failed deliveries, mocking providers, and verifying signatures. Missing app/destination update/delete operations (PATCH is mentioned in a description but no tool exists) are the main gap, though they are work-aroundable via other tools.