Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Tenhaw Kit

NPM · @TENHAW/MCP · 2 COMPONENTS

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

75 Trust /100

Last scanned (16 hours ago)

Scores higher than 51% of npm servers

Category AI and Machine Learning

Trust breakdown (7 categories)

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 Security99
  • 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
  • 4 of 18 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to Tenhaw/tenhaw-kit). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 4 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability41
  • 14% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 797 tokens (~24/item across 33 items; 8 tools + 25 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.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 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 26 +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.

  • 18 Nov 26 +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.

  • 17 Nov 26 +11
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → 0.94 ▲ functional
  • 16 Nov 26 62

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Analysed npm/@tenhaw/mcp@1.1.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo Tenhaw/tenhaw-kit
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/Tenhaw/tenhaw-kit/.github/workflows/release.yml@refs/heads/main
Rekor log index 3932418011
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:7e3259c62e73fa81b620cd06f663bba6150e0252f74bd9c8ab883b6053de0b482c8f89676efbf63c5263a3a3b0ff8636cdaa9a50eec0020f4aa452fd1

Background: How many MCP packages publish verified provenance →

Dependencies 18 packages
Packages resolved 18
Stale 4
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 8 exposed · ~605 tokens

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 →

Tool Tokens
assess_ai_readiness ~48

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
generatorobject––
result–yes–

No examples provided.

collect_delivery_events ~88

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.

NameTypeReqDescription
configobject––
githubReposarray––
jiraJqlstring––
sincestringyes–
untilstringyes–
NameTypeReqDescription
generatorobject––
resultobjectyes–

No examples provided.

estimate_ai_project_cost ~78

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.

NameTypeReqDescription
currencystring––
dayRatenumber––
durationWeeksnumber––
peoplenumber––
stage–yes–
NameTypeReqDescription
generatorobject––
resultobjectyes–

No examples provided.

estimate_ai_roi ~153

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.

NameTypeReqDescription
adoptionMonthsintegeryes–
annualDiscountRatenumberyes–
buildCostnumberyes–
cashRealisationnumberyes–
currencystringyes–
horizonMonthsintegeryes–
hourlyCostnumberyes–
minutesPerTasknumberyes–
monthlyRunCostnumberyes–
savingsobjectyes–
tasksPerUserPerMonthnumberyes–
useCasestringyes–
usersnumberyes–
NameTypeReqDescription
generatorobject––
resultobjectyes–

No examples provided.

generate_operating_model ~80

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.

NameTypeReqDescription
interactionsarray––
okrsarray––
productsarray––
roadmaparray––
teamsarrayyes–
NameTypeReqDescription
generatorobject––
resultobjectyes–

No examples provided.

generate_usecase_register ~45

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
generatorobject––
resultobjectyes–

No examples provided.

scaffold_internal_tool ~60

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.

NameTypeReqDescription
directorystringyes–
template–yes–
NameTypeReqDescription
generatorobject––
resultobjectyes–

No examples provided.

score_delivery_health ~53

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
generatorobject––
resultobjectyes–

No examples provided.

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.

npm · @tenhaw/mcp

# add to Claude Code
claude mcp add com-tenhaw-kit -- npx -y @tenhaw/mcp
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.