This document outlines the security architecture, data handling practices, and risk profile of the MetaDuro Model Context Protocol (MCP) server for IT administrators, compliance officers, and security teams evaluating Claude AI, Cursor, or enterprise assistant connectors.
The MCP server never receives your conversation, only the parameters of each tool call (for example a ticker, a month, or a strategy's rules), and it does not store them; analysis results stay in server memory for about a minute so repeated requests are fast. Like any website, our web server keeps standard access logs (IP address, time, requested URL, user agent) for 14 days for security and troubleshooting. For Claude connectors, these requests come from Anthropic's servers rather than your device.
The connector only has read-only tools (get_seasonality, search_trading_strategies, get_strategy_details, list_popular_assets, chart_seasonality, run_backtest, list_indicators). Backtests are simulations on stored historical prices: the connector cannot place trades, connect to brokerages, or access exchange API keys.
The MCP endpoint needs no sign-in. No account, broker login, API key, or payment details are requested or collected.
All requests are served over HTTPS with TLS 1.2 or 1.3, and HSTS (HTTP Strict Transport Security) is enabled. Plain HTTP requests are redirected to HTTPS.
The MetaDuro MCP connector exposes 7 read-only tools: four search published seasonality reports and strategy backtests, two compute seasonality statistics and strategy backtests from market data MetaDuro already stores, and one lists the indicators strategy rules can use. It also offers 2 prompt templates, 2 documentation resources, and an MCP App (interactive charts that run sandboxed in the client, load nothing from the internet except the client's fonts, and communicate only with the client: tool calls and links you click). There are no tools that write data: the connector cannot place orders, trade assets, create accounts, save strategies, or modify external files or enterprise systems.
Everything the tools return is statistical market information: published reports from metaduro.com, or statistics computed on request from MetaDuro's stored price history. Private or unpublished user content is never returned. MetaDuro does not store or index tool-call parameters, and the MCP server never receives conversation histories. The MCP endpoint sets no cookies and uses no tracking pixels or fingerprinting.
The server runs on Google Cloud in the United States (region us-west1) behind an nginx reverse proxy. Connections are served only over HTTPS (port 443); plain HTTP is redirected to HTTPS. The MCP endpoint is stateless, rate-limits requests per IP address, and accepts request bodies of up to 64 KB.
For enterprise vendor questionnaires, security assessments, or vulnerability reports, please contact our engineering team directly at info@metaduro.com.