Home / MCP registry index / io.github.openhook-dev/openhook-inbox

Openhook

io.github.openhook-dev/openhook-inbox in the official MCP registry. Endpoint https://openhook.dev/mcp. Source: github.com/openhook-dev/openhook-inbox.

The registry describes it as: Webhook, email and DNS inboxes for AI agents to capture callbacks and test integrations.

We read its 39 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http openhook-inbox https://openhook.dev/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "openhook-inbox": {
      "url": "https://openhook.dev/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"openhook-inbox","type":"http","url":"https://openhook.dev/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

server_status create_webhook get_hosted_inboxes access_hosted_inbox configure_webhook get_webhook_info get_webhook_email register_github_webhook register_stripe_webhook register_linear_webhook unregister_webhook delete_webhook rotate_webhook_token get_webhook_requests get_webhook_activity search_requests get_request update_request download_request_file delete_request delete_all_requests export_webhook_data wait_for_request wait_for_email send_requests extract_links_from_request generate_oob_payloads check_for_callbacks respond_to_next_request create_agent_session invite_agent_participant join_agent_session get_agent_session revoke_agent_participant send_agent_message read_agent_messages close_agent_session create_agent_channel manage_agent_channel

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-openhook-dev-openhook-inbox/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-openhook-dev-openhook-inbox)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Email MCP servers