# Hookjar (remote · comiza.lighting)

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

- Trust score: 75/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- remote · `comiza.lighting`: 75/100 (this document), [markdown](https://verifymcp.io/servers/lighting-comiza-hookjar/comiza.md), [page](https://verifymcp.io/servers/lighting-comiza-hookjar/comiza)

## Channel facts

- Endpoint: `https://comiza.lighting/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-25.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 395 tokens (~65/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 78/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 33% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_inbox" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Hookjar MCP server?

Hookjar is a hosted endpoint at https://comiza.lighting/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.

### Claude

```bash
claude mcp add --transport http lighting-comiza-hookjar 'https://comiza.lighting/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "lighting-comiza-hookjar": {
      "url": "https://comiza.lighting/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "lighting-comiza-hookjar": {
      "type": "http",
      "url": "https://comiza.lighting/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.lighting-comiza-hookjar]
url = "https://comiza.lighting/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lighting-comiza-hookjar": {
      "type": "remote",
      "url": "https://comiza.lighting/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add lighting-comiza-hookjar --url 'https://comiza.lighting/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  lighting-comiza-hookjar:
    url: "https://comiza.lighting/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "lighting-comiza-hookjar": {
      "Transport": "http",
      "Url": "https://comiza.lighting/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add lighting-comiza-hookjar -t streamable-http -u 'https://comiza.lighting/mcp'
```

### Other

```json
{
  "mcpServers": {
    "lighting-comiza-hookjar": {
      "type": "http",
      "url": "https://comiza.lighting/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 75, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-08 (score 75, 0)

- [security] Stability: 0.97 → pass

### 2026-09-07 (score 75, +1)

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

### 2026-09-04 (score 74, +1)

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

### 2026-09-02 (score 73, +1)

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

### 2026-08-31 (score 72, +1)

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

### 2026-08-29 (score 71, +1)

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

### 2026-08-26 (score 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (6)

### `create_inbox` (~92 tokens)

Create a webhook inbox

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.

Input parameters:

- `label` (string): Optional note to yourself, for example 'stripe test'.

### `list_inboxes` (~23 tokens)

List your inboxes

List the inboxes you currently own, with their URLs and expiry.

### `wait_for_request` (~103 tokens)

Wait for a request to arrive

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.

Input parameters:

- `after_seq` (integer): Return only requests newer than this sequence number. Use 0 the first time.
- `inbox_id` (string, required)
- `timeout_seconds` (integer): How long to wait. Capped by your tier.

### `get_requests` (~57 tokens)

List captured requests

List what has arrived in an inbox, newest last. Returns summaries without bodies. Use get_request for the full contents of one.

Input parameters:

- `after_seq` (integer)
- `inbox_id` (string, required)
- `limit` (integer)

### `get_request` (~45 tokens)

Read one captured request

Return the full method, headers, query string and body of a single captured request. Text bodies come back as text, binary as base64.

Input parameters:

- `request_id` (string, required)

### `delete_inbox` (~26 tokens)

Delete an inbox

Delete an inbox and everything captured in it.

Input parameters:

- `inbox_id` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/lighting-comiza-hookjar/comiza#diagnostics

## Score history

- 2026-09-25: 75
- 2026-09-24: 75
- 2026-09-23: 75
- 2026-09-22: 75
- 2026-09-21: 75
- 2026-09-20: 75
- 2026-09-19: 75
- 2026-09-18: 75
- 2026-09-17: 75
- 2026-09-16: 75
- 2026-09-15: 75
- 2026-09-14: 75
- 2026-09-13: 75
- 2026-09-12: 75
- 2026-09-11: 75
- 2026-09-10: 75
- 2026-09-09: 75
- 2026-09-08: 75
- 2026-09-07: 75
- 2026-09-06: 74
- 2026-09-05: 74
- 2026-09-04: 74
- 2026-09-03: 73
- 2026-09-02: 73
- 2026-09-01: 72
- 2026-08-31: 72
- 2026-08-30: 71
- 2026-08-29: 71
- 2026-08-28: 70
- 2026-08-27: 70

## Common questions

### What is the Hookjar MCP server?

Hookjar is an MCP server listed in the public MCP registry as lighting.comiza/hookjar. Public webhook inboxes for agents. Receive OAuth redirects, payment callbacks and CI notifications. This page covers its hosted endpoint (https://comiza.lighting/mcp).

### Is the Hookjar MCP server safe to use?

Hookjar scores 75 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 Hookjar MCP server expose?

Hookjar exposes 6 tools: create_inbox, list_inboxes, wait_for_request, get_requests, get_request, delete_inbox. Their descriptions and schemas cost roughly 346 tokens of context every time the server is loaded.

### Does the Hookjar MCP server require authentication?

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

### Is the Hookjar MCP server still maintained?

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

## Links

- Remote endpoint: https://comiza.lighting/mcp
- Website: https://comiza.lighting/hookjar/
- Changelog RSS feed: https://verifymcp.io/servers/lighting-comiza-hookjar/comiza.xml
- Changelog JSON feed: https://verifymcp.io/servers/lighting-comiza-hookjar/comiza.json
- HTML version of this page: https://verifymcp.io/servers/lighting-comiza-hookjar/comiza