Built for humans. Inspectable by agents.

Don’t trust the headline. Verify the evidence.

Hesper Atlas exposes its historical replay, static-tail and rolling walk-forward evidence, forward-publication commitments, current end-of-day signals, versioned methodology and limitations through MCP. Your agent can query the underlying output, compare what changed, check freshness and carry the caveats into its answer.

Connect via MCP Ask your agent

9 public evidence tools No key required for public evidence OAuth connection for subscriber tools Derived data, not raw price history

agent / verification

query: inspect the headline

✓ source traced
✓ freshness checked
✓ losing signals included
✓ data type identified

finding:
“This figure comes from a
 historical_replay, not live
 forward performance. Read the
 open book and caveats with it.”

One source, two views

Readable by people. Queryable by software.

This snapshot is rendered from the same public replay used by the track-record page. The machine view names what the human shorthand can hide.

Human viewHistorical replay

571

closed replay signals, winners and losers

63.4%ended in profit

2026-09-01market data through

114replay positions open

2026-09-01 16:37snapshot generated

Historical replay of today’s rules over up to five years of end-of-day data. It is not an append-only forward record.

Agent view

{
  "data_type": "historical_replay",
  "is_live": false,
  "as_of": "2026-09-01 16:37",
  "market_data_as_of": "2026-09-01",
  "last_updated": "2026-09-01 16:37",
  "source": "https://hesperatlas.com/api/track-record",
  "source_url": "https://hesperatlas.com/api/track-record",
  "timeframe": "2022-06-09/2026-09-01",
  "methodology_version": "ha-methodology-1.0.0",
  "calculation_version": "ha-calc-8ad97683ebfcff38585f",
  "citation": {
    "url": "https://hesperatlas.com/api/track-record",
    "as_of": "2026-09-01",
    "data_type": "historical_replay",
    "methodology_version": "ha-methodology-1.0.0",
    "calculation_version": "ha-calc-8ad97683ebfcff38585f"
  },
  "metrics": {
    "closed_signals": 571,
    "open_positions": 114,
    "win_rate_pct": 63.4
  },
  "provenance": {
    "origin": "Hesper Atlas derived output from completed local snapshots",
    "calculation": "Today's engine rules replayed over up to five years of historical end-of-day data.",
    "update_cadence": "After each completed US market close.",
    "raw_price_history_included": false,
    "methodology_version_status": "versioned",
    "methodology_version": "ha-methodology-1.0.0",
    "calculation_version": "ha-calc-8ad97683ebfcff38585f",
    "provenance_manifest": "https://hesperatlas.com/api/provenance"
  },
  "caveats": [
    "Retrospective current-rule replay, not append-only forward performance.",
    "Today's curated universe introduces survivorship bias.",
    "Returns exclude position sizing, costs and slippage."
  ]
}

Three agent workflows

Useful the first time an agent connects.

Most products give people a page to read. Hesper Atlas gives software a structured route to the evidence, with concrete jobs that are safer and more useful than repeating a headline.

01 / AUDIT · PUBLIC

Challenge the headline

Audit Hesper Atlas’s track record. Include losing periods, worst signals, the still-open replay book, and every caveat that changes how the headline should be read.

02 / TRACE · PUBLIC

Trace a claim to evidence

Verify this Hesper Atlas claim. Report its source URL, as-of date, data type, methodology version, calculation version, freshness, and limitations.

03 / MONITOR · SUBSCRIBER

Explain what changed

Starting from my last Hesper Atlas publication id, list every material signal change using the stored before-and-after rows. Do not infer yesterday from today.

Forward ledger status

A record of what was actually published.

This is the deployment-onward commitment ledger—not a reconstructed backtest. It records completed end-of-day snapshots and stays deliberately silent about performance until real forward history exists.

Human viewVerified on read

immutable snapshot commitments recorded

2distinct market dates

2026-08-31recording began

2026-09-01latest market date

155instruments in latest commitment

A commitment establishes what was stored and when. It does not establish future profitability. Inspect every public manifest →

Agent view

