Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AnyHook

NPM · ANYHOOK-MCP · 2 COMPONENTS

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

0 this week 88 Trust /100

Last scanned (4 hours ago)

Scores higher than 92% of npm servers

Category Workflow Automation

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to gba3124/anyhook-mcp). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 1 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability40
  • 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage95
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 86% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 0
    • CVE-2023-54404 no longer affects this package ▲ security
    • Known CVEs: fail → pass ▲ security
    • Schema quality: 2779 → 3124 ▼ functional
    • Schema quality: unverified → 0 ▲ functional
    • First check of Capabilities: pass functional
    • Package version: 0.3.0 → 0.5.0 functional
  • 1 Nov 26 +1
    • Stability: 0.97 → pass security
  • 31 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 25 Oct 26 +1
    • Stability: 0.97 → pass security
  • 24 Oct 26 −5
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
  • 23 Oct 26 +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.

  • 22 Oct 26 0
    • Package version: 0.3.0 → 0.4.0 functional
  • 20 Oct 26 +16
    • Malware scan: unverified → pass ▲ security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/anyhook-mcp@0.5.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo gba3124/anyhook-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/gba3124/anyhook-mcp/.github/workflows/publish-mcp.yml@refs/tags/mcp-v0.5.0
Rekor log index 3677327746
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:b35da790701e2091e485bc639029549fb9c5a2fc0a99e49a04d729d4616faac1a1316fa2bcb299389dc55693c454ea93d7445a9f37a86be06fb4843ce

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 18 exposed · ~3,117 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
anyhook_apps_create ~169

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": [...]}).

NameTypeReqDescription
api_keystring–API key (ahk_live_...) from anyhook_quickstart. Only needed over HTTP when no Authorization header is set; ignored over stdio.
destinationsarray–Destination URLs that should receive forwarded events.
namestringyesHuman-readable app name.
sourcestringyesProvider name (stripe, github, shopify, ...). Used for signature auto-detection.

No output schema declared.

No examples provided.

anyhook_apps_list ~152

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.

NameTypeReqDescription
api_keystring–API key (ahk_live_...) from anyhook_quickstart. Only needed over HTTP when no Authorization header is set; ignored over stdio.

No output schema declared.

No examples provided.

anyhook_code_deploy ~653

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.

NameTypeReqDescription
api_keystring–API key (ahk_live_...) from anyhook_quickstart. Only needed over HTTP when no Authorization header is set; ignored over stdio.
appSlugstringyesThe app whose events the code runs on.
codestringyesAn 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 }…
enabledboolean–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…
schedulestring|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…
secretsobject–Environment variables for the code, read as env.NAME or process.env.NAME. Merged into the saved ones; null removes a name.

No output schema declared.

No examples provided.

anyhook_code_get ~103

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.

NameTypeReqDescription
api_keystring–API key (ahk_live_...) from anyhook_quickstart. Only needed over HTTP when no Authorization header is set; ignored over stdio.
appSlugstringyesThe app whose code handler to read.

No output schema declared.

No examples provided.

anyhook_code_test ~145

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.

NameTypeReqDescription
api_keystring–API key (ahk_live_...) from anyhook_quickstart. Only needed over HTTP when no Authorization header is set; ignored over stdio.
appSlugstringyes–
body––Run on this body instead of a stored event.
event_idstring–Run on this stored event. Omit for the app's latest event.

No output schema declared.

No examples provided.

anyhook_connect ~335

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.

NameTypeReqDescription
api_keystring–API key (ahk_live_...) from anyhook_quickstart. Only needed over HTTP when no Authorization header is set; ignored over stdio.
appSlugstring–Connect this existing app. Omit to create a new app for the provider.
provider_keystringyesA 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…
targetstring–GitHub only: "owner/repo", or an organization name for an org-wide hook. Optional when the token administers exactly one repository.

No output schema declared.

No examples provided.

