Skip to content
anlyon.devby Anlyon

AHOOK MCP server

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

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

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

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

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • 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.dev only lists and labels, and these labels are the same either way.

Compare with similar serversMarkdownJSONReport this listing

What the AHOOK MCP server can do

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

3 tools read private data (wait_for_event, list_events and get_event); 3 tools bring in text other people can write (create_inbox, wait_for_event and list_events).

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

Its tools changed once since anlyon.dev first saw them.

Last scanned Nov 5, 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.

6 tools

Deletes or cancels 1Claude Code: deny
  • 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 server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Delete an inbox and its events. Auth: Authorization Bearer read token header.

    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).

    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 3Show 3 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
  • 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
  • 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 data3
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
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.

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. Tools6 changed.~6 changedView diff
All changes to this server

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"
    ],
    "ask": [
      "mcp__ahook__create_inbox",
      "mcp__ahook__extract_field"
    ],
    "deny": [
      "mcp__ahook__delete_inbox"
    ]
  }
}

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 4 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

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://anlyon.dev/api/v1/servers/app.ahook/ahook/verify?hash=c070247aa9f66c69847cd841b6f177f145795007a2410db4451577a601315f6f" | jq -e '.changed == false'

Pinned hash c070247aa9f6, from Nov 5, 2026, 19:17 UTC.

Watch

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

https://anlyon.dev/servers/app.ahook/ahook/changes.xml

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

Badge

anlyon.dev badge for app.ahook/ahook
[![anlyon.dev](https://anlyon.dev/badge/app.ahook/ahook.svg)](https://anlyon.dev/servers/app.ahook/ahook)

Source: MCP Registry · repository. Synced Nov 5, 2026, 19: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: 6 tools, 3 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. 1 tool can delete, cancel or revoke something: delete_inbox.

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?

6 tools: 1 destructive, 2 write, 3 read. delete_inbox, create_inbox, extract_field, wait_for_event, list_events and get_event.

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, once since anlyon.dev started tracking it, most recently on Nov 5, 2026. Every change is on this page and in its Atom feed.