Hesper Atlas Evidence
com.hesperatlas/hesper-atlas · 1.6.0
Verify stock signals, replay evidence, provenance, freshness, and caveats.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 45 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://hesperatlas.com/mcpstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 15 tools.
- Protocol
- 2025-06-18
- Calls itself
- hesper-atlas 1.6.0
- Handshake time
- 295 ms
- HTTP status
- 200
The tools it lists (15, as of 4 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
get_track_recordUse when a user asks whether Hesper Atlas's headline track record is supported, or wants winning, losing and still-open periods. Returns headline performance of today's trend engine replayed over up to five years of historical end-of-day data: number of closed signals, win rate, average winner vs average loser, average hold, plus a summary and bounded page of the open book (positions still running, marked at the last close). Winning and losing replay signals are both included. This is a retrospective replay, not an append-only live record. Signal data, not investment advice.
get_ledger_statsUse when a user asks for drawdowns, weak periods, best-versus-worst results, or whether a headline hides an unfavorable distribution. Returns detailed cuts of the current-rule historical replay: per calendar year, per theme, return distribution buckets, holding periods, the ten best and ten worst closed trades, the open book, and closed+open combined on identical buckets. Use `section` to pull one cut instead of all of them. Signal data, not investment advice.
get_symbol_recordUse when a user asks how Hesper Atlas's current rules historically behaved on one ticker. Returns every closed round trip produced on one ticker (entry date, entry price, exit date, exit price, return, days held), plus its open position if it currently has one. This is retrospective history, not a forward record or current recommendation: use get_signal for the latest end-of-day state. Signal data, not investment advice.
list_closed_tradesThe raw closed-signal historical replay, newest exit first, filterable by symbol and exit date. Winners and losers both; nothing is excluded from the replay. Signal data, not investment advice.
get_methodologyUse before interpreting a performance or signal claim, especially when a user asks for assumptions, limitations or possible bias. Explains how the engine decides, what the published numbers do and do not claim, and the known biases in the record. Read this before quoting any statistic from the other tools.
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
com.hesperatlas/hesper-atlas, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 37 days ago. The registry entry · hesperatlas.com