anyhook_events ~197

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.

NameTypeReqDescription
api_keystring–API key (ahk_live_...) from anyhook_quickstart. Only needed over HTTP when no Authorization header is set; ignored over stdio.
appSlugstring–Filter to a specific app slug (account mode).
limitinteger––
sourcestring–Filter by provider source (local mode).
statusstring–Filter by status. Account mode: queued|success|retrying|failed|rejected|circuit_open|quota_exceeded. Local mode: received|forwarded|failed|retrying.

No output schema declared.

No examples provided.

anyhook_inbox ~119

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.

NameTypeReqDescription
api_keystring–API key (ahk_live_...) from anyhook_quickstart. Only needed over HTTP when no Authorization header is set; ignored over stdio.
appstring–App slug (from anyhook_apps_list). Defaults to your first app.

No output schema declared.

No examples provided.

anyhook_inspect ~119

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.

NameTypeReqDescription
api_keystring–API key (ahk_live_...) from anyhook_quickstart. Only needed over HTTP when no Authorization header is set; ignored over stdio.
idstringyesEvent ID returned by anyhook_events.

No output schema declared.

No examples provided.

anyhook_mock ~134

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.

NameTypeReqDescription
dataobject–Optional fields to deep-merge into the fixture.
eventstringyesEvent name (e.g. 'payment_intent.succeeded' for Stripe).
providerstringyesWebhook provider to simulate.
secretstring–Signing secret. Falls back to a deterministic default per provider.
targetUrlstring–If set, POST the generated request to this URL and return the response.

No output schema declared.

No examples provided.

anyhook_providers ~27

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

anyhook_quickstart ~127

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.

NameTypeReqDescription
destination_urlstring–Optional forwarding destination for the new endpoint.
sourcestring–Optional provider hint (stripe, github, shopify, ...).

No output schema declared.

No examples provided.

anyhook_replay ~150

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.

NameTypeReqDescription
api_keystring–API key (ahk_live_...) from anyhook_quickstart. Only needed over HTTP when no Authorization header is set; ignored over stdio.
idstringyesEvent ID to replay. Replay does not consume event quota; it is charged to the compute allowance.

No output schema declared.

No examples provided.

anyhook_replay_failed ~223

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.

NameTypeReqDescription
api_keystring–API key (ahk_live_...) from anyhook_quickstart. Only needed over HTTP when no Authorization header is set; ignored over stdio.
appSlugstringyesThe app whose failed events to replay.
limitinteger–Most events to replay in this call, 1 to 100. Default 50.
sincestring–Only events received after this ISO 8601 time. Default: 24 hours ago.

No output schema declared.

No examples provided.

anyhook_simulate ~82

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.

NameTypeReqDescription
dataobject––
eventstringyes–
providerstringyes–
secretstring––

No output schema declared.

No examples provided.

anyhook_undelivered ~85

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

NameTypeReqDescription
api_keystring–API key (ahk_live_...) from anyhook_quickstart. Only needed over HTTP when no Authorization header is set; ignored over stdio.
appSlugstringyes–
limitinteger––

No output schema declared.

No examples provided.

anyhook_usage ~158

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.

NameTypeReqDescription
api_keystring–API key (ahk_live_...) from anyhook_quickstart. Only needed over HTTP when no Authorization header is set; ignored over stdio.

No output schema declared.

No examples provided.

anyhook_verify ~139

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.

NameTypeReqDescription
bodystringyesRaw request body.
headersobjectyesRequest headers as a flat object.
providerstringyesProvider name (e.g. 'stripe', 'github', 'slack', 'generic').
requestUrlstring–Original request URL (required for Twilio/HubSpot). Defaults to a placeholder.
secretstringyesSigning secret to verify against.

No output schema declared.

No examples provided.

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.

npm · anyhook-mcp

# add to Claude Code
claude mcp add net-anyhook-anyhook -- npx -y anyhook-mcp
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.