Hookjar
REMOTE · COMIZA.LIGHTING · SCANNED SEP 25
Public webhook inboxes for agents. Receive OAuth redirects, payment callbacks and CI notifications.
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 395 tokens (~65/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage78
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 33% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 7 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
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.
remote · comiza.lighting
claude mcp add --transport http lighting-comiza-hookjar 'https://comiza.lighting/mcp'
{
"mcpServers": {
"lighting-comiza-hookjar": {
"url": "https://comiza.lighting/mcp"
}
}
} {
"servers": {
"lighting-comiza-hookjar": {
"type": "http",
"url": "https://comiza.lighting/mcp"
}
}
} [mcp_servers.lighting-comiza-hookjar] url = "https://comiza.lighting/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"lighting-comiza-hookjar": {
"type": "remote",
"url": "https://comiza.lighting/mcp",
"enabled": true
}
}
} openclaw mcp add lighting-comiza-hookjar --url 'https://comiza.lighting/mcp' --transport streamable-http
mcp_servers:
lighting-comiza-hookjar:
url: "https://comiza.lighting/mcp" {
"McpServers": {
"lighting-comiza-hookjar": {
"Transport": "http",
"Url": "https://comiza.lighting/mcp"
}
}
} assistant mcp add lighting-comiza-hookjar -t streamable-http -u 'https://comiza.lighting/mcp'
{
"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.
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.
- 25 Sept 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
- 8 Sept 26 0
- Stability: 0.97 → pass security
- 7 Sept 26 +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.
- 4 Sept 26 +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.
- 2 Sept 26 +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.
- 31 Aug 26 +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.
- 29 Aug 26 +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.
- 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
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 25 Sept 2026 · Probed https://comiza.lighting/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=comiza.lighting | CN=YE2,O=Let's Encrypt,C=US | 14 Sept 2026 | 13 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6066de606113beed9e68fbf77bec8325d60 |
| SANs: comiza.lighting, www.comiza.lighting | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of comiza.lighting. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| lighting. | present | 55696 | 8 | Verified |
| comiza.lighting. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://comiza.lighting/mcp | Verified | 200 | |
| http (plaintext) | http://comiza.lighting/mcp | HTTPS enforced | 301 | https://comiza.lighting/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 →
create_inbox Create a webhook inbox ~92
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.
| Name | Type | Req | Description |
|---|---|---|---|
| label | string | – | Optional note to yourself, for example 'stripe test'. |
No output schema declared.
No examples provided.
delete_inbox Delete an inbox ~26
Delete an inbox and everything captured in it.
| Name | Type | Req | Description |
|---|---|---|---|
| inbox_id | string | yes | – |
No output schema declared.
No examples provided.
get_request Read one captured request ~45
Return the full method, headers, query string and body of a single captured request. Text bodies come back as text, binary as base64.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | string | yes | – |
No output schema declared.
No examples provided.
get_requests List captured requests ~57
List what has arrived in an inbox, newest last. Returns summaries without bodies. Use get_request for the full contents of one.
| Name | Type | Req | Description |
|---|---|---|---|
| after_seq | integer | – | – |
| inbox_id | string | yes | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
list_inboxes List your inboxes ~23
List the inboxes you currently own, with their URLs and expiry.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
wait_for_request Wait for a request to arrive ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| after_seq | integer | – | Return only requests newer than this sequence number. Use 0 the first time. |
| inbox_id | string | yes | – |
| timeout_seconds | integer | – | How long to wait. Capped by your tier. |
No output schema declared.
No examples provided.
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.