PineForge-Codegen
Related Servers
Alternatives to PineForge-Codegen
- FlicenseNot gradedqualityNot gradedmaintenanceexposes a remote MCP endpoint so agents can: run strategy backtests by symbol/timeframe/date range, pass strategy inputs programmatically, receive structured backtest results (trades, win rate, profit, drawdown), keep long-running runs observable via progress notifications, support Binance Futures tickers only, enforce a maximum of 1440 candles per backtest, apply a rate limit of 3 backtests per7-
- AlicenseAqualityDmaintenanceA type-safe MCP server that enables AI agents to control TradingView Desktop via Chrome DevTools Protocol, allowing chart state reading, symbol/timeframe changes, and OHLCV data fetching.111MIT
- AlicenseBqualityBmaintenanceOpen-source MCP server for market analysis: screeners, multi-timeframe technical analysis and backtests for crypto, stocks, forex and futures. 39 tools. Hosted version: TradingMCP.371,648 PyPI5,317MIT
Related Servers
- AlicenseAqualityBmaintenanceLLM-native code tools: 44 MCP tools for AI agents to read, understand and modify code. Rust tree-sitter parse daemon (crash-isolated), SQLite symbol index (repo map 98ms), transactional journal-backed writes, deterministic quality gates (zero LLM calls). 512MB cgroup: 128 concurrent, zero OOM. MIT.131MIT
- AlicenseNot gradedqualityDmaintenanceYour AI forgets everything between sessions. This fixes that — 98%+ retrieval accuracy, With llm 100% on LongMemEval, 99% token savings. 44 MCP tools. Fully local, zero cost.20MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to perform hybrid code search, get explanations, analyze relations and impacts, retrieve context packs, and generate documentation across ~45 languages via 17 MCP tools, all powered by a local vector database and LLM.2Apache 2.0
- AlicenseNot gradedqualityDmaintenanceLocal-first memory, pipelines, learning, feedback, and safe code tools for AI coding agents.MIT
- AlicenseCqualityCmaintenanceEnables IDE and terminal agents to query an offline AST graph, inspect a file’s one-hop impact, verify changes with zero-token checks and tests, and run Plan-Execute-Verify coding cycles using a local Ollama model.8Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables local LLMs to perform enterprise-grade code auditing, AST security screening, architectural planning, and real-time Discord observability with zero cloud API costs.1MIT
TDQS
Scored across 12 tools
Each tool targets a distinct action, and descriptions actively disambiguate (backtest_pine vs backtest_pine_grid, transpile-only vs run). The coverage trio (list_coverage_topics → get_coverage_topic → check_pine_feature) is well-nested by granularity, and check_engine_image vs pull_engine_image are clear. Minor overlap: check_tradingview_parity also runs the strategy, and binance_symbols/fetch_binance_ohlcv both touch the Binance API, but boundaries remain legible.
Names consistently use snake_case with a verb_noun pattern (list_*, get_*, check_*, backtest_*, fetch_*, transpile_*, pull_*). The only deviation is binance_symbols, which despite listing/validating omits the list_ prefix. Otherwise highly predictable.
Twelve tools sit squarely in the well-scoped 3-15 range. Each earns its place: core workflow (transpile, backtest, sweep, parity), data/infra (fetch, symbols, image management), and coverage discovery (list/get/check). No filler.
The Pine backtest lifecycle is well covered end-to-end: coverage discovery, transpile, single backtest, parameter sweeps, data fetching, parity verification, and engine/image management. Minor gaps exist, such as no tool to list or retrieve previously generated report_path files or manage saved artifacts, but agents can work around this via filesystem paths.