Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AHOOK

REMOTE · AHOOK.APP

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

Available components

+4 this week 67 Trust /100

Last scanned (14 hours ago)

Scores higher than 52% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Workflow Automation

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security46
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1334 tokens (~121/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
  • Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 0
    • Schema quality: pass → fail ▼ functional
    • New tool “submit_feedback” functional
  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1
    • New tool “delete_event”, which the server declares destructive security
    • Tool “delete_inbox” rewrote its description, which is the text the model reads security
    • Schema quality: fail → pass ▲ functional
    • New tool “get_inbox” functional
    • New tool “list_inboxes” functional
  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Nov 26 0
    • Schema quality: pass → fail ▼ functional
    • New tool “search” functional
  • 10 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://ahook.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=ahook.app CN=WE1,O=Google Trust Services,C=US 12 Nov 2026 10 Feb 2027 ECDSA 256 ECDSA-SHA256 68b669967626e140136f4f0db9c89056
SANs: ahook.app, origin.ahook.app, *.origin.ahook.app
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of ahook.app. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
app. DS published 23684 8 Verified
ahook.app. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://ahook.app/mcp Verified 400
http (plaintext) http://ahook.app/mcp Served over HTTP 200
MCP tools · 11 exposed · ~1,276 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
create_inbox ~147

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.

NameTypeReqDescription
slugstring–Optional username slug for the inbox (e.g. vintagefinds). Any account may pick one, including anonymous-free via MCP; the inbox never expires, so the slug is permanent.

No output schema declared.

No examples provided.

delete_event ~65

Delete one event from an inbox (per-event purge). Auth: Authorization Bearer read token header. Archived (cold-storage) events cannot be purged this way.

NameTypeReqDescription
event_idintegeryesThe event id to delete.
inbox_idstringyesThe inbox id.

No output schema declared.

No examples provided.

delete_inbox ~99

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

NameTypeReqDescription
inbox_idstringyesThe inbox id returned when the inbox was created (private; the slug in the ingest URL is the public part).

No output schema declared.

No examples provided.

extract_field ~93

Pull a JSON path out of an event body. Auth: Authorization Bearer read token header.

NameTypeReqDescription
event_idintegeryesThe numeric id of the event.
inbox_idstringyesThe inbox id returned when the inbox was created (private; the slug in the ingest URL is the public part).
json_pathstringyesDot-separated path into the event JSON body, e.g. user.email.

No output schema declared.

No examples provided.

get_event ~67

Get one event by id. Auth: Authorization Bearer read token header.

NameTypeReqDescription
event_idintegeryesThe numeric id of the event.
inbox_idstringyesThe inbox id returned when the inbox was created (private; the slug in the ingest URL is the public part).

No output schema declared.

No examples provided.

get_inbox ~53

Get one inbox: its slug, ingest URL, plan, status, and event count. Auth: Authorization Bearer read token header.

NameTypeReqDescription
inbox_idstringyesThe inbox id returned when the inbox was created.

No output schema declared.

No examples provided.

list_events ~83

List events in an inbox. Auth: Authorization Bearer read token header.

NameTypeReqDescription
afterinteger–Only list events with an id greater than this cursor.
inbox_idstringyesThe inbox id returned when the inbox was created (private; the slug in the ingest URL is the public part).
limitinteger–Maximum number of events to return.

No output schema declared.

No examples provided.

list_inboxes ~29

List the inboxes linked to your AHOOK account. Auth: Authorization Bearer account key header.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search ~257

Search the public API index (AHOOK Search, 14,000+ callable APIs and MCP servers). Ranks for whether an agent can actually use a result: BM25 text relevance plus readiness (machine interface, declared auth, liveness, llms.txt, ownership, example call), freshness, authority, and completeness. Every result carries its score_breakdown. Auth: Authorization Bearer ahk_ account key header (create one with POST /api/v1/accounts). One search = 1 metered read (meter search_queries, included in the $1 base, no per-search charge in v1). Rate limit: free 10/min, paid 60/min.

NameTypeReqDescription
categorystring–Exact category match, e.g. tts, coding, ai-models, payments.
free_commercialboolean–Only results whose free tier states commercial use.
limitnumber–Max results, 1..50, default 10.
max_token_costnumber–Only results whose token_cost.input_per_1m fits.
max_unit_costnumber–Only results whose unit_cost.amount_min fits.
querystringyesSearch terms. Empty = browse mode: highest score first.

No output schema declared.

No examples provided.

submit_feedback ~256

File feedback for the AHOOK team as a support ticket: a feature request, a bug, something confusing, or anything else. A human reviews every filing; nothing is auto-built from it. Limited to 6 filings per day. Returns the ticket id and a public status URL.

NameTypeReqDescription
callback_urlstring–An https URL to notify when the feedback is reviewed or resolved. Must be a public https URL; private or internal URLs are rejected (platform-wide internal-URL block).
errorstring–The error text or message the agent hit, if the feedback is about an error.
kindstring–The kind of feedback. Defaults to feature_request.
propertystring–The property slug (for example "main-landing") or group id. Under a PAP session it defaults to the session's property and cannot be overridden. With a bare account key it is required.
session_idstring–The agent's session id, if it has one.
textstringyesThe feedback, bug report, or feature request, in your own words. Required. Maximum 2000 characters.
tool_namestring–The MCP tool the feedback is about, if any.

No output schema declared.

No examples provided.

wait_for_event ~127

Wait for the next event in an inbox after a cursor, up to 30s. Auth: Authorization Bearer read token header.

NameTypeReqDescription
afterinteger–Only return the first event with an id greater than this cursor (0 for the first event).
body_containsstring–Only return an event whose body contains this text.
inbox_idstringyesThe inbox id returned when the inbox was created (private; the slug in the ingest URL is the public part).
timeout_msinteger–How long to wait in milliseconds (max 30000).

No output schema declared.

No examples provided.

Install

How do I install the AHOOK MCP server?

AHOOK is a hosted endpoint at https://ahook.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · ahook.app

# add to Claude Code
claude mcp add --transport http app-ahook-ahook 'https://ahook.app/mcp'
Common questions

What is the AHOOK MCP server?

AHOOK is an MCP server listed in the public MCP registry as app.ahook/ahook. Webhooks designed for agents. Create inboxes, wait for events, list and extract them. This page covers its hosted endpoint (https://ahook.app/mcp).

Is the AHOOK MCP server safe to use?

AHOOK scores 67 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the AHOOK MCP server expose?

AHOOK exposes 11 tools: create_inbox, wait_for_event, list_events, get_event, extract_field, and 6 more. Their descriptions and schemas cost roughly 1,276 tokens of context every time the server is loaded.

Does the AHOOK MCP server require authentication?

No. We connected to AHOOK without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the AHOOK MCP server still maintained?

AHOOK is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the AHOOK MCP server?

VerifyMCP ran 13 checks on AHOOK, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.