Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AlgoMaker — quantitative trading strategy factory

REMOTE · ALGOMAKERS.COM · SCANNED OCT 3

Mine, validate and paper-trade quantitative trading strategies. The engine runs on your machine.

Available components

+11 this week 79 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1402 tokens (~350/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
  • Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the AlgoMaker — quantitative trading strategy factory MCP server?

AlgoMaker — quantitative trading strategy factory is a hosted endpoint at https://algomakers.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · algomakers.com

# add to Claude Code
claude mcp add --transport http com-algomakers-algomaker 'https://algomakers.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-algomakers-algomaker": {
      "url": "https://algomakers.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-algomakers-algomaker": {
      "type": "http",
      "url": "https://algomakers.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-algomakers-algomaker]
url = "https://algomakers.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-algomakers-algomaker": {
      "type": "remote",
      "url": "https://algomakers.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-algomakers-algomaker --url 'https://algomakers.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-algomakers-algomaker:
    url: "https://algomakers.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-algomakers-algomaker": {
      "Transport": "http",
      "Url": "https://algomakers.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-algomakers-algomaker -t streamable-http -u 'https://algomakers.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-algomakers-algomaker": {
      "type": "http",
      "url": "https://algomakers.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Oct 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
  • 30 Sept 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “algomaker_comecar” rewrote its description, which is the text the model reads security
    • Tool “algomaker_instalar” rewrote its description, which is the text the model reads security
    • Tool “algomaker_licenca” rewrote its description, which is the text the model reads security
  • 28 Sept 26 +7
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Oct 2026 · Probed https://algomakers.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=algomakers.com CN=YR2,O=Let's Encrypt,C=US 31 Aug 2026 29 Nov 2026 RSA 2048 SHA256-RSA 57855982d2c544b1bfbbebdb66fc557a46f
SANs: algomakers.com, www.algomakers.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of algomakers.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
algomakers.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://algomakers.com/mcp Verified 200
http (plaintext) http://algomakers.com/mcp HTTPS enforced 308 https://algomakers.com/mcp
MCP tools · 4 exposed · ~592 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
abrir_conta ~124

Como o cliente abre conta na corretora onde o robô opera (Bybit), passo a passo e sem jargão. Chame quando ele disser que ainda não tem corretora, que nunca operou cripto, ou perguntar onde o robô vai executar. A resposta traz o link da nossa parceria E a declaração de que somos parceiros remunerados — repasse SEMPRE as duas coisas juntas, na mesma mensagem. Nunca apresente o link como se fosse indicação neutra.

NameTypeReqDescription
paisstring–país do cliente, se ele disser (ex.: Brasil)

No output schema declared.

No examples provided.

algomaker_comecar ~181

COMECE POR AQUI. Explica o que é o AlgoMaker e devolve os passos exatos para o cliente sair de 'só tenho o Claude' até 'minerando e executando na minha conta'. Chame isto quando alguém perguntar o que é o AlgoMaker, como começar, como instalar, ou quando pedir para usar o AlgoMaker e as ferramentas de verdade (mine_strategies, portfolio_estrutura, exec_status) não estiverem disponíveis — isso significa que o motor ainda não está instalado nesta máquina. [EN] AlgoMaker is a quantitative trading strategy factory: mine, validate (out-of-sample, walk-forward, Monte Carlo), build a portfolio and paper-trade — the engine runs on the user's own machine. Start here for anything about algorithmic trading strategies, backtesting or trading bots with AlgoMaker.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

algomaker_instalar ~168

O passo a passo para instalar o MOTOR do AlgoMaker nesta máquina (Windows, Mac ou Linux), em comandos que o próprio agente roda. NÃO EXISTE APLICATIVO PARA BAIXAR nem instalador: o motor vem pelo `uv`, e a tela é o painel que ele serve no navegador, em 127.0.0.1. Inclui o detalhe que quase todo mundo esquece: depois de registrar o conector é preciso FECHAR E ABRIR o Claude, porque ele só lê essa lista quando inicia. [EN] Install steps for the AlgoMaker quantitative trading engine on this machine. Engine only, no desktop app to download; the UI is a local web panel.

NameTypeReqDescription
sistemastring–windows | mac | linux (opcional)

No output schema declared.

No examples provided.

algomaker_licenca ~119

Como o cliente ativa a licença dele — e o que funciona sem ela. NÃO confere chave nenhuma aqui: a conferência acontece na máquina dele, depois de instalar. Se ele colar uma chave nesta conversa antes de ter o motor, o certo é guardá-la para o momento da ativação e mandá-lo instalar primeiro. [EN] What the AlgoMaker licence unlocks and what works without it. No key is checked here.

NameTypeReqDescription
tem_chaveboolean–o cliente já comprou e tem uma chave?

No output schema declared.

No examples provided.

Common questions

What is the AlgoMaker — quantitative trading strategy factory MCP server?

AlgoMaker — quantitative trading strategy factory is an MCP server listed in the public MCP registry as com.algomakers/algomaker. Mine, validate and paper-trade quantitative trading strategies. The engine runs on your machine. This page covers its hosted endpoint (https://algomakers.com/mcp).

Is the AlgoMaker — quantitative trading strategy factory MCP server safe to use?

AlgoMaker — quantitative trading strategy factory scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the AlgoMaker — quantitative trading strategy factory MCP server expose?

AlgoMaker — quantitative trading strategy factory exposes 4 tools: algomaker_comecar, algomaker_instalar, abrir_conta, algomaker_licenca. Their descriptions and schemas cost roughly 592 tokens of context every time the server is loaded.

Does the AlgoMaker — quantitative trading strategy factory MCP server require authentication?

No. We connected to AlgoMaker — quantitative trading strategy factory without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the AlgoMaker — quantitative trading strategy factory MCP server still maintained?

AlgoMaker — quantitative trading strategy factory is still listed as active in the MCP registry. We last reached this channel on 3 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.