Curve-fitting study summary — Noon Barbari Backtesting MCP Resource
Curve-fitting study summary
is one of 3 resources on the
Noon Barbari Backtesting
MCP server. Connect the server and your client can attach it as context.
by client
How to attach Curve-fitting study summary from your client
- Claude Code Noon Barbari Backtesting Resource/Curve-fitting study summary run in your project directory
- Claude Desktop Noon Barbari Backtesting Resource/Curve-fitting study summary ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Noon Barbari Backtesting Resource/Curve-fitting study summary ~/.cursor/mcp.json
- VS Code Noon Barbari Backtesting Resource/Curve-fitting study summary .vscode/mcp.json
- Zed Noon Barbari Backtesting Resource/Curve-fitting study summary ~/.config/zed/settings.json
- Windsurf Noon Barbari Backtesting Resource/Curve-fitting study summary ~/.codeium/windsurf/mcp_config.json
- Cline Noon Barbari Backtesting Resource/Curve-fitting study summary ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Noon Barbari Backtesting Resource/Curve-fitting study summary ~/.gemini/settings.json
- Grok Noon Barbari Backtesting Resource/Curve-fitting study summary .mcp.json (in your project root)
- ChatGPT Noon Barbari Backtesting Resource/Curve-fitting study summary Settings → Connectors → Advanced → Developer mode
- Claude.ai Noon Barbari Backtesting Resource/Curve-fitting study summary Settings → Connectors → Add custom connector
- LangChain Noon Barbari Backtesting Resource/Curve-fitting study summary pip install langchain-mcp-adapters
Other resources on this server
Noon Barbari Backtesting also offers 3 prompts — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 24 September 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.