AnyHook

net.anyhook/anyhook · v0.3.0

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

MCPremotelocal · npmno credentialsDeveloper toolsFinanceCloud & DevOps

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 15 tools, protocol 2025-06-18 · checked 2026-10-17

Test & rating

B 82/100

What it does: 15 tools · 8 read, 7 write (incl. delete/pay) · Developer tools, Finance, Cloud & DevOps

Test call anyhook_providers: needs a key: rpc error: Unauthorized (952 ms)

How the rating is made

Answers without login: +30
Speed of first answer: +6
Lists tools: +10
Tool descriptions: +15
Parameter descriptions: +8
Read/write annotations: +5
Safe test call: +8
More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

Remote URL

https://anyhook.net/mcp

Package

registry:   npm
identifier: anyhook-mcp
version:    0.3.0
transport:  stdio

Tools

15 tools listed at last check

anyhook_mock 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.
anyhook_verify Verify a webhook signature against a secret. Supports 20 providers including stripe, github, shopify, slack, line, discord, linear, vercel, paddle, hubspot, and paypal.
anyhook_providers List webhook providers AnyHook can mock, along with the event types available for each.
anyhook_apps_list 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_si
anyhook_inbox 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.
anyhook_apps_create 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} w
anyhook_connect 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. W
anyhook_replay Re-send a stored event to its destinations. Replays sit outside the monthly event quota but within a daily replay limit per plan, 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 eve
anyhook_undelivered Show events for the given app that have not successfully reached any destination (failed or still retrying).
anyhook_replay_failed Re-send every failed event for the given app slug. Useful after fixing a downstream bug to recover queued work.
anyhook_code_get 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.
anyhook_code_deploy 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. P
anyhook_code_test 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.
anyhook_events List webhook events, most recent first: id, app, type, status, attempt, destination status code, latency, timestamp. Summaries only, no request headers or body — call anyhook_inspect with an id from here to read one event's payload. Uses your AnyHook account when connected, otherwise the local in-me
anyhook_inspect 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.

Badge

Markdown for your README

[![Connect-MCP](https://clawy.uk/mcp/badge/net.anyhook/anyhook.svg)](https://clawy.uk/mcp/s/net.anyhook/anyhook)

Repository · Website