AnyHook
REMOTE · ANYHOOK.NET · SCANNED SEP 20
A webhook inbox for agents: one call returns a live URL. Mock, verify, inspect and replay.
Available components
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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1321 tokens (~120/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 Management92
- Stability check failed: schema churn in the 30 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 90% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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
How do I install the AnyHook MCP server?
AnyHook is a hosted endpoint at https://anyhook.net/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 · anyhook.net
claude mcp add --transport http net-anyhook-anyhook 'https://anyhook.net/mcp'
{
"mcpServers": {
"net-anyhook-anyhook": {
"url": "https://anyhook.net/mcp"
}
}
} {
"servers": {
"net-anyhook-anyhook": {
"type": "http",
"url": "https://anyhook.net/mcp"
}
}
} [mcp_servers.net-anyhook-anyhook] url = "https://anyhook.net/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"net-anyhook-anyhook": {
"type": "remote",
"url": "https://anyhook.net/mcp",
"enabled": true
}
}
} openclaw mcp add net-anyhook-anyhook --url 'https://anyhook.net/mcp' --transport streamable-http
mcp_servers:
net-anyhook-anyhook:
url: "https://anyhook.net/mcp" {
"McpServers": {
"net-anyhook-anyhook": {
"Transport": "http",
"Url": "https://anyhook.net/mcp"
}
}
} assistant mcp add net-anyhook-anyhook -t streamable-http -u 'https://anyhook.net/mcp'
{
"mcpServers": {
"net-anyhook-anyhook": {
"type": "http",
"url": "https://anyhook.net/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 18 Sept 26 0
- Tool “anyhook_inbox” rewrote its description, which is the text the model reads security
- Tool “anyhook_replay” rewrote its description, which is the text the model reads security
- Tool “anyhook_mock” is now declared destructive security
- Tool “anyhook_replay” is now declared destructive security
- Tool “anyhook_replay_failed” is now declared destructive security
- Server version: 0.2.3 → 0.2.4 functional
- 16 Sept 26 +54
- Stability: unverified → fail ▼ security
- Tool “anyhook_quickstart” was removed ▼ security
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. security
- Tool “anyhook_apps_list” rewrote its description, which is the text the model reads security
- Tool “anyhook_events” rewrote its description, which is the text the model reads security
- Tool “anyhook_inspect” rewrote its description, which is the text the model reads security
- Endpoint reachability: behind authorisation → reachable ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Destructive annotations: pass functional
- Server version: 0.2.2 → 0.2.3 functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 22 Aug 26 38
- Endpoint reachability: reachable → behind authorisation ▼ security
- Stability: 0.77 → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: unverified → pass ▲ security
- First check of Authorization: partial security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 21 Aug 26 0
- Tool “anyhook_quickstart” rewrote its description, which is the text the model reads security
- 20 Aug 26 0
- Tool “anyhook_apps_create” rewrote its description, which is the text the model reads security
- Tool “anyhook_verify” rewrote its description, which is the text the model reads security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 6 Aug 26 0
- Tool “anyhook_replay” rewrote its description, which is the text the model reads security
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 20 Sept 2026 · Probed https://anyhook.net/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=anyhook.net | CN=YR1,O=Let's Encrypt,C=US | 13 Aug 2026 | 11 Nov 2026 | RSA 2048 | SHA256-RSA | 6c928d43d5fdb96fd5cf9b9bbe09d715563 |
| SANs: anyhook.net | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of anyhook.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| net. | present | 37331 | 13 | Verified |
| anyhook.net. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://anyhook.net/.well-known/oauth-protected-resource/mcp"
Bearer resource_metadata="https://anyhook.net/.well-known/oauth-protected-resource/mcp"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Protected resource metadata
| Document | https://anyhook.net/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://anyhook.net |
| Authorisation server | https://clerk.anyhook.net |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://anyhook.net/mcp | Verified | 200 | |
| http (plaintext) | http://anyhook.net/mcp | HTTPS enforced | 308 | https://anyhook.net/mcp |
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 →
anyhook_apps_create Create a new AnyHook app ~169
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 (PATCH /api/v1/apps/{slug} with {"destinations": [...]}).
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | API key (ahk_live_...) from anyhook_quickstart. Only needed over HTTP when no Authorization header is set; ignored over stdio. |
| destinations | array | – | Destination URLs that should receive forwarded events. |
| name | string | yes | Human-readable app name. |
| source | string | yes | Provider name (stripe, github, shopify, ...). Used for signature auto-detection. |
No output schema declared.
No examples provided.
anyhook_apps_list List your AnyHook apps ~152
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 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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | API key (ahk_live_...) from anyhook_quickstart. Only needed over HTTP when no Authorization header is set; ignored over stdio. |
No output schema declared.
No examples provided.
anyhook_events List recent webhook events ~188
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 your AnyHook account when connected, otherwise the local in-memory store.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | API key (ahk_live_...) from anyhook_quickstart. Only needed over HTTP when no Authorization header is set; ignored over stdio. |
| appSlug | string | – | Filter to a specific app slug (account mode). |
| limit | integer | – | – |
| source | string | – | Filter by provider source (local mode). |
| status | string | – | Filter by status. Account mode: queued|success|retrying|failed. Local mode: received|forwarded|failed|retrying. |
No output schema declared.
No examples provided.
anyhook_inbox Get this app's email inbox address ~119
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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | API key (ahk_live_...) from anyhook_quickstart. Only needed over HTTP when no Authorization header is set; ignored over stdio. |
| app | string | – | App slug (from anyhook_apps_list). Defaults to your first app. |
No output schema declared.
No examples provided.
anyhook_inspect Inspect a specific event ~119
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 needed. Account or local store.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | API key (ahk_live_...) from anyhook_quickstart. Only needed over HTTP when no Authorization header is set; ignored over stdio. |
| id | string | yes | Event ID returned by anyhook_events. |
No output schema declared.
No examples provided.
anyhook_mock Mock a webhook ~134
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.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | Optional fields to deep-merge into the fixture. |
| event | string | yes | Event name (e.g. 'payment_intent.succeeded' for Stripe). |
| provider | string | yes | Webhook provider to simulate. |
| secret | string | – | Signing secret. Falls back to a deterministic default per provider. |
| targetUrl | string | – | If set, POST the generated request to this URL and return the response. |
No output schema declared.
No examples provided.
anyhook_providers List supported providers and event types ~27
List webhook providers AnyHook can mock, along with the event types available for each.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
anyhook_replay Replay an event ~108
Re-send a stored event to its destinations. Replay does not consume monthly event quota, but the destination does run its handler again: a receiver that is not idempotent will process the event twice while debugging.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | API key (ahk_live_...) from anyhook_quickstart. Only needed over HTTP when no Authorization header is set; ignored over stdio. |
| id | string | yes | Event ID to replay. Replay does not consume event quota. |
No output schema declared.
No examples provided.
anyhook_replay_failed Bulk-replay all failed events for an app ~88
Re-send every failed event for the given app slug. Useful after fixing a downstream bug to recover queued work.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | API key (ahk_live_...) from anyhook_quickstart. Only needed over HTTP when no Authorization header is set; ignored over stdio. |
| appSlug | string | yes | Bulk-replay every failed event for this app. |
No output schema declared.
No examples provided.
anyhook_undelivered List undelivered events for an app ~85
Show events for the given app that have not successfully reached any destination (failed or still retrying).
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | API key (ahk_live_...) from anyhook_quickstart. Only needed over HTTP when no Authorization header is set; ignored over stdio. |
| appSlug | string | yes | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
anyhook_verify Verify a webhook signature ~132
Verify a webhook signature against a secret. Supports 20 providers including stripe, github, shopify, slack, line, discord, linear, vercel, paddle, hubspot, and paypal.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Raw request body. |
| headers | object | yes | Request headers as a flat object. |
| provider | string | yes | Provider name (e.g. 'stripe', 'github', 'slack', 'generic'). |
| requestUrl | string | – | Original request URL (required for Twilio/HubSpot). Defaults to a placeholder. |
| secret | string | yes | Signing secret to verify against. |
No output schema declared.
No examples provided.
What is the AnyHook MCP server?
AnyHook is an MCP server listed in the public MCP registry as net.anyhook/anyhook. A webhook inbox for agents: one call returns a live URL. Mock, verify, inspect and replay. This page covers its hosted endpoint (https://anyhook.net/mcp).
Is the AnyHook MCP server safe to use?
AnyHook scores 92 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 AnyHook MCP server expose?
AnyHook exposes 11 tools: anyhook_mock, anyhook_verify, anyhook_providers, anyhook_apps_list, anyhook_inbox, and 6 more. Their descriptions and schemas cost roughly 1,321 tokens of context every time the server is loaded.
Does the AnyHook MCP server require authentication?
Yes. AnyHook asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the AnyHook MCP server still maintained?
AnyHook is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.