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.

Openhook

REMOTE · OPENHOOK.DEV

Webhook, email and DNS inboxes for AI agents to capture callbacks and test integrations.

Available components

62 Trust /100

Last scanned (4 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 17 Oct 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 Security57
Transport & Reachability100
Schema Quality & AI Usability70
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 1481 tokens (~46/item across 32 items; 29 tools + 3 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
  • Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 6 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 31 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
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.

  • 17 Oct 26 0
    • Tool “access_hosted_inbox” is now declared destructive security
    • Tool “configure_webhook” is now declared destructive security
    • Tool “create_webhook” is now declared destructive security
    • Tool “register_github_webhook” is now declared destructive security
    • Tool “register_linear_webhook” is now declared destructive security
    • Tool “register_stripe_webhook” is now declared destructive security
    • Tool “respond_to_next_request” is now declared destructive security
    • Tool “send_requests” is now declared destructive security
    • Tool “update_request” is now declared destructive security
    • Tool “access_hosted_inbox” changed its title: Access hosted inbox cosmetic
    • Tool “check_for_callbacks” changed its title: Check for new callbacks cosmetic
    • Tool “configure_webhook” changed its title: Configure webhook inbox cosmetic
    • Tool “create_webhook” changed its title: Create webhook inbox cosmetic
    • Tool “delete_all_requests” changed its title: Delete all captured events cosmetic
    • Tool “delete_request” changed its title: Delete captured event cosmetic
    • Tool “delete_webhook” changed its title: Delete webhook inbox cosmetic
    • Tool “download_request_file” changed its title: Download captured content cosmetic
    • Tool “export_webhook_data” changed its title: Export captured events cosmetic
    • Tool “extract_links_from_request” changed its title: Extract captured links cosmetic
    • Tool “generate_oob_payloads” changed its title: Get out-of-band callback addresses cosmetic
    • Tool “get_hosted_inboxes” changed its title: List hosted inboxes cosmetic
    • Tool “get_request” changed its title: Read captured event cosmetic
    • Tool “get_webhook_activity” changed its title: Read inbox activity cosmetic
    • Tool “get_webhook_email” changed its title: Get inbox email address cosmetic
    • Tool “get_webhook_info” changed its title: Inspect webhook inbox cosmetic
    • Tool “get_webhook_requests” changed its title: List captured events cosmetic
    • Tool “register_github_webhook” changed its title: Register GitHub webhook cosmetic
    • Tool “register_linear_webhook” changed its title: Register Linear webhook cosmetic
    • Tool “register_stripe_webhook” changed its title: Register Stripe webhook cosmetic
    • Tool “respond_to_next_request” changed its title: Configure next callback response cosmetic
    • Tool “rotate_webhook_token” changed its title: Rotate inbox token cosmetic
    • Tool “search_requests” changed its title: Search captured events cosmetic
    • Tool “send_requests” changed its title: Create test events cosmetic
    • Tool “server_status” changed its title: Inspect server status cosmetic
    • Tool “unregister_webhook” changed its title: Unregister provider webhook cosmetic
    • Tool “update_request” changed its title: Annotate captured event cosmetic
    • Tool “wait_for_email” changed its title: Wait for email cosmetic
    • Tool “wait_for_request” changed its title: Wait for a callback cosmetic
  • 16 Oct 26 +1

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

  • 15 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 14 Oct 26 61

    First indexed and scored.

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 17 Oct 2026 · Probed https://openhook.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=openhook.dev CN=YR2,O=Let's Encrypt,C=US 8 Oct 2026 6 Jan 2027 RSA 4096 SHA256-RSA 680da5fc95491697b3818eaf53d25834a0a
SANs: openhook.dev
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
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 openhook.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
openhook.dev. absent 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
Header Value
content-security-policy default-src 'self'; script-src 'self'; style-src 'self'; img-src 'self' data:; connect-src 'self'; font-src 'self'; object-src 'none'; base-uri 'self'; frame-ancestors 'none'
x-content-type-options nosniff
referrer-policy no-referrer

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://openhook.dev/mcp Verified 200
http (plaintext) http://openhook.dev/mcp HTTPS enforced 301 https://openhook.dev/mcp
MCP tools · 29 exposed · ~1,263 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
access_hosted_inbox ~47

Hosted only: issue a private inbox token for an inbox you own. Keep the returned token private.

NameTypeReqDescription
account_keystringyes–
inbox_idstringyes–

No output schema declared.

No examples provided.

check_for_callbacks ~35

Check for callbacks newer than a sequence cursor without waiting.

NameTypeReqDescription
sinceinteger––
webhook_tokenstringyes–

No output schema declared.

No examples provided.

configure_webhook ~68

Set HTTP responses and optional SHA256 HMAC verification, preserving unspecified fields.

NameTypeReqDescription
cors–––
default_content–––
default_content_type–––
default_status–––
signature_provider–––
verification_secret–––
webhook_tokenstringyes–

No output schema declared.

No examples provided.

create_webhook ~57

Create an inbox. Save its private token; share only public capture addresses. A hosted Pro account_key creates a persistent owned inbox.

NameTypeReqDescription
account_keystring––
expiryinteger––
namestring––

No output schema declared.

No examples provided.

delete_all_requests ~29

Clear stored events, keeping the inbox's addresses and settings.

NameTypeReqDescription
webhook_tokenstringyes–

No output schema declared.

No examples provided.

delete_request ~34

Permanently delete one event belonging to this inbox.

NameTypeReqDescription
request_idstringyes–
webhook_tokenstringyes–

No output schema declared.

No examples provided.

delete_webhook ~27

Permanently delete this inbox and its stored events.

NameTypeReqDescription
webhook_tokenstringyes–

No output schema declared.

No examples provided.

download_request_file ~40

Retrieve exact captured bytes as base64, including binary bodies or raw MIME.

NameTypeReqDescription
request_idstringyes–
webhook_tokenstringyes–

No output schema declared.

No examples provided.

export_webhook_data ~52

Export a bounded page of full events; resume with next_since. Browser export streams the entire inbox.

NameTypeReqDescription
formatstring––
sinceinteger––
webhook_tokenstringyes–

No output schema declared.

No examples provided.

extract_links_from_request ~35

Extract HTTP links and verification codes without visiting the URLs.

NameTypeReqDescription
request_id–––
webhook_tokenstringyes–

No output schema declared.

No examples provided.

generate_oob_payloads ~29

Read callback addresses for authorized out-of-band testing.

NameTypeReqDescription
webhook_tokenstringyes–

No output schema declared.

No examples provided.

get_hosted_inboxes ~36

Hosted only: list your persistent inboxes and usage using a private account agent key.

NameTypeReqDescription
account_keystringyes–

No output schema declared.

No examples provided.

get_request ~36

Read a complete event; omit request_id to inspect the newest one.

NameTypeReqDescription
request_id–––
webhook_tokenstringyes–

No output schema declared.

No examples provided.

get_webhook_activity ~48

Read durable receipt and mutation history with a cursor. Bodies and secrets are excluded.

NameTypeReqDescription
limitinteger––
sinceinteger––
webhook_tokenstringyes–

No output schema declared.

No examples provided.

get_webhook_email ~30

Read the email address, available when this deployment runs SMTP.

NameTypeReqDescription
webhook_tokenstringyes–

No output schema declared.

No examples provided.

get_webhook_info ~31

Read addresses, expiry, response settings, and retained event count.

NameTypeReqDescription
webhook_tokenstringyes–

No output schema declared.

No examples provided.

get_webhook_requests ~55

Read events with pagination or a durable sequence cursor.

NameTypeReqDescription
limitinteger––
pageinteger––
request_type–––
sinceinteger––
webhook_tokenstringyes–

No output schema declared.

No examples provided.

register_github_webhook ~57

Create a signed GitHub repository subscription and native inbox. Requires webhook-write permission.

NameTypeReqDescription
access_tokenstringyes–
account_keystring––
eventsarrayyes–
repositorystringyes–

No output schema declared.

No examples provided.

register_linear_webhook ~59

Create a signed Linear subscription and native inbox. Requires admin scope; optional team filter.

NameTypeReqDescription
access_tokenstringyes–
account_keystring––
resource_typesarrayyes–
team_idstring––

No output schema declared.

No examples provided.

register_stripe_webhook ~50

Create a signed Stripe webhook endpoint and native inbox. Provider credentials are not stored.

NameTypeReqDescription
access_tokenstringyes–
account_keystring––
eventsarrayyes–

No output schema declared.

No examples provided.

respond_to_next_request ~69

Respond to the next request using ?openhook_wait=1, within its 20-second response window.

NameTypeReqDescription
contentstringyes–
content_typestring––
statusinteger––
timeout_secondsnumber––
webhook_tokenstringyes–

No output schema declared.

No examples provided.

rotate_webhook_token ~35

Revoke the old private token and return a new one; capture addresses stay unchanged.

NameTypeReqDescription
webhook_tokenstringyes–

No output schema declared.

No examples provided.

search_requests ~56

Search captured bodies, URLs, and headers for a literal substring.

NameTypeReqDescription
limitinteger––
pageinteger––
querystringyes–
request_type–––
webhook_tokenstringyes–

No output schema declared.

No examples provided.

send_requests ~36

Create up to ten marked test HTTP events in this inbox.

NameTypeReqDescription
payloadsarrayyes–
webhook_tokenstringyes–

No output schema declared.

No examples provided.

server_status ~19

Inspect native storage, retention, and enabled capture transports.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

unregister_webhook ~39

Remove the registered provider subscription and permanently delete its native inbox and events.

NameTypeReqDescription
access_tokenstringyes–
webhook_tokenstringyes–

No output schema declared.

No examples provided.

update_request ~42

Annotate an event without changing its original captured body.

NameTypeReqDescription
notestringyes–
request_idstringyes–
webhook_tokenstringyes–

No output schema declared.

No examples provided.

wait_for_email ~50

Wait for an email received by Openhook's SMTP listener.

NameTypeReqDescription
return_existingboolean––
since–––
timeout_secondsnumber––
webhook_tokenstringyes–

No output schema declared.

No examples provided.

wait_for_request ~62

Wait up to 120 seconds; pass next_since when reconnecting to avoid missing events.

NameTypeReqDescription
request_type–––
return_existingboolean––
since–––
timeout_secondsnumber––
webhook_tokenstringyes–

No output schema declared.

No examples provided.

Install

How do I install the Openhook MCP server?

Openhook is a hosted endpoint at https://openhook.dev/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 · openhook.dev

# add to Claude Code
claude mcp add --transport http openhook-dev-openhook-inbox 'https://openhook.dev/mcp'
Common questions

What is the Openhook MCP server?

Openhook is an MCP server listed in the public MCP registry as io.github.openhook-dev/openhook-inbox. Webhook, email and DNS inboxes for AI agents to capture callbacks and test integrations. This page covers its hosted endpoint (https://openhook.dev/mcp).

Is the Openhook MCP server safe to use?

Openhook scores 62 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 Openhook MCP server expose?

Openhook exposes 29 tools: server_status, create_webhook, get_hosted_inboxes, access_hosted_inbox, configure_webhook, and 24 more. Their descriptions and schemas cost roughly 1,263 tokens of context every time the server is loaded.

Does the Openhook MCP server require authentication?

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

Is the Openhook MCP server still maintained?

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