MCP Verified 14 hours ago free Registry import by @fastdrop

Backtest360

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

MCP server exposing the Backtest360 engine API as tools for AI agents. Official MCP Registry: com.backtest360/[email protected]. Remote endpoint: https://mcp.backtest360.com/mcp

Problem it solves

Discoverable MCP server listed in the official MCP Registry.

How it's different

Remote MCP endpoint ingested from the official registry and probed by FastDrop.

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as com.backtest360/backtest360 and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Claim this listing

Tools this endpoint exposes

Read directly from the endpoint on 28 Jul 2026. Not supplied by the maker.

  • get_me

    The configured API key's permissions, limits, and current usage. Cheap. Call early in a session — before planning work — to learn what this key can do instead of discovering limits th

  • engine_info

    Engine version, API contract number, and health. Free (not quota-counted). Call once at the start of a session to confirm the engine is reachable and which contract it serves.

  • get_catalog

    Fetch one engine reference catalog. Catalogs (cheap, cacheable per session): - 'operators' — comparison operators for condition expressions - 'execution-modes' — entry/exit an

  • list_indicators

    List indicators, or fetch one indicator's full schema. Cheap, cacheable per session. With no arguments: a compact catalog — ``{"indicators": [...], "count": N}`` — where each

  • list_templates

    List predesigned strategy templates, or fetch one in full. Cheap, cacheable per session. The engine returns the templates available to the calling key. With no arguments: a c

  • get_strategy_schema

    JSON Schema for the strategy document (condition_tree + indicators). Fetch this before composing a strategy by hand; the validate_strategy tool checks against the same rules.

  • validate_strategy

    Validate a strategy document without running a backtest. A cheap quota separate from backtest runs, so validate freely and ALWAYS before run_backtest. Args: strat

  • run_backtest

    Run a historical backtest against the engine. Quota-counted and compute-bound. Validate the strategy first (validate_strategy is far cheaper). On a 504 compute timeout, do NOT

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.

Sign in to claim this listing

Reviews

Sign in to leave a review.

No reviews yet.

Comments

Sign in to join the discussion.

No comments yet - start the discussion.