INDIVIDUAL MCP TOOL

get_heldout_evidence

Use when a user wants to reconstruct or challenge the 152-name static-tail validation headline.

hesperatlas.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://hesperatlas.com/mcp

No auth detected

Connect to this endpoint to inspect the live schema for get_heldout_evidence and invoke it with your own arguments.

{}

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

CONNECT WITH APPROVAL

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.hesper-atlas]
url = "https://hesperatlas.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "hesper-atlas": {
      "type": "http",
      "url": "https://hesperatlas.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: hesper-atlas
Remote MCP URL: https://hesperatlas.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "hesper-atlas": {
      "url": "https://hesperatlas.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "hesper-atlas": {
      "type": "http",
      "url": "https://hesperatlas.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "hesper-atlas",
  "transport": "streamable-http",
  "url": "https://hesperatlas.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

get_track_record — Use when a user asks whether Hesper Atlas's headline track record is supported, or wants winning, losing and still-open periods.
get_ledger_stats — Use when a user asks for drawdowns, weak periods, best-versus-worst results, or whether a headline hides an unfavorable distribution.
get_symbol_record — Use when a user asks how Hesper Atlas's current rules historically behaved on one ticker.
list_closed_trades — The raw closed-signal historical replay, newest exit first, filterable by symbol and exit date.
get_methodology — Use before interpreting a performance or signal claim, especially when a user asks for assumptions, limitations or possible bias.
list_forward_publications — Use when a user asks what Hesper Atlas actually published, when it was committed, what changed, or whether forward history is mature enough to evaluate.
get_walk_forward_evidence — Use when a user asks for stricter time-ordered evidence, weak years, benchmark underperformance, or a check against look-ahead.
get_provenance — Use when a user asks where a number came from, whether two results used the same code, or what first-party hashes can and cannot prove.