io.github.tracetify/tracetify-mcp
NPM · TRACETIFY-MCP · SCANNED AUG 19
Trace how any product actually grew — 12-source growth reconstruction for competitor research.
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 →
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
- 30 of 96 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 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 309 tokens (~61/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 50% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · tracetify-mcp
claude mcp add tracetify-tracetify-mcp -- npx -y tracetify-mcp
codex mcp add tracetify-tracetify-mcp -- npx -y tracetify-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"tracetify-tracetify-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"tracetify-mcp"
],
"enabled": true
}
}
} openclaw mcp add tracetify-tracetify-mcp --command npx --arg -y --arg tracetify-mcp
mcp_servers:
tracetify-tracetify-mcp:
command: "npx"
args: ["-y", "tracetify-mcp"] {
"mcpServers": {
"tracetify-tracetify-mcp": {
"command": "npx",
"args": [
"-y",
"tracetify-mcp"
]
}
}
} 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.
- 18 Aug 26 +15
- Malware scan: unverified → pass ▲ security
- 17 Aug 26 53
First indexed and scored.
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 19 Aug 2026 · Analysed npm/tracetify-mcp@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 |
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
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.
get_trace ~34
Check a running trace. When status is "done", read the report with read_report.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
No output schema declared.
No examples provided.
read_report ~35
Read one Tracetify growth report by slug (from search_reports or a completed trace). Free.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
search_reports ~49
Search existing Tracetify growth reports by domain. Reading existing reports is free.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Domain or fragment, e.g. "weshop" or "weshop.ai" |
No output schema declared.
No examples provided.
start_trace ~90
Trace how a product actually grew: 12 sources, takes 60-90s, costs credits from your Tracetify balance. Returns a cached report slug for free when a fresh one already exists. Poll progress with get_trace.
| Name | Type | Req | Description |
|---|---|---|---|
| refresh | boolean | – | Force a fresh run even if a cached report exists |
| url | string | yes | Domain to trace, e.g. weshop.ai |
No output schema declared.
No examples provided.
unlock_report ~101
Permanently unlock a report's full timeline, evidence and SEO detail for this account. Costs credits — quote the exact price to the user first (it is in the report's timelineLocked.cost field from read_report) and call this ONLY after they explicitly agree to spend. Idempotent: unlocking an already-unlocked report never charges twice. Returns the full report. The verdict stays on the website — you are the analyst here.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.