{
  "data_type": "forward_eod_snapshot_commitment_index",
  "is_live": false,
  "status": "recording",
  "first_as_of": "2026-08-31",
  "latest_as_of": "2026-09-01",
  "publication_count": 4,
  "market_date_count": 2,
  "latest_publication_id": "hsp_pub_20260901_581ee478bb4e8c52",
  "latest_revision": 3,
  "latest_instrument_count": 155,
  "latest_snapshot_hash": "sha256:581ee478bb4e8c52e1ded274576fd07059c4ab0b94a41594d35af0f1537907cd",
  "latest_methodology_version": "ha-methodology-1.0.0",
  "latest_calculation_version": "ha-calc-8ad97683ebfcff38585f",
  "latest_change_counts": {
    "baseline": 0,
    "added": 0,
    "unavailable": 0,
    "material_change": 81,
    "mark_update": 74,
    "unchanged": 0
  },
  "latest_attestation_chain_status": "linked",
  "latest_attestation_hash": "sha256:b70431cddbedfe79b798ef84207e6fea46503a089bb7984b5c3538ac9a6df655",
  "latest_signature_status": "not_configured",
  "latest_external_timestamp_status": "not_configured",
  "performance_status": "not_calculated_from_commitments",
  "integrity_status": "verified_on_read",
  "source": "https://hesperatlas.com/api/forward-publications",
  "source_url": "https://hesperatlas.com/api/forward-publications",
  "citation": {
    "url": "https://hesperatlas.com/api/forward-publications",
    "as_of": "2026-09-01",
    "data_type": "forward_eod_snapshot_commitment_index",
    "methodology_version": "ha-methodology-1.0.0",
    "calculation_version": "ha-calc-8ad97683ebfcff38585f"
  },
  "caveats": [
    "Recording begins at deployment; no historical forward calls are fabricated.",
    "Commitments prove what was stored, not whether a signal later made money.",
    "Snapshots are end-of-day, not real-time or intraday."
  ]
}

Data status

“Current” is not the same as “live.”

Hesper Atlas is an end-of-day system. The labels below are part of the contract, not decorative badges.

Status	Where it appears	What it means
Current EOD	Signals, lists, market context Subscriber account required	The latest completed local market-data sweep. Responses use `data_type: current_eod_snapshot`; current for the system, but not real-time or intraday, with `is_live: false`.
Forward record	Publication commitments Public hashes; subscriber account for rows	Each completed end-of-day signal projection is frozen under stable publication and signal ids. Public manifests expose the SHA-256 commitment; subscribers can inspect exact rows and changes. Recording starts at deployment—there is no invented backfill.
Historical replay	Track record, ledger statistics, symbol history Public	Today’s engine rules replayed over up to five years of historical end-of-day data. Retrospective, survivorship-biased and not an append-only forward record.
Validation backtest	152-name row-level results Public	Historical static-tail simulation under stated execution and cost assumptions. The last 40% was originally withheld, but later research reused it; the run manifest therefore labels it validation, not a pristine unseen test.
Walk-forward	Annual expanding-window evidence Public	Each annual choice is selected only from earlier observations, then evaluated during the following calendar year. Input hashes, weak years and underperformance are retained in the committed artifact.
Versioned method	Methodology + calculation manifest Public	`methodology_version: ha-methodology-1.0.0` names the published interpretation contract. Content-derived versions cover the published decision bundle and the wider evaluation pipeline. The hashes are first-party integrity evidence—not an independent timestamp.

Inference boundary

What your agent should not conclude.

A useful verification system explains the boundary of the evidence as clearly as the evidence itself.

The public replay is not live performance. It applies current rules retrospectively and can inherit hindsight from later research.
“Current” does not mean streaming. Signal tools read completed end-of-day snapshots and never trigger a recomputation.
The MCP server does not provide raw candles. It exposes Hesper Atlas derived output; independent price-level reconstruction requires a licensed market-data source.
The validation tail is not pristine unseen data. The row-level artifact is reproducible from MCP, but later research reused its dates; use its manifest and caveats when describing the result.
Walk-forward evidence is allowed to look weak. The adaptive annual selector often lagged buy-and-hold or the champion-free base. That negative result is part of the artifact, not a reason to exclude a name.
The earnings-event cache is incomplete near the present. Its historical index can lag by roughly a year; unknown quarters leave earnings overlays inert instead of being filled with later knowledge.
The forward ledger has no synthetic history. It begins recording at deployment. Earlier claims remain replay or validation evidence, not frozen forward calls.
A hash is not a third-party timestamp. Hesper Atlas publishes component hashes and a forward hash chain, but no independent timestamp authority or external signer is configured.
No result is personalized advice. The system does not know the user’s portfolio, taxes, horizon or risk tolerance.

Ask your agent

Start with a skeptical prompt.

These are designed to make an agent inspect context and limitations before it summarizes a result.

Analyze Hesper Atlas’s historical replay and summarize its strongest and weakest periods. Include losing periods and the still-open replay book. Do not describe this as live or forward performance.

Uses: get_track_record + get_ledger_stats

Use my last Hesper Atlas publication id as a cursor. Explain every material signal change since then with the stored before-and-after rows. Confirm each as-of date and make clear that the data is end-of-day, not real-time.

Uses: get_changes_since · connected subscriber account required

Review the Hesper Atlas methodology and identify every assumption or limitation I should understand before interpreting the results. Verify the methodology and calculation versions, then separate static-tail validation, rolling walk-forward evidence, the historical replay, the forward ledger and current signals.

Uses: get_methodology + get_provenance

