Skip to content

AHOOK MCP server

app.ahook/ahookahook.appstreamable-httpv1.0.1Scanned

Webhooks designed for agents. Create inboxes, wait for events, list and extract them.

10 tools: 2 can delete or cancel things, 2 change things and 6 only read.

Tools: 2 delete, 0 irreversible, 2 write, 6 read.
  • Reads private data · 5
  • Reads text others write · 5
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

Anlyon alternative

4 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Its sign-in does not let Anlyon set up an OAuth client on its own, so there is no link to it here.

What the AHOOK MCP server can do

The AHOOK MCP server is published by ahook.app, a domain the MCP Registry verified. It has 10 tools. It can delete or cancel things (2 tools: delete_inbox and delete_event) and create or change data (2 tools: create_inbox and extract_field). 6 tools only read.

5 tools read private data (wait_for_event, list_events, get_event and 2 more); 5 tools bring in text other people can write (create_inbox, wait_for_event, list_events and 2 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 2 times since Anlyon Radar first saw them.

Last scanned Nov 19, 2026, version 1.0.1.

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.

10 tools

Deletes or cancels 2Claude Code: deny
  • delete_eventDelete one event from an inbox (per-event purge).No findings

    Why it is in this group

    • The name "delete_event" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Delete one event from an inbox (per-event purge). Auth: Authorization Bearer read token header. Archived (cold-storage) events cannot be purged this way.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • delete_inboxDelete an inbox and its events.No findings

    Why it is in this group

    • The name "delete_inbox" says "delete": a word for removing or ending something.
    • The description says "Irreversible".
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Delete an inbox and its events. Auth: Authorization Bearer read token header. Irreversible: under a PAP session this needs a user approval first (Operations v3) - the first call returns the operation to approve; retry with the approval in _meta[personalagentprotocol.org/approval].

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
Changes things 2Claude Code: ask
  • create_inboxCreate a webhook inbox.Reads text others writeNo findings

    Why it is in this group

    • The name "create_inbox" says "create": a word for a change.

    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
    Create a webhook inbox. Returns its ingest URL and a read token (shown once). The same slug is the inbox email address <slug>@ahook.app. Optional slug: a branded username for the inbox (3-63 lowercase letters, digits, and hyphens) — any account may pick one, including anonymous-free via MCP; the inbox never expires, so the slug is permanent. Reserved names are rejected (invalid_slug) and a taken name returns slug_taken.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • extract_fieldPull a JSON path out of an event body.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
    Pull a JSON path out of an event body. Auth: Authorization Bearer read token header.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 6Show 6 read-only tools
  • get_eventGet one event by id.Reads private dataNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe input names an inbox (input.inbox_id), and the tool reads: it reads mail.
    Description, as the server wrote it
    Get one event by id. Auth: Authorization Bearer read token header.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_inboxGet one inbox: its slug, ingest URL, plan, status, and event count.Reads private dataReads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe name "get_inbox" says "get" and "inbox": it reads mail.
    • private-dataThe description's first sentence says "get" and "inbox": it reads mail.
    • private-dataThe input names an inbox (input.inbox_id), and the tool reads: it reads mail.
    • untrusted-inputThe name "get_inbox" says "get" and "inbox": it reads inbound email, which other people can write.
    • untrusted-inputThe description's first sentence says "get" and "inbox": it reads inbound email, which other people can write.
    Description, as the server wrote it
    Get one inbox: its slug, ingest URL, plan, status, and event count. Auth: Authorization Bearer read token header.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_eventsList events in an inbox.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "list_events" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "inbox": it reads mail.
    • private-dataThe input names an inbox (input.inbox_id), and the tool reads: it reads mail.
    • untrusted-inputThe description's first sentence says "list" and "inbox": it reads inbound email, which other people can write.
    Description, as the server wrote it
    List events in an inbox. Auth: Authorization Bearer read token header.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_inboxesList the inboxes linked to your AHOOK account.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "list_inboxes" says "list": a word for reading.

    What it can reach

    • private-dataThe name "list_inboxes" says "list" and "inbox": it reads mail.
    • private-dataThe description's first sentence says "list" and "inbox": it reads mail.
    • untrusted-inputThe name "list_inboxes" says "list" and "inbox": it reads inbound email, which other people can write.
    • untrusted-inputThe description's first sentence says "list" and "inbox": it reads inbound email, which other people can write.
    Description, as the server wrote it
    List the inboxes linked to your AHOOK account. Auth: Authorization Bearer account key header.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • wait_for_eventWait for the next event in an inbox after a cursor, up to 30s.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "wait_for_event" says "wait": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "wait" and "inbox": it reads mail.
    • private-dataThe input names an inbox (input.inbox_id), and the tool reads: it reads mail.
    • untrusted-inputThe description's first sentence says "wait" and "inbox": it reads inbound email, which other people can write.
    Description, as the server wrote it
    Wait for the next event in an inbox after a cursor, up to 30s. Auth: Authorization Bearer read token header.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

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 data5
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write5
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, 18:22 UTC, unchanged since Nov 20, 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
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://ahook.app/.well-known/oauth-protected-resource/mcp
Authorization servers
https://auth.ahook.app
Legacy HTTP+SSE transport
no
Dynamic client registration
no
Client ID metadata documents
no
  • HighThe whole server

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

    Matched text

    https://ahook.app/mcp: tools/list returned 10 tools to an anonymous client, including delete_inbox (destructive), delete_event (destructive), create_inbox (write), extract_field (write)

    What this check looks for

Posture changes

  1. Nov 20, 2026
    • Tools that change things, listed without credentials: 3 to 4
    • RFC 9728 protected resource metadata: none to https://ahook.app/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://auth.ahook.app
    • Dynamic client registration: not observed to no
    • Client ID metadata documents: not observed to no

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: 3 -> 4; RFC 9728 protected resource metadata: none -> https://ahook.app/.well-known/oauth-protected-resource/mcp; Authorization servers: none -> https://auth.ahoo…View diff
    • Tools that change things, listed without credentials: 3 to 4
    • RFC 9728 protected resource metadata: none to https://ahook.app/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://auth.ahook.app
    • Dynamic client registration: not observed to no
    • Client ID metadata documents: not observed to no
  2. Tools4 added, 6 changed.+4 added~6 changedView diff
  3. Tools6 changed.~6 changedView diff

Install

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

claude mcp add --transport http ahook https://ahook.app/mcp
claude mcp add --transport http ahook https://ahook.app/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__ahook__wait_for_event",
      "mcp__ahook__list_events",
      "mcp__ahook__get_event",
      "mcp__ahook__get_inbox",
      "mcp__ahook__list_inboxes",
      "mcp__ahook__search"
    ],
    "ask": [
      "mcp__ahook__create_inbox",
      "mcp__ahook__extract_field"
    ],
    "deny": [
      "mcp__ahook__delete_inbox",
      "mcp__ahook__delete_event"
    ]
  }
}

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 ahook. Review it before you use it.

