io.github.FixtureForge/timeweaver-mcp
NPM · TIMEWEAVER-MCP · SCANNED SEP 20
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 → Why this is hard to 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
- 31 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 112 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 Management93
- Stability observed for 28 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.FixtureForge/timeweaver-mcp server?
io.github.FixtureForge/timeweaver-mcp runs locally as an npm package, launched with npx -y timeweaver-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 · timeweaver-mcp
claude mcp add fixtureforge-timeweaver-mcp -- npx -y timeweaver-mcp
{
"mcpServers": {
"fixtureforge-timeweaver-mcp": {
"command": "npx",
"args": [
"-y",
"timeweaver-mcp"
]
}
}
} {
"servers": {
"fixtureforge-timeweaver-mcp": {
"command": "npx",
"args": [
"-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": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"timeweaver-mcp"
]
}
}
} assistant mcp add fixtureforge-timeweaver-mcp -t stdio -c npx -a -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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 10 Sept 26 −2
- Security disclosure: fail → unverified ▼ functional
- Stability: pass → 0.83 functional
- 9 Sept 26 0
- Stability: 0.97 → pass security
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 20 Sept 2026 · Analysed npm/timeweaver-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| 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 →
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.
What is the io.github.FixtureForge/timeweaver-mcp server?
io.github.FixtureForge/timeweaver-mcp is listed in the public MCP registry as io.github.FixtureForge/timeweaver-mcp. Synthetic time-series test data with trend, seasonality, noise, and anomalies, for any MCP client. This page covers its npm package (timeweaver-mcp).
Is the io.github.FixtureForge/timeweaver-mcp server safe to use?
io.github.FixtureForge/timeweaver-mcp scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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.FixtureForge/timeweaver-mcp server expose?
io.github.FixtureForge/timeweaver-mcp exposes 2 tools: list_presets, generate_timeseries. Their descriptions and schemas cost roughly 556 tokens of context every time the server is loaded.
Is the io.github.FixtureForge/timeweaver-mcp server still maintained?
io.github.FixtureForge/timeweaver-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 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.FixtureForge/timeweaver-mcp server under?
io.github.FixtureForge/timeweaver-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.