RoutineKit
NPM · ROUTINEKIT · SCANNED SEP 25
Capture tool workflows, save typed tools, and replay with human approval. Includes an MCP Apps UI.
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 20 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability48
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 757 tokens (~44/item across 17 items; 16 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage75
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 24% 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; "routine_web_call" implies "execute" 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 18 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
- Supports UI / widget rendering.Pass
How do I install the RoutineKit MCP server?
RoutineKit runs locally as an npm package, launched with npx -y routinekit. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · routinekit
claude mcp add sjh9714-routinekit -- npx -y routinekit
{
"mcpServers": {
"sjh9714-routinekit": {
"command": "npx",
"args": [
"-y",
"routinekit"
]
}
}
} {
"servers": {
"sjh9714-routinekit": {
"command": "npx",
"args": [
"-y",
"routinekit"
]
}
}
} codex mcp add sjh9714-routinekit -- npx -y routinekit
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sjh9714-routinekit": {
"type": "local",
"command": [
"npx",
"-y",
"routinekit"
],
"enabled": true
}
}
} openclaw mcp add sjh9714-routinekit --command npx --arg -y --arg routinekit
mcp_servers:
sjh9714-routinekit:
command: "npx"
args: ["-y", "routinekit"] {
"McpServers": {
"sjh9714-routinekit": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"routinekit"
]
}
}
} assistant mcp add sjh9714-routinekit -t stdio -c npx -a -y routinekit
{
"mcpServers": {
"sjh9714-routinekit": {
"command": "npx",
"args": [
"-y",
"routinekit"
]
}
}
} 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 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +3
- Stability: unverified → 0.23 ▲ functional
- 6 Sept 26 +15
- Malware scan: unverified → pass ▲ security
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 · Analysed npm/routinekit@0.2.0
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 →
routine_discard ~22
Discard the current in-memory recording. Saved routines are preserved.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
routine_export ~44
Export one saved routine as a ZIP containing SKILL.md and routine.json. Recheck private literals before sharing. No credentials or permissions are bundled.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
routine_import ~37
Review and import portable routine JSON into local storage. Requires human approval. Never overwrites an existing routine.
| Name | Type | Req | Description |
|---|---|---|---|
| routine_json | string | yes | – |
No output schema declared.
No examples provided.
routine_inspect ~34
Read one saved routine, including its inputs, origin contracts, bindings, and success checks.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
routine_list ~21
List saved routines and current capture/replay state. No execution.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
routine_mcp_call ~53
Call one allowlisted connected MCP tool with human approval. Selected successful calls are recorded.
| Name | Type | Req | Description |
|---|---|---|---|
| arguments_json | string | yes | – |
| name | string | yes | Exact mcp:alias:tool name from routine_tools. |
No output schema declared.
No examples provided.
routine_mcp_connect ~41
Review and start one explicitly configured local MCP server. No automatic software installation, existing host configuration import, or credential transfer.
| Name | Type | Req | Description |
|---|---|---|---|
| server | string | yes | – |
No output schema declared.
No examples provided.
routine_preview ~63
Preview the executable routine without saving. Use checks to verify task success, not just output shape.
| Name | Type | Req | Description |
|---|---|---|---|
| checks_json | string | – | Optional JSON array: [{"step":"step_2","path":"/opened","equals":true}] or a check with "input":"category". |
No output schema declared.
No examples provided.
routine_record ~77
Begin opt-in, task-local capture of a successful linear workflow. Inputs are exact example argument values, not a natural-language goal. Human approval is required.
| Name | Type | Req | Description |
|---|---|---|---|
| inputs_json | string | yes | JSON object of named example scalar inputs, e.g. {"category":"notes"}. |
| name | string | yes | – |
| tools | array | yes | – |
No output schema declared.
No examples provided.
routine_run ~57
Replay a reviewed routine with new input values, using live tools and existing host permissions. Requires fresh human approval; stop on mismatch. The replay engine makes no model calls.
| Name | Type | Req | Description |
|---|---|---|---|
| inputs_json | string | yes | – |
| name | string | yes | – |
No output schema declared.
No examples provided.
routine_save ~53
Show the exact routine to the user, then save only if approved. Set expose to make this a named tool with typed inputs. Does not replay.
| Name | Type | Req | Description |
|---|---|---|---|
| checks_json | string | – | – |
| expose | boolean | – | – |
No output schema declared.
No examples provided.
routine_stop ~30
Cancel the active replay and close only RoutineKit's isolated browser. Already completed side effects are not rolled back.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
routine_tools ~29
List available tool contracts. WebMCP tools need routine_web_open first. Record names exactly as returned.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
routine_web_call ~61
Execute one discovered WebMCP tool after human approval. Selected calls are captured by an active recording. Tool hints are not safety guarantees.
| Name | Type | Req | Description |
|---|---|---|---|
| arguments_json | string | yes | – |
| name | string | yes | Exact webmcp: tool name from routine_tools. |
No output schema declared.
No examples provided.
routine_web_open ~47
Ask permission to open a WebMCP origin in a blank isolated browser. No existing login profile, screen-scraping fallback, or cross-origin requests.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
No output schema declared.
No examples provided.
routine_workbench ~34
Open the RoutineKit capture/replay workbench inside a compatible MCP Apps host. Human form elicitation is required for mutations.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the RoutineKit MCP server?
RoutineKit is an MCP server listed in the public MCP registry as io.github.sjh9714/routinekit. Capture tool workflows, save typed tools, and replay with human approval. Includes an MCP Apps UI. This page covers its npm package (routinekit).
Is the RoutineKit MCP server safe to use?
RoutineKit scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 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 RoutineKit MCP server expose?
RoutineKit exposes 16 tools: routine_list, routine_tools, routine_record, routine_preview, routine_save, and 11 more. Their descriptions and schemas cost roughly 703 tokens of context every time the server is loaded.
Is the RoutineKit MCP server still maintained?
RoutineKit 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.
What licence is the RoutineKit MCP server under?
RoutineKit declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.