io.github.musatoktas/whyts
NPM · WHYTS-MCP
Find out why a TypeScript project is slow: measured analysis and before/after comparison.
Available components
Last scanned (2 hours ago)
Scores higher than 93% of npm servers
Category Testing and QA
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 Security100
- 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
- 0 of 5 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to musatoktas/whyts). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 13 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability61
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 871 tokens (~290/item across 3 items; 3 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 Management73
- Stability observed for 22 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 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.
- 24 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 23 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 0.8.9 → 0.8.10 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 5 Nov 2026 · Analysed npm/whyts-mcp@0.8.10
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 | musatoktas/whyts |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/musatoktas/whyts/.github/workflows/release.yml@refs/tags/v0.8.10 |
| Rekor log index | 3414181924 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:afc9dd53fe33dd33bb3d13df24a654ab6bd5a8d70551888da53e53ead5dc8817dcfddd66330ef0780ba306ada65c4ceeff8324c8b3359c45f96b6354b |
Background: How many MCP packages publish verified provenance →
Dependencies 5 packages
| Packages resolved | 5 |
|---|---|
| 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 →
analyze ~253
Find out why a TypeScript project is slow. Runs one traced type check of the project (plus `runs` untraced timing runs) and returns compact JSON: Check time, file count, compiler error summary (not the full list of errors), `diagnoses` (a known slow-type pattern with location, evidence and a fix), the top 5 measured findings, and warnings. It takes as long as a full type check of the project (seconds to minutes), plus the extra timing runs.
| Name | Type | Req | Description |
|---|---|---|---|
| maxOldSpaceMb | integer | – | Heap limit in MB for the compiler process. Ignored with TypeScript 7. |
| project | string | yes | Absolute path to a directory with a tsconfig.json, or to a tsconfig file. |
| runs | integer | – | Untraced timing runs for a stable Check time (default 1). Each run is one more full type check. Use 3 or more for a median. |
| timeoutSeconds | number | – | Compiler timeout in seconds for each type check. Default 900. |
| typescript | string | – | Path to a typescript package directory to use instead of the one in the project (5.x, 6.x or 7.x). |
No output schema declared.
No examples provided.
compare ~309
Prove whether a change made type checking faster or slower. Runs the full type check `runs` times for the baseline and for the candidate project (a copy or a git worktree of the same project, before and after the change), alternating the order, and returns a decision: `separated` (the ranges do not overlap, a real change, with direction), `within-noise` (no change can be claimed) or `not-comparable` (a side has compiler errors or the compilers differ). It takes about (2 x runs + 2) type checks, so it is slow: `runs` 3 gives a quick answer and 5 or more a firm one.
| Name | Type | Req | Description |
|---|---|---|---|
| baseline | string | yes | Absolute path to the project before the change (directory with tsconfig.json, or a tsconfig file). |
| candidate | string | yes | Absolute path to the project after the change. It must be a separate directory, for example a git worktree. |
| maxOldSpaceMb | integer | – | Heap limit in MB for the compiler process. Ignored with TypeScript 7. |
| runs | integer | – | Measured runs per side (default 5, minimum 3 for a verdict). |
| timeoutSeconds | number | – | Compiler timeout in seconds for each type check. Default 900. |
| typescript | string | – | Path to a typescript package directory to use instead of the one in the project (5.x, 6.x or 7.x). |
No output schema declared.
No examples provided.
explain ~128
Show why one file is in the TypeScript program: the shortest import chain from a configured root and the direct importers. It reads the import graph only and does not run the type checker, so it finishes in seconds.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | File to explain, relative to the tsconfig directory. |
| project | string | yes | Absolute path to a directory with a tsconfig.json, or to a tsconfig file. |
| typescript | string | – | Path to a typescript package directory to use instead of the one in the project (5.x, 6.x or 7.x). |
No output schema declared.
No examples provided.
How do I install the io.github.musatoktas/whyts MCP server?
io.github.musatoktas/whyts runs locally as an npm package, launched with npx -y whyts-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 · whyts-mcp
claude mcp add musatoktas-whyts -- npx -y whyts-mcp
What is the io.github.musatoktas/whyts MCP server?
io.github.musatoktas/whyts is an MCP server listed in the public MCP registry as io.github.musatoktas/whyts. Find out why a TypeScript project is slow: measured analysis and before/after comparison. This page covers its npm package (whyts-mcp).
Is the io.github.musatoktas/whyts MCP server safe to use?
io.github.musatoktas/whyts scores 89 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 io.github.musatoktas/whyts MCP server expose?
io.github.musatoktas/whyts exposes 3 tools: analyze, compare, explain. Their descriptions and schemas cost roughly 690 tokens of context every time the server is loaded.
Is the io.github.musatoktas/whyts MCP server still maintained?
io.github.musatoktas/whyts is still listed as active in the MCP registry. We last reached this channel on 5 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 io.github.musatoktas/whyts MCP server under?
io.github.musatoktas/whyts declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.