Wickworks MCP server
Self-hosted MCP server: technical indicators + smart-money-concepts from OHLC bars.
3 stars
Reviews
Write oneNobody has reviewed Wickworks yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Wickworks tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-10-16 · same rubric, same numbers if you re-run it
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 3 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Wickworks compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 75% of 48,255 servers
- GitHub stars
- 3
- more than 80% of 28,688 servers
Install Wickworks in Claude Code, Cursor or VS Code
claude mcp add wickworks -- docker run -i --rm docker.io/psyb0t/wickworks:v0.7.0
What the publisher says
From the Wickworks repository's README, as published. We do not edit it. Read it on GitHub
wickworks
The dumb-as-rocks OHLC analyzer. You throw bars at it over HTTP, it throws indicators and SMC objects back. That's the whole product. No database, no queue, no state, no opinions, no "AI-powered signals," no upsell to a $97/mo Discord. Just primitives.
Every snake-oil-flavored TA SaaS out there wants to tell you when to buy. Wickworks tells you the order block is at 1.0832 and the RSI is 71.4. The "what does that mean?" part is where your strategy lives — and it should live in your code, not behind someone else's paywall.
Built on pandas_ta and smartmoneyconcepts, wrapped in a FastAPI server, locked behind 370 tests that diff our output against closed-form references on real EURUSD ticks. If a math bug slips in, the test suite screams before the container builds.
Table of Contents
- What's Inside
- Quick Start
- API
- GET /health
- GET /metadata
- POST / — compute
- The indicators object
- Concepts
- Available indicators
- Request fields
- Response
- Errors
What's Inside
All JSON field names are camelCase. Output is NaN-safe — NaN becomes null, never a literal NaN token that blows up downstream parsers. NumPy/Pandas scalars and arrays are serialized cleanly (no numpy.float64(...) leaks). Bars in UTC, math in UTC, container runs TZ=UTC — timezone bullshit is your problem, not ours.
Quick Start
docker run --rm -p 8000:8000 psyb0t/wickworks:latestThat's it. The service listens on :8000.
docker compose
services:
wickworks:
image: psyb0t/wickworks:latest
ports: ["8000:8000"]
environment:
LOG_LEVEL: INFO
MAX_BARS: "5000"
MIN_BARS: "50"Local development container
make run # build the dev image and run uvicorn on :8000API
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Wickworks: common questions
- Is Wickworks MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the Wickworks safety report
- How do I install Wickworks?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Wickworks need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Wickworks maintained?
- The last commit was 21 days ago (2026-10-13). The latest release is v0.7.0.
- How does Wickworks compare with other MCP servers?
- safety score 88/100 (higher than 75% of 48,255 servers); github stars 3 (more than 80% of 28,688 servers). Full comparison.