AnyHook MCP server

• Registry namenet.anyhook/anyhookverified in the MCP registry

The registry name sits under anyhook.net. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-26
• Tools16
• Server calls itselfanyhook
• Server version0.4.0
• Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 154 ms.

• Its tools do every use case we checked: replay webhook events after the server was down; inspect incoming payloads and the server's responses.
• Checked on 1 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
• What an agent can do with it2 of 2 use cases
• Use43 npm downloads a week
• Answeredmeasuring1 of the 7 daily checks it takes to print a share
• Median first answer283 ms
• Space in an agent's context≈ 3,301 tokensthe definitions of all its tools (16), which an agent carries on every turn
• Tool definitionsA · 96 of 100
• Typed results0 of 16 toolsdeclared outputSchema: results come typed, read once

• Parameters without a type: in 1 of 16
• Parameters without a description: in 3 of 16

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• 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, for every source the AnyHook edge verifies, including stripe, github, shopify, slack, line, discord, linear, vercel, paddle, hubspot, paypal and xero.

• 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…

• 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…

• 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…

• 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 the monthly compute allowance (anyhook_usage), and replaying an event that was held for quota bills it as…

• 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_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_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…

• 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…

• 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…