drio
  • App Tracker
  • Contact
Sign inStart Free
drio© 2026 drio All rights reserved.

Get the Builder Brief

Weekly notes from Yash on MCP, ChatGPT apps, and getting business workflows into production.

Product
HomeTemplatesHow it worksPricing
Solutions
Use casesOperations teamsEcommerce teamsFinance teamsRecruiting teamsReal estate teams
Resources
DocsMCP RegistryGlossaryBlogChangelog
Company
Contact usWhy driodrio agency↗Privacy PolicyTerms of Service
All systems normal
Follow us on:
MCP Registry/Backtest360
B

Backtest360

MCP server exposing the Backtest360 engine API as tools for AI agents.

Import into drioUse with clientMarkdown

Install and compare this MCP server

Use this profile to copy client config, check auth requirements, review tools and resources, and compare related MCP servers before adding it to an AI client.

Install
uvx backtest360-mcp
Clients
Claude, Cursor, VS Code, Codex
Transport
STDIO, HTTP
Auth
Auth required by registry metadata
Capabilities
0 tools, 0 resources, 0 prompts
Related
onsense, Bowmark, nable

Want MCP integration examples?

Get practical integration notes and launch examples for MCP servers like Backtest360.

InstallAuthTools & ResourcesOverview

Install

Connection

Transport
STDIO, HTTP
Endpoint
https://mcp.backtest360.com/mcp
Command
uvx backtest360-mcp
Environment
{ "BACKTEST360_API_KEY": "YOUR_SECRET_VALUE" }

Headers: X-API-Key

Claude Desktop

Add this server entry to the mcpServers object in your Claude Desktop config, then restart the app.

{
  "mcpServers": {
    "com-backtest360-backtest360": {
      "command": "uvx",
      "args": [
        "backtest360-mcp"
      ],
      "env": {
        "BACKTEST360_API_KEY": "YOUR_SECRET_VALUE"
      }
    }
  }
}

Config location

macOS
~/Library/Application Support/Claude/claude_desktop_config.json
Windows
%APPDATA%\Claude\claude_desktop_config.json

Auth

Package transport

No remote HTTP endpoint is advertised. Use the package or stdio setup shown in Install.

Get credential

Scan with credential

Not persisted

Paste an API key, bearer token, or session value from the provider. It is used once to list inventory and discarded after the request.

Backtest360 engine API key, sent to the hosted MCP server as X-API-Key. Get a free key at https://backtest360.com/api-access.

Tools & Resources

Tools
0
Resources
0
Prompts
0
No public tools, resources, or prompts captured yet. Use Auth when this server requires credentials.

Tools

No tools captured yet.

Resources

No resources captured yet.

Prompts

No prompts captured yet.

Questions

What is Backtest360?+

Backtest360 is an MCP server for MCP server exposing the Backtest360 engine API as tools for AI agents.. It supports STDIO, HTTP transport.

How do I install Backtest360?+

Use the generated config in Install. This server runs with uvx backtest360-mcp; add any required environment variables before starting your client.

How do I add Backtest360 to Claude Desktop?+

Choose the Claude Desktop tab in Install, copy the config, and add it to Claude Desktop's MCP server settings. Endpoint: https://mcp.backtest360.com/mcp.

How do I add Backtest360 to Claude Code?+

Choose the Claude Code tab in Install, copy the config, and add it to Claude Code's MCP server settings. Endpoint: https://mcp.backtest360.com/mcp.

How do I use Backtest360 with Codex?+

Choose the Codex tab in Install, copy the config, and add it to Codex's MCP server settings. Endpoint: https://mcp.backtest360.com/mcp.

How do I add Backtest360 to Cursor or VS Code?+

Choose the Cursor or VS Code tab in Install, copy the config, and add it to Cursor or VS Code's MCP server settings. Endpoint: https://mcp.backtest360.com/mcp.

What endpoint and transport does Backtest360 use?+

Backtest360 uses STDIO, HTTP transport. Endpoint: https://mcp.backtest360.com/mcp.

What tools and resources does Backtest360 expose?+

Backtest360 inventory is listed when the MCP endpoint exposes tools, resources, or prompts. Some servers require auth first.

Does Backtest360 require authentication?+

Backtest360 is marked with Auth required by registry metadata auth. You may need provider login, an API key, a bearer token, or a session header.

Related MCPs

onsenseAndroid phone camera, sensors & files for any MCP client — local, no cloud, no ADB.BowmarkDo things on live websites: prices, availability, quotes, bookings, anything behind a form or login.nableSee where your cloud and AI bills go, and spend less. Local-first, in your terminal or editor.HPSILab Quant FinanceQuant finance tools: stock analysis, options IV, Monte Carlo, AI prediction, risk scan, backtests.DataCharterLocal-first, contract-governed data explorer with read-only, PII-masked query tools for AI agents.InferraAuditable rule-based decisions with RAG explanations: a Rete engine decides, an LLM explains why.

Profile notes

  • Remote header: X-API-Key (required; secret)
  • Package: Pypi backtest360-mcp v0.5.0
  • Environment variable: BACKTEST360_API_KEY (required; secret)
  • The upstream registry signals required auth or secrets.

Packages

PackageRegistryVersionInputs
backtest360-mcp

stdio

pypi0.5.0

Env: BACKTEST360_API_KEY required secret

Details

Version
0.5.0
Auth
Auth required by registry metadata
Repository
https://github.com/Backtest360/backtest360-mcp
Updated
Jul 29, 2026