io.github.useotterkit/otterkit
NPM · OTTERKIT · SCANNED SEP 20
Tunnels and webhooks for AI agents: capture, await, verify, replay, and send signed test events.
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 99 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 37 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
- Context-footprint check failed: tool/resource definitions use about 1404 tokens (~127/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 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
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; "event_send" implies "send" 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 11 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.useotterkit/otterkit MCP server?
io.github.useotterkit/otterkit runs locally as an npm package, launched with npx -y otterkit. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · otterkit
claude mcp add useotterkit-otterkit -- npx -y otterkit
{
"mcpServers": {
"useotterkit-otterkit": {
"command": "npx",
"args": [
"-y",
"otterkit"
]
}
}
} {
"servers": {
"useotterkit-otterkit": {
"command": "npx",
"args": [
"-y",
"otterkit"
]
}
}
} codex mcp add useotterkit-otterkit -- npx -y otterkit
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"useotterkit-otterkit": {
"type": "local",
"command": [
"npx",
"-y",
"otterkit"
],
"enabled": true
}
}
} openclaw mcp add useotterkit-otterkit --command npx --arg -y --arg otterkit
mcp_servers:
useotterkit-otterkit:
command: "npx"
args: ["-y", "otterkit"] {
"McpServers": {
"useotterkit-otterkit": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"otterkit"
]
}
}
} assistant mcp add useotterkit-otterkit -t stdio -c npx -a -y otterkit
{
"mcpServers": {
"useotterkit-otterkit": {
"command": "npx",
"args": [
"-y",
"otterkit"
]
}
}
} 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.
- 19 Sept 26 −3
- Stability: pass → 0.80 functional
- 18 Sept 26 +1
- Stability: 0.97 → pass security
- 17 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 16 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 14 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.
- 12 Sept 26 −3
- Stability: pass → 0.80 functional
- 11 Sept 26 +1
- Stability: 0.97 → pass security
- 10 Sept 26 0
- Security disclosure: unverified → fail ▼ 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 20 Sept 2026 · Analysed npm/otterkit@0.12.2
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 99 packages
| Packages resolved | 99 |
|---|---|
| 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 →
account_status Account and credit balance ~34
Show the logged-in OtterKit account and prepaid credit balance (1 credit = $0.01 = 1 tunnel hour).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
event_send Send a synthetic signed provider event ~185
Fire a correctly-signed synthetic webhook event (Stripe, GitHub, Shopify, Slack) at a local handler — develop and test a webhook handler with NO provider account, dashboard, or real event needed. Pass the signing secret and the handler will pass its signature verification. Omit event/target and pass list=true to see available events. Fully local, no credits.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | Override the generated payload with raw JSON |
| event | string | – | provider:event, e.g. "stripe:payment_intent.succeeded" or "github:push" |
| list | boolean | – | List available providers and events instead of sending |
| secret | string | – | Signing secret — signs the event so the handler's verification passes |
| target | string | – | Local handler, e.g. "127.0.0.1:3000/webhooks/stripe" |
No output schema declared.
No examples provided.
request_await Wait for a request to arrive ~142
Block until a request matching the filters arrives on a capture log, then return it. The perfect assertion step: trigger an event, await its arrival, inspect the payload. Only matches NEW requests from the moment of the call. The session keeps running afterwards.
| Name | Type | Req | Description |
|---|---|---|---|
| method | string | – | Only match this HTTP method |
| path | string | – | Only match paths containing this substring |
| status | string | – | Only match this response status (e.g. 200 or 2xx) |
| subdomain | string | yes | Session subdomain to watch |
| timeoutSeconds | integer | – | Give up after this many seconds (default 60, max 300) |
No output schema declared.
No examples provided.
request_replay Replay a captured request ~235
Re-send a captured request to a local target (no tunnel round-trip, no credits). Optionally override method/path/headers/body or edit individual JSON body fields via set (e.g. ["data.amount=999"]). The exchange is appended to the capture log.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | Replace the request body |
| headers | array | – | Override/add headers, each "Key: value" |
| index | integer | – | Which request: 1 = oldest, -1 = latest (default -1) |
| method | string | – | Override the HTTP method |
| path | string | – | Override the request path |
| resign | string | – | Re-sign the edited body with this provider scheme (needs secret) so the handler still accepts it |
| secret | string | – | Signing secret for resign |
| set | array | – | Edit JSON body fields before sending, each "path=value" e.g. "data.amount=999" |
| subdomain | string | yes | Session whose capture log to replay from |
| target | string | – | host:port to send to (defaults to the running tunnel daemon's target) |
No output schema declared.
No examples provided.
request_verify Verify captured request signatures ~110
Check whether captured requests carry a valid provider signature for the given secret — answers "is my signature-verification code wrong, or is the payload wrong?". Returns per-request valid/invalid with the reason. Fully local; the secret never leaves the machine.
| Name | Type | Req | Description |
|---|---|---|---|
| last | integer | – | Verify the last N requests (default 20) |
| provider | string | yes | Signature scheme |
| secret | string | yes | The signing secret to verify against |
| subdomain | string | yes | Session whose captured requests to verify |
No output schema declared.
No examples provided.
requests_list List captured requests ~104
Read requests captured on a webhook or tunnel(capture=true) session, newest last. Bodies are decoded when printable. Filters combine.
| Name | Type | Req | Description |
|---|---|---|---|
| last | integer | – | Max entries to return (default 20) |
| method | string | – | Only this HTTP method |
| path | string | – | Only paths containing this substring |
| status | string | – | Only this response status (e.g. 500 or 5xx) |
| subdomain | string | yes | Session subdomain |
No output schema declared.
No examples provided.
session_stop Stop a session ~49
Stop a running tunnel/webhook daemon. The capture log is kept on disk so requests_list and request_replay still work afterwards.
| Name | Type | Req | Description |
|---|---|---|---|
| subdomain | string | yes | Subdomain of the daemon to stop |
No output schema declared.
No examples provided.
sessions_list List running sessions ~22
List running OtterKit tunnel/webhook daemons on this machine.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
try_claim Claim an otterkit.com/try session ~144
Continue a session started on the otterkit.com/try page: same public URL, converted to a normal metered webhook session on this account. Captures from the page are imported into the local log. The claim code comes from the /try page ("subdomain:secret"). Note: this registers the session for capture but a live connection requires `otterkit webhook --claim` in a terminal; prefer webhook_create unless continuing a /try session specifically.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Claim code from the /try page, "try-xxxx:secret" |
| ttl | string | – | Auto-stop TTL, e.g. 4h (default 24h) |
No output schema declared.
No examples provided.
tunnel_create Create tunnel to localhost ~179
Expose a local port on a public URL (https://<subdomain>.otterkit.app). Runs as a background daemon. Costs 1 credit per connected hour (max 10/day). Set capture=true to also log every request for requests_list/request_await/request_replay.
| Name | Type | Req | Description |
|---|---|---|---|
| auth | string | – | Require HTTP Basic auth as "user:pass" (enforced locally, never sent to servers) |
| capture | boolean | – | Also capture requests to the local log |
| host | string | – | Local host (default 127.0.0.1) |
| port | integer | yes | Local port to forward to |
| subdomain | string | – | Stable reserved subdomain |
| ttl | string | – | Auto-stop after e.g. 4h, 3d (default 24h, max 7d) |
No output schema declared.
No examples provided.
webhook_create Create webhook endpoint ~200
Provision a public webhook capture endpoint (https://<subdomain>.otterkit.app). Runs as a background daemon; every request is captured to a local log readable with requests_list/request_await. Costs 1 credit per connected hour (max 10/day). Returns the public URL.
| Name | Type | Req | Description |
|---|---|---|---|
| respond | integer | – | Auto-response HTTP status (default 200) |
| respondBody | string | – | Auto-response body (default {"received":true}) |
| standby | boolean | – | Keep the endpoint live if the daemon dies or disconnects: the server serves the auto-response itself and buffers requests (up to 200), replaying them into the log on reconnect. Billing continues whil… |
| subdomain | string | – | Stable reserved subdomain (claimed to the account on first use) |
| ttl | string | – | Auto-stop after e.g. 45m, 4h, 3d (default 24h, max 7d) |
No output schema declared.
No examples provided.
What is the io.github.useotterkit/otterkit MCP server?
io.github.useotterkit/otterkit is an MCP server listed in the public MCP registry as io.github.useotterkit/otterkit. Tunnels and webhooks for AI agents: capture, await, verify, replay, and send signed test events. This page covers its npm package (otterkit).
Is the io.github.useotterkit/otterkit MCP server safe to use?
io.github.useotterkit/otterkit scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 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.useotterkit/otterkit MCP server expose?
io.github.useotterkit/otterkit exposes 11 tools: webhook_create, tunnel_create, sessions_list, session_stop, requests_list, and 6 more. Their descriptions and schemas cost roughly 1,404 tokens of context every time the server is loaded.
Is the io.github.useotterkit/otterkit MCP server still maintained?
io.github.useotterkit/otterkit is still listed as active in the MCP registry. We last reached this channel on 20 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.useotterkit/otterkit MCP server under?
io.github.useotterkit/otterkit declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.