io.github.ozers/hooksense
NPM · @HOOKSENSE/MCP · SCANNED SEP 29
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 → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 92 dependencies flagged as unhealthy. 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 96 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability82
- 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.ozers/hooksense MCP server?
io.github.ozers/hooksense runs locally as an npm package, launched with npx -y @hooksense/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @hooksense/mcp
claude mcp add ozers-hooksense -- npx -y @hooksense/mcp
{
"mcpServers": {
"ozers-hooksense": {
"command": "npx",
"args": [
"-y",
"@hooksense/mcp"
]
}
}
} {
"servers": {
"ozers-hooksense": {
"command": "npx",
"args": [
"-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": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@hooksense/mcp"
]
}
}
} assistant mcp add ozers-hooksense -t stdio -c npx -a -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.
- 29 Sept 26 0
- Stability: 0.97 → pass security
- Security disclosure: fail → unverified ▼ functional
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 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
- 24 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 23 Sept 26 +12
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.80 functional
- 22 Sept 26 0
- Stability: 0.97 → pass security
- 21 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.
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 29 Sept 2026 · Analysed npm/@hooksense/mcp@0.2.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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_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.
What is the io.github.ozers/hooksense MCP server?
io.github.ozers/hooksense is an MCP server listed in the public MCP registry as io.github.ozers/hooksense. Webhook & callback layer for AI agents: create a URL, wait_for_callback, and verify over MCP. This page covers its npm package (@hooksense/mcp).
Is the io.github.ozers/hooksense MCP server safe to use?
io.github.ozers/hooksense scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 29 September 2026. It declares no install or post-install scripts. 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 io.github.ozers/hooksense MCP server expose?
io.github.ozers/hooksense exposes 8 tools: list_endpoints, create_callback_endpoint, list_callbacks, get_callback_payload, verify_signature, and 3 more. Their descriptions and schemas cost roughly 743 tokens of context every time the server is loaded.
Is the io.github.ozers/hooksense MCP server still maintained?
io.github.ozers/hooksense is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.ozers/hooksense MCP server under?
io.github.ozers/hooksense declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.