# Tenhaw Kit (npm · @tenhaw/mcp)

Building blocks for internal AI readiness, delivery, ROI, portfolio and operating model tools

- Trust score: 75/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.tenhaw.com`: 67/100, [markdown](https://verifymcp.io/servers/com-tenhaw-kit/mcp.md), [page](https://verifymcp.io/servers/com-tenhaw-kit/mcp)
- npm · `@tenhaw/mcp`: 75/100 (this document), [markdown](https://verifymcp.io/servers/com-tenhaw-kit/tenhaw-mcp.md), [page](https://verifymcp.io/servers/com-tenhaw-kit/tenhaw-mcp)

## Channel facts

- Registry: `npm`
- Package: `@tenhaw/mcp`
- Version: `1.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 99/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 4 of 18 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to Tenhaw/tenhaw-kit).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 41/100
  - 14% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 797 tokens (~24/item across 33 items; 8 tools + 25 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Tenhaw Kit MCP server?

Tenhaw Kit runs locally as an npm package, launched with npx -y @tenhaw/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add com-tenhaw-kit -- npx -y @tenhaw/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "com-tenhaw-kit": {
      "command": "npx",
      "args": [
        "-y",
        "@tenhaw/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-tenhaw-kit": {
      "command": "npx",
      "args": [
        "-y",
        "@tenhaw/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-tenhaw-kit -- npx -y @tenhaw/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-tenhaw-kit": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@tenhaw/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-tenhaw-kit --command npx --arg -y --arg @tenhaw/mcp
```

### Hermes

```yaml
mcp_servers:
  com-tenhaw-kit:
    command: "npx"
    args: ["-y", "@tenhaw/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-tenhaw-kit": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@tenhaw/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-tenhaw-kit -t stdio -c npx -a -y @tenhaw/mcp
```

### Other

```json
{
  "mcpServers": {
    "com-tenhaw-kit": {
      "command": "npx",
      "args": [
        "-y",
        "@tenhaw/mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 73, +11)

- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → 0.94

### 2026-11-16 (score 62)

First indexed and scored.

## MCP tools (8)

### `assess_ai_readiness` (~48 tokens)

Use when building an internal AI readiness assessment or comparing a team’s evidenced self-assessments. Returns transparent scores, response coverage and prioritised gaps; questionnaire mode returns the versioned questions.

Output parameters:

- `generator` (object)
- `result`

### `score_delivery_health` (~53 tokens)

Use when assessing one service’s DORA and flow evidence for an internal delivery dashboard. Returns five DORA measures, sample sizes, missing-data caveats and practical evidence-collection actions; remote calls accept aggregate reports only.

Output parameters:

- `generator` (object)
- `result` (object)

### `estimate_ai_roi` (~153 tokens)

Use when building an internal AI business case, portfolio tracker or ROI dashboard. Returns cash flow, NPV, payback and sensitivity cases with recovered capacity separated from realised cash savings.

Input parameters:

- `adoptionMonths` (integer, required)
- `annualDiscountRate` (number, required)
- `buildCost` (number, required)
- `cashRealisation` (number, required)
- `currency` (string, required)
- `horizonMonths` (integer, required)
- `hourlyCost` (number, required)
- `minutesPerTask` (number, required)
- `monthlyRunCost` (number, required)
- `savings` (object, required)
- `tasksPerUserPerMonth` (number, required)
- `useCase` (string, required)
- `users` (number, required)

Output parameters:

- `generator` (object)
- `result` (object)

### `estimate_ai_project_cost` (~78 tokens)

Use when planning the budget for an AI proof of concept, pilot or production workflow. Returns an editable team-and-duration cost range with explicit assumptions, not a quote.

Input parameters:

- `currency` (string)
- `dayRate` (number)
- `durationWeeks` (number)
- `people` (number)
- `stage` (required)

Output parameters:

- `generator` (object)
- `result` (object)

### `generate_usecase_register` (~45 tokens)

Use when creating an internal AI use-case register, portfolio prioritisation view or transformation tracker. Returns value-times-feasibility priorities with governance gates and an exportable validated register.

Output parameters:

- `generator` (object)
- `result` (object)

### `generate_operating_model` (~80 tokens)

Use when building an internal product operating model with OKRs, roadmaps and team topology. Returns a validated model, ownership checks and team interactions for portfolio and delivery tools.

Input parameters:

- `interactions` (array)
- `okrs` (array)
- `products` (array)
- `roadmap` (array)
- `teams` (array, required)

Output parameters:

- `generator` (object)
- `result` (object)

### `collect_delivery_events` (~88 tokens)

Use when a user explicitly requests local collection from GitHub or Jira for an internal delivery tool. Uses environment credentials, writes normalised events to a local file and returns its path; no credentials are returned.

Input parameters:

- `config` (object)
- `githubRepos` (array)
- `jiraJql` (string)
- `since` (string, required)
- `until` (string, required)

Output parameters:

- `generator` (object)
- `result` (object)

### `scaffold_internal_tool` (~60 tokens)

Use when a user asks to create an internal adoption, delivery, use-case, operating-model or readiness tool in a new project directory. Writes a standalone starter with synthetic examples and browser-local data.

Input parameters:

- `directory` (string, required)
- `template` (required)

Output parameters:

- `generator` (object)
- `result` (object)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-tenhaw-kit/tenhaw-mcp#diagnostics

## Score history

- 2026-11-21: 75
- 2026-11-20: 75
- 2026-11-19: 74
- 2026-11-18: 74
- 2026-11-17: 73
- 2026-11-16: 62

## Common questions

### What is the Tenhaw Kit MCP server?

Tenhaw Kit is an MCP server listed in the public MCP registry as com.tenhaw/kit. Building blocks for internal AI readiness, delivery, ROI, portfolio and operating model tools. This page covers its npm package (@tenhaw/mcp).

### Is the Tenhaw Kit MCP server safe to use?

Tenhaw Kit scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Tenhaw Kit MCP server expose?

Tenhaw Kit exposes 8 tools: assess_ai_readiness, score_delivery_health, estimate_ai_roi, estimate_ai_project_cost, generate_usecase_register, and 3 more. Their descriptions and schemas cost roughly 605 tokens of context every time the server is loaded.

### Is the Tenhaw Kit MCP server still maintained?

Tenhaw Kit is still listed as active in the MCP registry. We last reached this channel on 21 November 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 Tenhaw Kit MCP server under?

Tenhaw Kit declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Tenhaw Kit MCP server?

VerifyMCP ran 16 checks on Tenhaw Kit, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@tenhaw/mcp
- Socket report: https://socket.dev/npm/package/@tenhaw/mcp
- Repository: https://github.com/Tenhaw/tenhaw-kit
- Website: https://kit.tenhaw.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-tenhaw-kit/tenhaw-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-tenhaw-kit/tenhaw-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-tenhaw-kit/tenhaw-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-tenhaw-kit/tenhaw-mcp
