io.github.FixtureForge/timeweaver-mcp
NPM · TIMEWEAVER-MCP · SCANNED AUG 3
Synthetic time-series test data with trend, seasonality, noise, and anomalies, for any MCP client.
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 Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. 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 64 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 556 tokens (~278/item across 2 items; 2 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 Management27
- Stability observed for 8 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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 · timeweaver-mcp
claude mcp add fixtureforge-timeweaver-mcp -- npx -y timeweaver-mcp
codex mcp add fixtureforge-timeweaver-mcp -- npx -y timeweaver-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"fixtureforge-timeweaver-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"timeweaver-mcp"
],
"enabled": true
}
}
} openclaw mcp add fixtureforge-timeweaver-mcp --command npx --arg -y --arg timeweaver-mcp
mcp_servers:
fixtureforge-timeweaver-mcp:
command: "npx"
args: ["-y", "timeweaver-mcp"] {
"mcpServers": {
"fixtureforge-timeweaver-mcp": {
"command": "npx",
"args": [
"-y",
"timeweaver-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.
- 3 Aug 26 +4
- Stability: unverified → 0.27 ▲ functional
- 2 Aug 26 +56
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Security disclosure: fail → unverified ▼ functional
- Dependency health: partial → unverified ▼ functional
- MCP protocol: unverified → pass ▲ functional
- Maintenance: unverified → pass ▲ functional
- License: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → excellent ▲ functional
- Licence: MIT functional
- 1 Aug 26 −11
- Tool coverage: 100 → unverified ▼ functional
- Dependency health: unverified → partial ▲ functional
- 31 Jul 26 −25
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +19
- Tool coverage: unverified → 100 ▲ functional
- 28 Jul 26 −19
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 27 Jul 26 43
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 95 packages
95 packages in the resolved dependency tree · 95 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
generate_timeseries ~496
Generate realistic synthetic time-series data with configurable trend, seasonality, noise, anomalies, and multiple correlated series. Ideal for testing dashboards, charts, monitoring/alerting, forecasting and anomaly-detection. Output as JSON, CSV, or SQL INSERTs. Use a preset for quick sensible defaults, or specify components explicitly.
| Name | Type | Req | Description |
|---|---|---|---|
| anomalies | array | — | Injected anomalies for testing detection/alerting. Pro feature. |
| ar1_phi | number | — | AR(1) autocorrelation coefficient (-1..1), used when noise='ar1'. |
| baseline | number | — | Baseline level the series varies around. |
| correlation | number | — | Target pairwise correlation between multiple series (0..1). Pro feature. |
| format | string | — | Output format. 'json' (default), 'csv', or 'sql'. CSV and SQL are Pro features. |
| frequency | string | — | Spacing between points. Default daily (or the preset's frequency). |
| integer | boolean | — | Round values to integers. |
| length | integer | — | Number of data points. Default 100. |
| max | number | — | Clamp values to this maximum. |
| min | number | — | Clamp values to this minimum. |
| names | array | — | Optional explicit series names. |
| noise | string | — | Noise model. 'ar1' (autocorrelated) is a Pro feature. |
| noise_level | number | — | Standard deviation of the noise. Default 1. |
| preset | string | — | Optional preset name (see list_presets). Fills sensible defaults; explicit params below override it. |
| seasonality | array | — | One or more seasonal cycles, summed together. Multiple cycles are a Pro feature. |
| seed | integer | — | Deterministic seed for reproducible output. Pro feature. |
| series_count | integer | — | How many series to generate. >1 is a Pro feature. Default 1. |
| start | string | — | ISO start timestamp, e.g. '2024-01-01T00:00:00Z'. Default 2024-01-01. |
| table_name | string | — | Table name for SQL output. Default 'timeseries'. |
| trend | string | — | Trend shape. Non-linear trends are a Pro feature. |
| trend_strength | number | — | Trend magnitude: slope per point (linear), growth rate (exponential), or capacity (logistic). |
No output schema declared.
No examples provided.
list_presets ~60
List the built-in time-series presets (realistic ready-made configurations like e-commerce sales, server CPU, IoT temperature, website traffic, stock price, API latency). Use a preset name with generate_timeseries to get sensible defaults you can still override.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.