History of Market
REMOTE · HISTORYOFMARKET.COM
Read-only U.S. stock market history: S&P 500 since 1928, CAPE, drawdowns, index changes.
Available components
Last scanned (10 hours ago)
Scores higher than 69% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 822 tokens (~164/item across 5 items; 5 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 Management53
- Stability observed for 16 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 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.
- 30 Oct 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.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
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 5 Nov 2026 · Probed https://historyofmarket.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=historyofmarket.com | CN=WE1,O=Google Trust Services,C=US | 14 Oct 2026 | 12 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 5ba5ab9d500cfc0a0e1c51170a66b1f8 |
| SANs: historyofmarket.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of historyofmarket.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| historyofmarket.com. | No DS | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://historyofmarket.com/mcp | Verified | 200 | |
| http (plaintext) | http://historyofmarket.com/mcp | HTTPS enforced | 301 | https://historyofmarket.com/mcp |
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 →
annual_returns Calendar-year returns ~124
Calendar-year returns by year, price return and total return (dividends reinvested), with the arithmetic mean and compound annual rate over the complete years in the range. Indexes: sp500 (from 1928), ndx, sox, xlk, xlf, xly, xlp. The current year is year-to-date and flagged `ytd`.
| Name | Type | Req | Description |
|---|---|---|---|
| from_year | integer | – | First year to include. |
| index | string | – | Which index or ETF. Default sp500. |
| to_year | integer | – | Last year to include. |
No output schema declared.
No examples provided.
get_dataset Read a dataset ~224
Read one published dataset (the JSON behind a chart), e.g. "sp500/drawdowns", "sp500/pe", "ndx/forward-pe", "recessions". Rows can be filtered by `since`/`until` on their `date` (or `year`). A result is capped at about 60,000 characters: when a file is larger (long daily series), each array keeps its most recent rows and the cut is reported under `windowed`. Scalars and summary fields are always included.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Dataset path without /api/ and .json, as returned by search_charts. |
| since | string | – | Keep rows dated on or after this (YYYY-MM-DD or YYYY). |
| tail | integer | – | Rows kept per array after filtering, from the end. By default every row is returned when the result fits; long daily series are cut to their most recent rows and reported under `windowed`. |
| until | string | – | Keep rows dated on or before this (YYYY-MM-DD or YYYY). |
No output schema declared.
No examples provided.
get_latest Latest readings ~133
Current headline readings (value, unit, observation date) for the site's charts: S&P 500 level, Shiller CAPE, forward P/E for the S&P 500, Nasdaq 100, SOX and sector ETFs, VIX, drawdown from the high, breadth, Magnificent 7 weight and more. Pass `id` for one chart, or omit it for all.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Chart id, e.g. "pe" (Shiller CAPE), "forward-pe", "ndx-forward-pe", "drawdown", "vix". Omit for every reading. |
No output schema declared.
No examples provided.
index_changes Index additions and deletions ~98
Constituent changes with effective date, the company added, the company removed and the reason. sp500 from 2016, ndx from 2020. Newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| index | string | – | Default sp500. |
| limit | integer | – | Default 20. |
| since | string | – | Only changes effective on or after this date (YYYY-MM-DD). |
| ticker | string | – | Only changes that add or remove this ticker. |
No output schema declared.
No examples provided.
search_charts Find a chart or dataset ~95
Search the site's charts by topic or question (e.g. "bear markets", "Shiller CAPE", "Nasdaq 100 drawdown", "monthly seasonality"). Returns each chart's title, the question it answers, its page and the dataset path to pass to get_dataset.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Default 10. |
| query | string | yes | Words to match against chart titles and the questions they answer. |
No output schema declared.
No examples provided.
How do I install the History of Market MCP server?
History of Market is a hosted endpoint at https://historyofmarket.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 · historyofmarket.com
claude mcp add --transport http com-historyofmarket-market-history 'https://historyofmarket.com/mcp'
What is the History of Market MCP server?
History of Market is an MCP server listed in the public MCP registry as com.historyofmarket/market-history. Read-only U.S. stock market history: S&P 500 since 1928, CAPE, drawdowns, index changes. This page covers its hosted endpoint (https://historyofmarket.com/mcp).
Is the History of Market MCP server safe to use?
History of Market scores 77 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 History of Market MCP server expose?
History of Market exposes 5 tools: get_latest, annual_returns, index_changes, search_charts, get_dataset. Their descriptions and schemas cost roughly 674 tokens of context every time the server is loaded.
Does the History of Market MCP server require authentication?
No. We connected to History of Market without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the History of Market MCP server still maintained?
History of Market is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the History of Market MCP server?
VerifyMCP ran 13 checks on History of Market, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.