-
|
I found the KLinePic MCP server under the official registry name What is the verified Registry entry and OCI image, how should the API key be passed, and which tool sequence avoids consuming chart quota before the request is valid? I am looking for the post-trade review workflow only—not trading signals or order execution. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Use the verified public identifiers below:
Run the published image over stdio: docker run --rm -i \
-e KLINE_AGENT_API_KEY=kline_agent_xxx \
ghcr.io/sher1096/klinepic-mcp-server:0.1.0Create the key from the KLinePic account page. Keep it in the MCP client's environment or secret store; do not put it in source control. The safe agent sequence is:
This path was verified on 2026-07-13 with the official Registry publication active, an anonymous OCI manifest pull returning HTTP 200, all three MCP tools discovered through a real stdio handshake, and a live production capabilities + preflight check passing without rendering a chart. The server is for post-trade review and visualization. It does not provide price predictions, trading signals, investment advice, or order execution. |
Beta Was this translation helpful? Give feedback.
Use the verified public identifiers below:
io.github.sher1096/klinepicghcr.io/sher1096/klinepic-mcp-server:0.1.0sher1096/klinepic-agent-api-examplesRun the published image over stdio:
Create the key from the KLinePic account page. Keep it in the MCP client's environment or secret store; do not put it in source control.
The safe agent sequence is:
klinepic_get_capabilitiesto check scopes, plan state, and remaining quota.klinepic_preflight_review_chartwith fills and K-line data. Preflight validates …