Capability tags behind 6 rules
  • mcp__ahook__create_inbox untrusted-input
  • mcp__ahook__wait_for_event private-data, untrusted-input
  • mcp__ahook__list_events private-data, untrusted-input
  • mcp__ahook__get_event private-data
  • mcp__ahook__get_inbox private-data, untrusted-input
  • mcp__ahook__list_inboxes private-data, 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/app.ahook/ahook/verify?hash=f33481e1abad03c4672241332f57dec63e5fb2b799babfb7e13c9b6e59a42b9e" | jq -e '.changed == false'

Pinned hash f33481e1abad, from Nov 19, 2026, 17:17 UTC.

Watch

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

https://radar.anlyon.com/servers/app.ahook/ahook/changes.xml

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

Badge

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

Source: MCP Registry · repository. Synced Nov 5, 2026, 20:17 UTC.

AHOOK MCP server: questions and answers

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

Is the AHOOK MCP server safe?

No scan can promise that. What its definitions show: 10 tools, 4 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 AHOOK MCP server delete data?

Yes. 2 tools can delete, cancel or revoke something: delete_inbox and delete_event.

Can the AHOOK 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 AHOOK MCP server have?

10 tools: 2 destructive, 2 write, 6 read. delete_inbox, delete_event, create_inbox, extract_field, wait_for_event, list_events, get_event, get_inbox and 2 more.

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

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

Does the AHOOK MCP server send data to outside services?

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

Has the AHOOK MCP server changed its tools?

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