Skip to content

AnyHook MCP server

net.anyhook/anyhookanyhook.netstreamable-httpv0.6.2Scanned

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

17 tools: 8 can delete or cancel things, 4 change things and 5 only read.

Tools: 8 delete, 0 irreversible, 4 write, 5 read.
  • Reads private data · 1
  • Reads text others write · 7
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

8 tools here can delete or cancel things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the AnyHook MCP server can do

The AnyHook MCP server is published by anyhook.net, a domain the MCP Registry verified. It has 17 tools. It can delete or cancel things (8 tools: anyhook_mock, anyhook_apps_create, anyhook_destination_add, anyhook_connect and 4 more) and create or change data (4 tools: anyhook_verify, anyhook_inbox, anyhook_undelivered and anyhook_usage). 5 tools only read.

1 tool reads private data (anyhook_code_get); 7 tools bring in text other people can write (anyhook_mock, anyhook_destination_add, anyhook_connect and 4 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 3 times since Anlyon Radar first saw them.

Last scanned Nov 9, 2026, version 0.6.2.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

17 tools

Deletes or cancels 8Claude Code: deny
  • anyhook_apps_createCreate a new app with a name, provider source, and (optionally) destinations.No findings

    Why it is in this group

    • The name "anyhook_apps_create" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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 with anyhook_destination_add.

    Annotations the server declares

    • title: Create a new AnyHook app
    • readOnlyHint: false
    • destructiveHint: true
  • anyhook_code_deploySave 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.Reads text others writeNo findings

    Why it is in this group

    • The name "anyhook_code_deploy" says "deploy": a word for a change.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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). anyhook_code_test runs it on a stored event.

    Annotations the server declares

    • title: Deploy code that runs on an app's events
    • readOnlyHint: false
    • destructiveHint: true
    • openWorldHint: true
  • anyhook_code_testRun 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.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "run": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Run an app's code on a stored event
    • readOnlyHint: false
    • destructiveHint: true
    • openWorldHint: true
  • anyhook_connectWire 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, an…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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. Until the app has a destination (anyhook_destination_add), events are received and logged but not forwarded.

    Annotations the server declares

    • title: Connect Stripe or GitHub with one key
    • readOnlyHint: false
    • destructiveHint: true
    • openWorldHint: true
  • anyhook_destination_addAdd a destination to an existing app: new events are forwarded to this URL, with retries, within about a minute, and the app's other destinations stay as they are.Reads text others writeNo findings

    Why it is in this group

    • The name "anyhook_destination_add" says "add": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Add a destination to an existing app: new events are forwarded to this URL, with retries, within about a minute, and the app's other destinations stay as they are. Adding a URL the app already has changes nothing. Returns the destination's signing secret once, for verifying the AnyHook-Signature header on the receiving server.

    Annotations the server declares

    • title: Forward an app's events to a URL
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
  • anyhook_mockGenerate a webhook request with a valid signature for Stripe, GitHub, or Slack.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "generate": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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. This hosted server reaches public https URLs only; to reach localhost, run npx -y anyhook-mcp.

    Annotations the server declares

    • title: Mock a webhook
    • readOnlyHint: false
    • destructiveHint: true
    • openWorldHint: true
  • anyhook_replayRe-send a stored event to its destinations.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Replay an event
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • anyhook_replay_failedRe-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…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Bulk-replay an app's failed events
    • readOnlyHint: false
    • destructiveHint: true
    • openWorldHint: true
