EmidLabs Backtest
Server Details
Run crypto trading strategy backtests through EmidLabs's Backtesting API.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.4/5 across 3 of 3 tools scored.
Each tool has a clear, non-overlapping purpose: submitting a backtest, fetching its result (with built-in polling), and listing available assets. No ambiguity.
All tools follow a consistent verb_noun pattern in snake_case (submit_backtest, get_backtest_result, list_available_assets), making the action-target relationship clear.
Three tools is minimal but well-scoped for the server's core functionality: submit, retrieve results, and explore data. Each tool earns its place without bloat.
Covers the main workflow (submit, get result, list assets). Minor gaps exist (no delete/cancel, no detailed trade-level results), but these are intentionally omitted and agents can work around with the provided tools.
Available Tools
3 toolsget_backtest_resultGet Backtest ResultRead-onlyInspect
Fetches a submitted backtest by id. By default (waitForCompletion: true) polls internally until it finishes, so one call returns one final answer — no need to poll from the caller's side. Trade-level detail is intentionally omitted; only aggregate metrics are returned.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The id returned by submit_backtest. | |
| pollTimeoutMs | No | Defaults to 120000 (2 minutes). | |
| backtestApiKey | Yes | Your EmidLabs backtest API key. | |
| backtestBaseUrl | No | Defaults to the public production API. | |
| waitForCompletion | No | If true (default), polls internally until the backtest finishes or pollTimeoutMs elapses. |
Output Schema
| Name | Required | Description |
|---|---|---|
| id | No | |
| result | No | |
| status | No | |
| errorMessage | No |
list_available_assetsList Available AssetsRead-onlyInspect
Lists every asset pair with real historical data, each with its supported timeframes and the date range actually available. Optional to call — submit_backtest already returns a clear error (with the real available range) when an asset or date range doesn't have data, so this is for up-front exploration or for recovering from an "unknown asset" error, not a required step before every submit_backtest.
| Name | Required | Description | Default |
|---|---|---|---|
| backtestApiKey | Yes | Your EmidLabs backtest API key. | |
| backtestBaseUrl | No | Defaults to the public production API. Override only for self-hosted/staging use. |
Output Schema
| Name | Required | Description |
|---|---|---|
| assets | No |
submit_backtestSubmit BacktestInspect
Submits a strategy for backtesting against historical OHLCV data. Returns immediately with an id and status — call get_backtest_result to fetch the outcome once it finishes.
| Name | Required | Description | Default |
|---|---|---|---|
| assetPair | Yes | e.g. "BTC-USDC". | |
| finalDate | Yes | ISO date string, e.g. "2025-06-01". | |
| initialDate | Yes | ISO date string, e.g. "2025-01-01". | |
| backtestApiKey | Yes | Your EmidLabs backtest API key (created in the Console). | |
| backtestBaseUrl | No | Defaults to the public production API. Override only for self-hosted/staging use. | |
| strategySnapshotJson | Yes | The Strategy DSL object — see the strategy-dsl-spec resource for the shape. |
Output Schema
| Name | Required | Description |
|---|---|---|
| id | No | |
| status | No |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!