io.github.FixtureForge/timeweaver-mcp
timeweaver
Synthetic time-series test data with trend, seasonality, noise, and anomalies, for any MCP client.
alive probed 2026-10-19
2tools
≈ 969tokens, estimate
≈ 0.5 %of Claude's 200k window
0.7×the median server
346 msto initialize
10 msto list tools
- Run it
- npx -y timeweaver-mcp@0.1.1 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- timeweaver 0.1.0
- Capabilities
- tools
- Instructions
- none
- Of a 1M window
- ≈ <0.1 % of a 1M context window, estimate
- Claude count
- The count_tokens endpoint refused the tool schemas: invalid x-api-key. The estimate stands in.
- Repository
- https://github.com/FixtureForge/timeweaver-mcp
- Registry
- active, updated 2026-05-30 · registry entry
- Reachable
- 1 of the last 1 probe
Most expensive tools
Estimates with the o200k_base tokenizer.
| Tool | o200k estimate | Share of this server |
|---|---|---|
| generate_timeseries | 883 | 91 % |
| list_presets | 86 | 9 % |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The Anthropic count_tokens endpoint refused the tool schemas (invalid x-api-key). A client that validates schemas can refuse them too.