# AnyHook (npm · anyhook-mcp)

A webhook inbox for agents: one call returns a live URL. Mock, verify, inspect and replay.

- Trust score: 88/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `anyhook.net`: 88/100, [markdown](https://verifymcp.io/servers/net-anyhook-anyhook/anyhook.md), [page](https://verifymcp.io/servers/net-anyhook-anyhook/anyhook)
- npm · `anyhook-mcp`: 88/100 (this document), [markdown](https://verifymcp.io/servers/net-anyhook-anyhook/anyhook-mcp.md), [page](https://verifymcp.io/servers/net-anyhook-anyhook/anyhook-mcp)

## Channel facts

- Registry: `npm`
- Package: `anyhook-mcp`
- Version: `0.5.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to gba3124/anyhook-mcp).
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 1 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 40/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 3124 tokens (~164/item across 19 items; 18 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 86% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the AnyHook MCP server?

AnyHook runs locally as an npm package, launched with npx -y anyhook-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add net-anyhook-anyhook -- npx -y anyhook-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "net-anyhook-anyhook": {
      "command": "npx",
      "args": [
        "-y",
        "anyhook-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "net-anyhook-anyhook": {
      "command": "npx",
      "args": [
        "-y",
        "anyhook-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add net-anyhook-anyhook -- npx -y anyhook-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "net-anyhook-anyhook": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "anyhook-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add net-anyhook-anyhook --command npx --arg -y --arg anyhook-mcp
```

### Hermes

```yaml
mcp_servers:
  net-anyhook-anyhook:
    command: "npx"
    args: ["-y", "anyhook-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "net-anyhook-anyhook": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "anyhook-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add net-anyhook-anyhook -t stdio -c npx -a -y anyhook-mcp
```

### Other

```json
{
  "mcpServers": {
    "net-anyhook-anyhook": {
      "command": "npx",
      "args": [
        "-y",
        "anyhook-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 88, 0)

- [security improvement] CVE-2023-54404 no longer affects this package
- [security improvement] Known CVEs: fail → pass
- [functional regression] Schema quality: 2779 → 3124
- [functional improvement] Schema quality: unverified → 0
- [functional] First check of Capabilities: pass
- [functional] Package version: 0.3.0 → 0.5.0

### 2026-11-01 (score 88, +1)

- [security] Stability: 0.97 → pass

### 2026-10-31 (score 87, −1)

- [functional] Stability: pass → 0.97

### 2026-10-25 (score 88, +1)

- [security] Stability: 0.97 → pass

### 2026-10-24 (score 87, −5)

- [security regression] CVE-2023-54404 affects this package: high
- [security regression] Known CVEs: pass → fail

### 2026-10-23 (score 92, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 91, 0)

- [functional] Package version: 0.3.0 → 0.4.0

### 2026-10-20 (score 91, +16)

- [security improvement] Malware scan: unverified → pass

## MCP tools (18)

### `anyhook_mock` (~134 tokens)

Mock a webhook

Generate a webhook request with a valid signature for Stripe, GitHub, or Slack. If targetUrl is provided, the request is POSTed there and the response is returned.

Input parameters:

- `data` (object): Optional fields to deep-merge into the fixture.
- `event` (string, required): Event name (e.g. 'payment_intent.succeeded' for Stripe).
- `provider` (string, required): Webhook provider to simulate.
- `secret` (string): Signing secret. Falls back to a deterministic default per provider.
- `targetUrl` (string): If set, POST the generated request to this URL and return the response.

### `anyhook_verify` (~139 tokens)

Verify a webhook signature

Verify a webhook signature against a secret, for every source the AnyHook edge verifies, including stripe, github, shopify, slack, line, discord, linear, vercel, paddle, hubspot, paypal and xero.

Input parameters:

- `body` (string, required): Raw request body.
- `headers` (object, required): Request headers as a flat object.
- `provider` (string, required): Provider name (e.g. 'stripe', 'github', 'slack', 'generic').
- `requestUrl` (string): Original request URL (required for Twilio/HubSpot). Defaults to a placeholder.
- `secret` (string, required): Signing secret to verify against.

### `anyhook_providers` (~27 tokens)

List supported providers and event types

List webhook providers AnyHook can mock, along with the event types available for each.

### `anyhook_quickstart` (~127 tokens)

Create a free AnyHook endpoint (no account needed)

Zero-config bootstrap: creates a free ephemeral relay endpoint + API key with no signup. Returns inbound_url (receives webhooks immediately), api_key, and claim_url. Relay claim_url to your user before the session ends, unclaimed workspaces self-delete in 7 days. This MCP session auto-connects to the new account; remote tools work right after. Endpoint expires in 7 days unless claimed.

Input parameters:

- `destination_url` (string): Optional forwarding destination for the new endpoint.
- `source` (string): Optional provider hint (stripe, github, shopify, ...).

### `anyhook_apps_list` (~152 tokens)

List your AnyHook apps

List apps in your AnyHook account with inbound URLs, sources, and destination URLs. Check isActive: an inactive app's inbound URL answers setup handshakes but acknowledges and discards event POSTs (202, reason app_inactive) instead of relaying them. Destination signing secrets are redacted to has_signing_secret plus a 4-char hint; a new secret in plaintext comes only from rotating it. An app whose slug was changed lists its former URLs under legacyInboundUrls; those still route to it.

Input parameters:

- `api_key` (string): API key (ahk_live_...) from anyhook_quickstart. Only needed over HTTP when no Authorization header is set; ignored over stdio.

### `anyhook_inbox` (~119 tokens)

Get this app's email inbox address

Every AnyHook app is also an email inbox: mail sent to {user}.{app}@anyhook.net becomes an event (type email.received) you can read with anyhook_events. Returns the address and webhook URL for one of your apps.

Input parameters:

- `api_key` (string): API key (ahk_live_...) from anyhook_quickstart. Only needed over HTTP when no Authorization header is set; ignored over stdio.
- `app` (string): App slug (from anyhook_apps_list). Defaults to your first app.

### `anyhook_apps_create` (~169 tokens)

Create a new AnyHook app

Create a new app with a name, provider source, and (optionally) destinations. Returns the inbound URL. The app is active immediately. Created WITHOUT destinations it still receives and LOGS every event (inspect-only), it just delivers nowhere until a destination is added (PATCH /api/v1/apps/{slug} with {"destinations": [...]}).

Input parameters:

- `api_key` (string): API key (ahk_live_...) from anyhook_quickstart. Only needed over HTTP when no Authorization header is set; ignored over stdio.
- `destinations` (array): Destination URLs that should receive forwarded events.
- `name` (string, required): Human-readable app name.
- `source` (string, required): Provider name (stripe, github, shopify, ...). Used for signature auto-detection.

### `anyhook_connect` (~335 tokens)

Connect Stripe or GitHub with one key

Wire a provider to AnyHook in one call: give a Stripe or GitHub key and AnyHook registers the app's inbound URL as a webhook at the provider, saves the signing secret it yields, and turns on signature verification at the edge. The provider is read from the key; the key is used once and not stored. Without appSlug a new app is created (and removed again if the provider refuses the key). Re-running replaces the registration instead of duplicating it. GitHub sends a signed ping immediately, so the first event appears within seconds. Add a destination afterwards (PATCH /api/v1/apps/{slug}) to forward events; until then they are received and logged.

Input parameters:

- `api_key` (string): API key (ahk_live_...) from anyhook_quickstart. Only needed over HTTP when no Authorization header is set; ignored over stdio.
- `appSlug` (string): Connect this existing app. Omit to create a new app for the provider.
- `provider_key` (string, required): A Stripe secret or restricted key (sk_… / rk_…) or a GitHub token (github_pat_… / ghp_…). The provider is read from the key. Used once to register the webhook at the provider; AnyHook does not store…
- `target` (string): GitHub only: "owner/repo", or an organization name for an org-wide hook. Optional when the token administers exactly one repository.

### `anyhook_replay` (~150 tokens)

Replay an event

Re-send a stored event to its destinations. Replays sit outside the monthly event quota but within a daily replay limit per plan and the monthly compute allowance (anyhook_usage), and replaying an event that was held for quota bills it as a new event. The destination does run its handler again: a receiver that is not idempotent will process the event twice while debugging.

Input parameters:

- `api_key` (string): API key (ahk_live_...) from anyhook_quickstart. Only needed over HTTP when no Authorization header is set; ignored over stdio.
- `id` (string, required): Event ID to replay. Replay does not consume event quota; it is charged to the compute allowance.

### `anyhook_undelivered` (~85 tokens)

List undelivered events for an app

Show events for the given app that have not successfully reached any destination (failed or still retrying).

Input parameters:

- `api_key` (string): API key (ahk_live_...) from anyhook_quickstart. Only needed over HTTP when no Authorization header is set; ignored over stdio.
- `appSlug` (string, required)
- `limit` (integer)

### `anyhook_replay_failed` (~223 tokens)

Bulk-replay an app's failed events

Re-send an app's failed events after the destination is fixed, oldest first: by default those received in the last 24 hours, at most 50 per call (since and limit change both; limit goes up to 100). Events held by an open circuit are included. An event replayed once is not selected again, so a second call continues with the rest. The result lists what was replayed, what was skipped and why, and more: true while failed events are still waiting. Replays count against the plan's daily replay limit.

Input parameters:

- `api_key` (string): API key (ahk_live_...) from anyhook_quickstart. Only needed over HTTP when no Authorization header is set; ignored over stdio.
- `appSlug` (string, required): The app whose failed events to replay.
- `limit` (integer): Most events to replay in this call, 1 to 100. Default 50.
- `since` (string): Only events received after this ISO 8601 time. Default: 24 hours ago.

### `anyhook_code_get` (~103 tokens)

Read an app's code handler

The code that runs on this app's events: its source, the names of its secrets (never the values), whether events are reaching it, and runs used this month against the plan's limit.

Input parameters:

- `api_key` (string): API key (ahk_live_...) from anyhook_quickstart. Only needed over HTTP when no Authorization header is set; ignored over stdio.
- `appSlug` (string, required): The app whose code handler to read.

### `anyhook_code_deploy` (~653 tokens)

Deploy code that runs on an app's events

Save a handler that runs on every event this app receives, in an isolated sandbox, with AnyHook's retries and replay around it: no server of your own. Each run's console output and return value are stored as that delivery's response (anyhook_inspect shows them). It can also run on a cron schedule. Pro and Scale; runs are capped per month with no overage, retries, test runs and schedule firings each count, and each run and package install is charged to the monthly compute allowance (anyhook_usage shows both). Test it with anyhook_code_test before real events arrive.

Input parameters:

- `api_key` (string): API key (ahk_live_...) from anyhook_quickstart. Only needed over HTTP when no Authorization header is set; ignored over stdio.
- `appSlug` (string, required): The app whose events the code runs on.
- `code` (string, required): An ES module, run in a sandboxed Node.js on every event this app receives. Either `export default async function (event, { env }) {}` (event: { method, headers, body, raw_body, delivery_id, attempt }…
- `enabled` (boolean): Whether events run the code. false saves it switched off, so it runs only through anyhook_code_test. Omit: a first deploy goes live and later deploys keep the current state. Deploy off while another…
- `schedule` (string|null): Also run on a cron schedule: five fields, UTC unless prefixed CRON_TZ=Area/City, e.g. "*/15 * * * *". Each firing arrives as an anyhook.schedule event and counts as a run. null removes it; omit to ke…
- `secrets` (object): Environment variables for the code, read as env.NAME or process.env.NAME. Merged into the saved ones; null removes a name.

### `anyhook_code_test` (~145 tokens)

Run an app's code on a stored event

Run the saved handler now and return its logs, return value and duration: on a stored event (the latest when event_id is omitted) or on a body you give. Counts as a run. Nothing is delivered, but whatever the code itself sends does happen.

Input parameters:

- `api_key` (string): API key (ahk_live_...) from anyhook_quickstart. Only needed over HTTP when no Authorization header is set; ignored over stdio.
- `appSlug` (string, required)
- `body`: Run on this body instead of a stored event.
- `event_id` (string): Run on this stored event. Omit for the app's latest event.

### `anyhook_usage` (~158 tokens)

Show plan limits and usage

What the plan allows and what this account has used of each: events this month (per delivery, large events count per 64 KB), overage, the compute allowance and what used it (retries, replays, waiting on slow destinations, code runs, builds, schedules), API calls today (each tool call that reads or changes the account counts one), code runs and package snapshots, with when each resets. Call it when something answers with a limit, before bulk work such as replay_failed, or when the user asks what they are using.

Input parameters:

- `api_key` (string): API key (ahk_live_...) from anyhook_quickstart. Only needed over HTTP when no Authorization header is set; ignored over stdio.

### `anyhook_events` (~197 tokens)

List recent webhook events

List webhook events, most recent first: id, app, type, status, attempt, destination status code, latency, timestamp. Summaries only, no request headers or body; anyhook_inspect reads one event's payload by the id from here. Uses your AnyHook account when connected, otherwise the local in-memory store.

Input parameters:

- `api_key` (string): API key (ahk_live_...) from anyhook_quickstart. Only needed over HTTP when no Authorization header is set; ignored over stdio.
- `appSlug` (string): Filter to a specific app slug (account mode).
- `limit` (integer)
- `source` (string): Filter by provider source (local mode).
- `status` (string): Filter by status. Account mode: queued|success|retrying|failed|rejected|circuit_open|quota_exceeded. Local mode: received|forwarded|failed|retrying.

### `anyhook_inspect` (~119 tokens)

Inspect a specific event

Full detail for one event by id, including the inbound headers and body that anyhook_events omits, plus the destination's response. Payloads can be large and often contain personal data, so fetch one at a time, only when the body is needed. Account or local store.

Input parameters:

- `api_key` (string): API key (ahk_live_...) from anyhook_quickstart. Only needed over HTTP when no Authorization header is set; ignored over stdio.
- `id` (string, required): Event ID returned by anyhook_events.

### `anyhook_simulate` (~82 tokens)

Simulate an incoming webhook (local only)

Generate a mocked webhook AND insert it into the local memory store, so list/inspect flows can be exercised without a real provider. Not available in remote mode, where a real inbound URL takes the place of the store.

Input parameters:

- `data` (object)
- `event` (string, required)
- `provider` (string, required)
- `secret` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/net-anyhook-anyhook/anyhook-mcp#diagnostics

## Score history

- 2026-11-05: 88
- 2026-11-04: 88
- 2026-11-03: 88
- 2026-11-02: 88
- 2026-11-01: 88
- 2026-10-31: 87
- 2026-10-30: 88
- 2026-10-29: 88
- 2026-10-28: 88
- 2026-10-27: 88
- 2026-10-26: 88
- 2026-10-25: 88
- 2026-10-24: 87
- 2026-10-23: 92
- 2026-10-22: 91
- 2026-10-21: 91
- 2026-10-20: 91
- 2026-10-19: 75
- 2026-10-18: 90
- 2026-10-17: 90
- 2026-10-16: 89
- 2026-10-15: 89
- 2026-10-14: 88
- 2026-10-13: 49
- 2026-10-12: 49
- 2026-10-04: 84
- 2026-10-03: 84
- 2026-10-02: 80
- 2026-10-01: 80
- 2026-09-30: 80

## Common questions

### What is the AnyHook MCP server?

AnyHook is an MCP server listed in the public MCP registry as net.anyhook/anyhook. A webhook inbox for agents: one call returns a live URL. Mock, verify, inspect and replay. This page covers its npm package (anyhook-mcp).

### Is the AnyHook MCP server safe to use?

AnyHook scores 88 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the AnyHook MCP server expose?

AnyHook exposes 18 tools: anyhook_mock, anyhook_verify, anyhook_providers, anyhook_quickstart, anyhook_apps_list, and 13 more. Their descriptions and schemas cost roughly 3,117 tokens of context every time the server is loaded.

### Is the AnyHook MCP server still maintained?

AnyHook is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the AnyHook MCP server under?

AnyHook declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/anyhook-mcp
- Socket report: https://socket.dev/npm/package/anyhook-mcp
- Repository: https://github.com/gba3124/anyhook-mcp
- Website: https://anyhook.net/
- Changelog RSS feed: https://verifymcp.io/servers/net-anyhook-anyhook/anyhook-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/net-anyhook-anyhook/anyhook-mcp.json
- HTML version of this page: https://verifymcp.io/servers/net-anyhook-anyhook/anyhook-mcp