Changes things 4Claude Code: ask
  • anyhook_inboxEvery 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.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get this app's email inbox address
    • readOnlyHint: true
  • anyhook_undeliveredEvents for the given app that have not reached a destination: failed, held (circuit_open, quota_exceeded), still retrying, or logged while anyhook-mcp listen was stopped.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Events for the given app that have not reached a destination: failed, held (circuit_open, quota_exceeded), still retrying, or logged while anyhook-mcp listen was stopped. An app with no destination has none: its events are logged, not forwarded.

    Annotations the server declares

    • title: List undelivered events for an app
    • readOnlyHint: true
  • anyhook_usageWhat 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 (retrie…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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. It says how much is left when something answers with a limit, before bulk work such as replay_failed, or when the user asks what they are using.

    Annotations the server declares

    • title: Show plan limits and usage
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • anyhook_verifyVerify a webhook signature against a secret, for every source the AnyHook edge verifies, including stripe, github, shopify, slack, line, discord, linear, vercel, paddle, hubspot, p…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Verify a webhook signature
    • readOnlyHint: true
Only reads 5Show 5 read-only tools
  • anyhook_apps_listList apps in your AnyHook account with inbound URLs, sources, and destination URLs.No findings

    Why it is in this group

    • The name "anyhook_apps_list" says "list": a word for reading.
    Description, as the server wrote it
    List apps in your AnyHook account with inbound URLs, sources, and destination URLs. With isActive false, an 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.

    Annotations the server declares

    • title: List your AnyHook apps
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • anyhook_code_getThe 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.Reads private dataNo findings

    Why it is in this group

    • The name "anyhook_code_get" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "secret": it reads secrets.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Read an app's code handler
    • readOnlyHint: true
  • anyhook_eventsList webhook events, most recent first: id, app, type, status, attempt, destination status code, latency, timestamp.No findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List recent webhook events
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • anyhook_inspectFull detail for one event by id, including the inbound headers and body that anyhook_events omits, plus the destination's response.No findings

    Why it is in this group

    • The name "anyhook_inspect" says "inspect": a word for reading.
    Description, as the server wrote it
    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 it reads one event at a time, for when the body is needed. Account or local store.

    Annotations the server declares

    • title: Inspect a specific event
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • anyhook_providersList webhook providers AnyHook can mock, along with the event types available for each.No findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.
    Description, as the server wrote it
    List webhook providers AnyHook can mock, along with the event types available for each.

    Annotations the server declares

    • title: List supported providers and event types
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write7
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:16 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
12
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://anyhook.net/.well-known/oauth-protected-resource/mcp
Authorization servers
https://clerk.anyhook.net
Legacy HTTP+SSE transport
no
Dynamic client registration
no
Client ID metadata documents
yes
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 12 tools that change things (8 destructive, 4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://anyhook.net/mcp: tools/list returned 17 tools to an anonymous client, including anyhook_mock (destructive), anyhook_apps_create (destructive), anyhook_destination_add (destructive), anyhook_connect (destructive), anyhook_replay (destructive) and 7 more

    What this check looks for

Posture changes

  1. Nov 13, 2026
    • Tools that change things, listed without credentials: 10 to 12

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 10 -> 12.View diff
    • Tools that change things, listed without credentials: 10 to 12
  2. Tools3 changed.~3 changedView diff
  3. Tools1 added, 16 changed.+1 added~16 changedView diff
  4. Tools15 changed.~15 changedView diff

Install

Pinned to version 0.6.2. Values in angle brackets are yours to fill in.

claude mcp add --transport http anyhook https://anyhook.net/mcp
claude mcp add --transport http anyhook https://anyhook.net/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__anyhook__anyhook_providers",
      "mcp__anyhook__anyhook_apps_list",
      "mcp__anyhook__anyhook_code_get",
      "mcp__anyhook__anyhook_events",
      "mcp__anyhook__anyhook_inspect"
    ],
    "ask": [
      "mcp__anyhook__anyhook_verify",
      "mcp__anyhook__anyhook_inbox",
      "mcp__anyhook__anyhook_undelivered",
      "mcp__anyhook__anyhook_usage"
    ],
    "deny": [
      "mcp__anyhook__anyhook_mock",
      "mcp__anyhook__anyhook_apps_create",
      "mcp__anyhook__anyhook_destination_add",
      "mcp__anyhook__anyhook_connect",
      "mcp__anyhook__anyhook_replay",
      "mcp__anyhook__anyhook_replay_failed",
      "mcp__anyhook__anyhook_code_deploy",
      "mcp__anyhook__anyhook_code_test"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as anyhook. Review it before you use it.

Capability tags behind 8 rules
  • mcp__anyhook__anyhook_mock untrusted-input
  • mcp__anyhook__anyhook_destination_add untrusted-input
  • mcp__anyhook__anyhook_connect untrusted-input
  • mcp__anyhook__anyhook_replay untrusted-input
  • mcp__anyhook__anyhook_replay_failed untrusted-input
  • mcp__anyhook__anyhook_code_get private-data
  • mcp__anyhook__anyhook_code_deploy untrusted-input
  • mcp__anyhook__anyhook_code_test untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/net.anyhook/anyhook/verify?hash=2857803e9a88340a58ce7938be0fcd8129d04be7e850d61ed46ad2612b9baf80" | jq -e '.changed == false'

Pinned hash 2857803e9a88, from Nov 9, 2026, 11:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/net.anyhook/anyhook/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for net.anyhook/anyhook
[![Anlyon Radar](https://radar.anlyon.com/badge/net.anyhook/anyhook.svg)](https://radar.anlyon.com/servers/net.anyhook/anyhook)

Source: MCP Registry · repository. Synced Nov 9, 2026, 11:18 UTC.

AnyHook MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the AnyHook MCP server safe?

No scan can promise that. What its definitions show: 17 tools, 12 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the AnyHook MCP server delete data?

Yes. 8 tools can delete, cancel or revoke something: anyhook_mock, anyhook_apps_create, anyhook_destination_add, anyhook_connect, anyhook_replay, anyhook_replay_failed and 2 more.

Can the AnyHook MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the AnyHook MCP server have?

17 tools: 8 destructive, 4 write, 5 read. anyhook_mock, anyhook_apps_create, anyhook_destination_add, anyhook_connect, anyhook_replay, anyhook_replay_failed, anyhook_code_deploy, anyhook_code_test and 9 more.

Does the AnyHook MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the AnyHook MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the AnyHook MCP server changed its tools?

Yes, 3 times since Anlyon Radar started tracking it, most recently on Nov 9, 2026. Every change is on this page and in its Atom feed.