Is the Comiza Hookjar MCP server down?

mcp-registry/lighting.comiza/hookjar · v1.0.0

As of 2026-10-24 20:28 UTC, the Comiza Hookjar MCP server is up with a Glimind reliability score of 83/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 7 outages in 90 days, with a median recovery of 7 minutes.

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

claude mcp add --transport http comiza-hookjar-mcp-server https://comiza.lighting/mcp

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

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: D (69/100)

What to fix (4)

Auto-fix: 5 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 4 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Flighting.comiza%2Fhookjar/fixes

{
  "name": "create_inbox",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "label": {
        "type": "string",
        "description": "Optional note to yourself, for example 'stripe test'."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "Create a webhook inbox"
}

{
  "name": "delete_inbox",
  "description": "Delete an inbox and everything captured in it.",
  "inputSchema": {
    "type": "object",
    "required": [
      "inbox_id"
    ],
    "properties": {
      "inbox_id": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": true,
    "idempotentHint": true
  },
  "title": "Delete an inbox"
}

{
  "name": "get_request",
  "description": "Return the full method, headers, query string and body of a single captured request. Text bodies come back as text, binary as base64.",
  "inputSchema": {
    "type": "object",
    "required": [
      "request_id"
    ],
    "properties": {
      "request_id": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Read one captured request"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/lighting.comiza/hookjar"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/lighting.comiza/hookjar"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~587 tokens).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 99.73% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• wait_for_request ~175 tokens
• create_inbox ~143 tokens
• get_requests ~98 tokens
• get_request ~77 tokens
• delete_inbox ~52 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Flighting.comiza%2Fhookjar.svg)](https://glimind.com/server/mcp-registry%2Flighting.comiza%2Fhookjar?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Flighting.comiza%2Fhookjar?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Flighting.comiza%2Fhookjar.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Flighting.comiza%2Fhookjar.svg
   :target: https://glimind.com/server/mcp-registry%2Flighting.comiza%2Fhookjar?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:5ec0682e1764a2de…, first seen 2026-10-17, included at leaf 3642 of 61,076. Version history · verify what your client received.

Tools (6)

• create_inbox
• delete_inbox
• get_request
• get_requests
• list_inboxes
• wait_for_request

Compare: most reliable web servers · most reliable communication servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Comiza Hookjar MCP server down right now?

As of 2026-10-24 20:28 UTC, the Comiza Hookjar MCP server is up with a Glimind reliability score of 83/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 7 outages in 90 days, with a median recovery of 7 minutes.

How many tools does Comiza Hookjar MCP server provide?

Comiza Hookjar MCP server advertises 6 tools, including create_inbox, delete_inbox, get_request, get_requests, list_inboxes.

How do I install Comiza Hookjar MCP server?

Point your MCP client at this streamable-http endpoint: https://comiza.lighting/mcp

Is the Comiza Hookjar MCP server safe to connect to an AI agent?

Glimind scanned all 6 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Comiza Hookjar MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.