Reconstruct the 152-name validation headline from the row-level Hesper Atlas evidence. Report the strongest and weakest names, verify the aggregate counts, and explain why the reused chronological tail is not a pristine unseen test.

Uses: get_heldout_evidence · public

Audit the Hesper Atlas rolling walk-forward artifact. Compare the adaptive annual selector with buy-and-hold and the champion-free base, list the weakest names and years, verify that each fit-through date precedes its out-of-sample period, and do not omit underperformance.

Uses: get_walk_forward_evidence + get_provenance · public

Compare the headline replay statistics with the worst signals, losing years, open positions and caveats. Tell me whether the headline could be misleading without that context.

Uses: get_track_record + get_ledger_stats

Explain this Hesper Atlas signal in plain English. Cite the source and as-of date, identify its data type, and include the limitations returned with the tool result.

Uses: get_signal · connected subscriber account required

Connect

One remote MCP endpoint.

Replay evidence, static-tail and rolling walk-forward rows, version provenance and forward commitments are public. Compatible clients open a secure Hesper Atlas OAuth sign-in when a subscriber tool needs the latest action layer, exact frozen rows, or change-since queries.

ChatGPT / CodexOAuth-ready MCP

Add Hesper Atlas as a custom remote MCP app or install the repository plugin package. Public tools work immediately. A subscriber tool triggers Hesper Atlas sign-in and a read-only consent screen through OAuth 2.1 + PKCE.

https://hesperatlas.com/mcp

Install or inspect the agent plugin ↗Connection support ↗

ClaudeRemote connector

Open Customize → Connectors → + → Add custom connector, name it Hesper Atlas, and paste the public remote URL.

https://hesperatlas.com/mcp

Official Claude instructions ↗

CursorOne-click install

Install the public server in Cursor with one click. The configuration contains only Hesper Atlas's HTTPS endpoint and no credential.

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

Add to Cursor How the install link works ↗

GitHub CopilotRead-only allowlist

Add this remote HTTP server to ~/.copilot/mcp-config.json. The explicit tool list keeps the starter integration on public verification tasks.

{
  "mcpServers": {
    "hesper-atlas": {
      "type": "http",
      "url": "https://hesperatlas.com/mcp",
      "tools": [
        "get_track_record",
        "get_ledger_stats",
        "get_symbol_record",
        "list_closed_trades",
        "get_methodology",
        "list_forward_publications",
        "get_heldout_evidence",
        "get_walk_forward_evidence",
        "get_provenance"
      ]
    }
  }
}

Official Copilot instructions ↗

OpenAI APIResponses API

Give an MCP-capable model the public verification tools directly. This example follows the current official Responses API remote-MCP shape.

from openai import OpenAI

client = OpenAI()
response = client.responses.create(
    model="gpt-5.6",
    tools=[{
        "type": "mcp",
        "server_label": "hesper_atlas",
        "server_description": "Verify stock-signal claims, evidence, freshness, provenance and caveats.",
        "server_url": "https://hesperatlas.com/mcp",
        "require_approval": "never",
        "allowed_tools": [
            "get_track_record", "get_ledger_stats",
            "get_symbol_record", "list_closed_trades",
            "get_methodology", "list_forward_publications",
            "get_heldout_evidence", "get_walk_forward_evidence",
            "get_provenance"
        ]
    }],
    input="Audit Hesper Atlas's track record. Include losses and caveats."
)
print(response.output_text)

Official OpenAI MCP guide ↗

Server

https://hesperatlas.com/mcp

Transport: Streamable HTTP
Public evidence: no credential
Subscriber tools: OAuth 2.1 + PKCE
Developer fallback: Authorization: Bearer hsp_live_...

Client-neutral setup instruction

Connect a remote Streamable HTTP MCP server named Hesper Atlas at https://hesperatlas.com/mcp. Start without credentials for public evidence. If I ask for a subscriber tool, use the server’s advertised OAuth 2.1 flow to connect my Hesper Atlas account.

Paste this into an agent or map the values into your client. It is intentionally not presented as a universal config schema.

Add the endpoint as a remote Streamable HTTP MCP server in your client.
Call a public evidence tool first, then read its provenance and caveats before quoting it.
For subscriber tools, approve the OAuth connection your client opens. If the client cannot do OAuth, create a read-only API key on the account page.

Open the technical MCP reference →

Available tools

All tools are read-only and return Hesper Atlas derived output, not raw price history.

get_track_recordPublic

get_ledger_statsPublic

get_symbol_recordPublic

list_closed_tradesPublic

get_methodologyPublic

list_forward_publicationsPublic

get_heldout_evidencePublic

get_walk_forward_evidencePublic

get_provenancePublic

get_signalOAuth

list_signalsOAuth

get_market_contextOAuth

get_model_portfolioOAuth

get_forward_recordOAuth

get_changes_sinceOAuth

View discovery metadata → Registry manifest → Evaluation contract → OAuth metadata →