Skip to content

Hookjar MCP server

lighting.comiza/hookjarcomiza.lightingstreamable-httpv1.0.0Scanned

Public webhook inboxes for agents. Receive OAuth redirects, payment callbacks and CI notifications.

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

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

Tools listed without sign-in. Remote posture

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

What the Hookjar MCP server can do

The Hookjar MCP server is published by comiza.lighting, 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 (1 tool: create_inbox). 4 tools only read.

3 tools read private data (list_inboxes, wait_for_request and get_requests); 3 tools bring in text other people can write (list_inboxes, wait_for_request and get_requests).

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

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 18, 2026, version 1.0.0.

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 everything captured in it.No findings

    Why it is in this group

    • The name "delete_inbox" says "delete": a word for removing or ending something.
    Description, as the server wrote it
    Delete an inbox and everything captured in it.
Changes things 1Claude Code: ask
  • create_inboxCreate a public URL that captures any HTTP request sent to it.No findings

    Why it is in this group

    • The name "create_inbox" says "create": a word for a change.
    Description, as the server wrote it
    Create a public URL that captures any HTTP request sent to it. Use it when you need something outside this session to reach you: an OAuth redirect, a payment provider callback, a CI notification, a webhook you are testing. Returns the URL to hand to the other service. Requests are readable with get_requests or wait_for_request.
Only reads 4Show 4 read-only tools
  • get_requestReturn the full method, headers, query string and body of a single captured request.No findings

    Why it is in this group

    • The name "get_request" says "get": a word for reading.
    Description, as the server wrote it
    Return the full method, headers, query string and body of a single captured request. Text bodies come back as text, binary as base64.
  • get_requestsList what has arrived in an inbox, newest last.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_requests" says "get": 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 what has arrived in an inbox, newest last. Returns summaries without bodies. Use get_request for the full contents of one.
  • list_inboxesList the inboxes you currently own, with their URLs and expiry.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "list_inboxes" says "list": a word for reading.

    What it can reach

    • private-dataThe name "list_inboxes" says "list" and "inbox": it reads mail.
    • private-dataThe description's first sentence says "list" and "inbox": it reads mail.
    • untrusted-inputThe name "list_inboxes" says "list" and "inbox": it reads inbound email, which other people can write.
    • 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 the inboxes you currently own, with their URLs and expiry.
  • wait_for_requestBlock until a request lands in the inbox, then return it.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "wait_for_request" says "wait": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "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 "inbox": it reads inbound email, which other people can write.
    Description, as the server wrote it
    Block until a request lands in the inbox, then return it. This is the tool to use straight after you have triggered the action that should produce the callback. Returns immediately if something already arrived after the sequence number you pass.

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.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:15 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (1 destructive, 1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://comiza.lighting/mcp: tools/list returned 6 tools to an anonymous client, including delete_inbox (destructive), create_inbox (write)

    What this check looks for

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.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http hookjar https://comiza.lighting/mcp
claude mcp add --transport http hookjar https://comiza.lighting/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__hookjar__list_inboxes",
      "mcp__hookjar__wait_for_request",
      "mcp__hookjar__get_requests",
      "mcp__hookjar__get_request"
    ],
    "ask": [
      "mcp__hookjar__create_inbox"
    ],
    "deny": [
      "mcp__hookjar__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 hookjar. Review it before you use it.

Capability tags behind 3 rules
  • mcp__hookjar__list_inboxes private-data, untrusted-input
  • mcp__hookjar__wait_for_request private-data, untrusted-input
  • mcp__hookjar__get_requests private-data, untrusted-input

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://radar.anlyon.com/api/v1/servers/lighting.comiza/hookjar/verify?hash=24c2d32058234f556eee9bb95ee522c263bbebacd9b8c6a9d400fd8b493c2b49" | jq -e '.changed == false'

Pinned hash 24c2d3205823, from Nov 18, 2026, 17:18 UTC.

Watch

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

https://radar.anlyon.com/servers/lighting.comiza/hookjar/changes.xml

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

Badge

Anlyon Radar badge for lighting.comiza/hookjar
[![Anlyon Radar](https://radar.anlyon.com/badge/lighting.comiza/hookjar.svg)](https://radar.anlyon.com/servers/lighting.comiza/hookjar)

Source: MCP Registry. Synced Oct 21, 2026, 18:53 UTC.

Hookjar MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Hookjar MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 2 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 Hookjar MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: delete_inbox.

Can the Hookjar 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 Hookjar MCP server have?

6 tools: 1 destructive, 1 write, 4 read. delete_inbox, create_inbox, list_inboxes, wait_for_request, get_requests and get_request.

Does the Hookjar MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Hookjar MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Hookjar MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.