io.github.ozers/hooksense
NPM · @HOOKSENSE/MCP · SCANNED AUG 3
Webhook & callback layer for AI agents: create a URL, wait_for_callback, and verify over MCP.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security36
- Malware scan not yet available for this package.Unverified
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 39 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 743 tokens (~92/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @hooksense/mcp
claude mcp add ozers-hooksense -- npx -y @hooksense/mcp
codex mcp add ozers-hooksense -- npx -y @hooksense/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ozers-hooksense": {
"type": "local",
"command": [
"npx",
"-y",
"@hooksense/mcp"
],
"enabled": true
}
}
} openclaw mcp add ozers-hooksense --command npx --arg -y --arg @hooksense/mcp
mcp_servers:
ozers-hooksense:
command: "npx"
args: ["-y", "@hooksense/mcp"] {
"mcpServers": {
"ozers-hooksense": {
"command": "npx",
"args": [
"-y",
"@hooksense/mcp"
]
}
}
} 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.
- 3 Aug 26 +4
- Stability: unverified → 0.23 ▲ functional
- 2 Aug 26 +45
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Schema quality: unverified → excellent ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Licence: MIT functional
- 1 Aug 26 −23
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +22
- Tool coverage: unverified → 100 ▲ functional
- 28 Jul 26 −22
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 27 Jul 26 28
First indexed and scored.
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 3 Aug 2026 · Analysed npm/@hooksense/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 94 packages
94 packages in the resolved dependency tree · 94 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
create_callback_endpoint ~103
Create a callback endpoint and return its URL. Hand this URL to a long-running/async job (or another agent) as its webhook/callback target, then await the result with wait_for_callback. Also works as a plain webhook capture URL for any provider (Stripe, GitHub, …).
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | — | Optional human-readable slug (3-32 chars, letters/numbers/hyphens). Requires Hook plan or above. Auto-generated if omitted. |
No output schema declared.
No examples provided.
get_callback_payload ~65
Fetch a single received callback with full headers, decrypted body, and metadata. Use this to read the result of an async job after wait_for_callback or list_callbacks gives you a callback id.
| Name | Type | Req | Description |
|---|---|---|---|
| requestId | string | yes | Callback UUID, from wait_for_callback or list_callbacks |
No output schema declared.
No examples provided.
get_endpoint ~37
Get details about a specific endpoint — its full URL, signature provider config, and custom response settings.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Endpoint slug |
No output schema declared.
No examples provided.
list_callbacks ~105
List callbacks received by an endpoint, newest first. Returns a summary (method, status, provider, received_at). Use `get_callback_payload` for the full body. Tip: read the newest `received_at` and pass it as `after` to wait_for_callback to wait only for what comes next.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | — | Max callbacks to return (1-100, default 20) |
| slug | string | yes | Endpoint slug (e.g. 'stripe-prod') |
No output schema declared.
No examples provided.
list_endpoints ~29
List all webhook endpoints owned by the authenticated user. Returns slug, created_at, and request counts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
replay_callback ~87
Replay a received callback to a target URL. The original headers and body are re-sent unchanged — useful to re-drive your handler against a known payload without re-triggering the upstream event.
| Name | Type | Req | Description |
|---|---|---|---|
| requestId | string | yes | Callback UUID to replay |
| targetUrl | string | yes | Where to POST the replayed payload (e.g. http://localhost:3000/webhooks/stripe) |
No output schema declared.
No examples provided.
verify_signature ~100
Verify the HMAC signature of a received callback against the endpoint's configured secret (Stripe, GitHub, Shopify, or custom), using a timing-safe comparison. Returns whether the callback is authentic and untampered — call this before your agent acts on a payload. Requires the endpoint to have a webhook secret configured and a paid plan.
| Name | Type | Req | Description |
|---|---|---|---|
| requestId | string | yes | Callback UUID to verify |
| slug | string | yes | Endpoint slug the callback belongs to |
No output schema declared.
No examples provided.
wait_for_callback ~217
Block until the next webhook (callback) arrives at an endpoint, then return it — instead of polling. Use this for async/long-running work: kick off the job with the endpoint URL as its callback, then call wait_for_callback to receive the result the moment it lands (signature-verified, decrypted). Returns { status: 'received', request } on delivery, or { status: 'pending' } if `timeoutMs` elapses first (just call again to keep waiting). Pass `after` (the receivedAt of the last callback you saw) so a callback that arrived between calls is returned immediately rather than missed.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | — | Optional ISO timestamp cursor. Any callback received after this is returned immediately without blocking — pass the previous callback's receivedAt to avoid missing one between calls. |
| slug | string | yes | Endpoint slug to wait on (from create_callback_endpoint) |
| timeoutMs | number | — | How long to block before returning 'pending' (1000–60000, default 30000). |
No output schema declared.
No examples provided.