Point-in-time methodology — tw market data MCP Resource

Point-in-time methodology is one of 6 resources on the tw market data MCP server. Connect the server and your client can attach it as context.

by client

How to attach Point-in-time methodology from your client

• Claude Code tw market data Resource/Point-in-time methodology run in your project directory
• Claude Desktop tw market data Resource/Point-in-time methodology ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor tw market data Resource/Point-in-time methodology ~/.cursor/mcp.json
• VS Code tw market data Resource/Point-in-time methodology .vscode/mcp.json
• Zed tw market data Resource/Point-in-time methodology ~/.config/zed/settings.json
• Windsurf tw market data Resource/Point-in-time methodology ~/.codeium/windsurf/mcp_config.json
• Cline tw market data Resource/Point-in-time methodology ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI tw market data Resource/Point-in-time methodology ~/.gemini/settings.json
• Grok tw market data Resource/Point-in-time methodology .mcp.json (in your project root)
• ChatGPT tw market data Resource/Point-in-time methodology Settings → Connectors → Advanced → Developer mode
• Claude.ai tw market data Resource/Point-in-time methodology Settings → Connectors → Add custom connector
• LangChain tw market data Resource/Point-in-time methodology pip install langchain-mcp-adapters

Other resources on this server

• Dataset catalogue
• Taiwan-market glossary
• Standards mapping (self-assessed)
• Leakage benchmark method
• Coverage and freshness

tw market data also offers 4 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.