Timefire
REMOTE · API.TIMEFIRE.AI
Timefire's public record of AI stock forecasts: graded books, track record and proof.
Available components
Last scanned (13 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 21 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 Security69
- 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 enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1937 tokens (~161/item across 12 items; 12 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 Management47
- Stability observed for 14 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 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 (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
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.
- 21 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.
- 19 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.
- 17 Nov 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.
- 15 Nov 26 0
- Tool “verify_batch” rewrote its description, which is the text the model reads security
- Schema quality: 145 → 161 ▼ functional
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 +3
- HSTS header: fail → pass ▲ security
- 11 Nov 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.
- 9 Nov 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.
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 21 Nov 2026 · Probed https://api.timefire.ai/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=timefire.ai | CN=WE1,O=Google Trust Services,C=US | 22 Oct 2026 | 20 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 8f91d97530d1a79f13f5967c8a0542e7 |
| SANs: timefire.ai, api.timefire.ai, *.api.timefire.ai | ||||||
| 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 api.timefire.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814 | 8 | Verified |
| timefire.ai. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.timefire.ai/mcp/ | Verified | 200 | |
| http (plaintext) | http://api.timefire.ai/mcp/ | Inconclusive | 406 |
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 →
explain_resolved_prediction Explain a prediction ~144
Get the stored evidence behind one stock's forecast in a graded book: its rank, side, market regime, 5- and 20-day lookback returns, news items and notes. Use this to see the context a stock was ranked in, and get_stock_resolved_history to find which books hold it. An ungraded date, or a ticker not in that book, is an error.
| Name | Type | Req | Description |
|---|---|---|---|
| ticker | string | yes | Stock ticker, for example AAPL. Upper or lower case both work. |
| trading_date | string | yes | The book's trading date, as YYYY-MM-DD. list_resolved_batches gives the graded dates. |
Structured output declared, but exposes no named fields.
No examples provided.
get_book_portfolio Book portfolio ~216
Get a resolved book's portfolio: market-cap-weighted vs SPY ("cap", the default, the portfolio the ledger's verdict grades) or equal-weighted vs RSP ("equal"), with each long pick's weight and graded return, the book return, the benchmark return and its evidence, alpha and verdict. Equal weights always pair with RSP and cap weights with SPY. Per prediction, books serve the two as equal_weight and market_cap_weight; never read a pick's cap_weight as either without checking inference_metadata.weighting. Use this for one book's result, and get_simulation_nav for the running portfolio across books. An ungraded or unknown date is an error.
| Name | Type | Req | Description |
|---|---|---|---|
| trading_date | string | yes | The book's trading date, as YYYY-MM-DD. list_resolved_batches gives the graded dates. |
| weighting | string | – | "cap" for market-cap weights against SPY (the default), or "equal" for equal weights against RSP. |
Structured output declared, but exposes no named fields.
No examples provided.
get_calibration Calibration ~80
Check whether forecasts matched outcomes: mean predicted against mean realized return by decile across every graded book, and hit rates by rank bucket and by side (long or short) across books graded under the published rule. Use this to judge how well the ranking held up, and get_track_record_stats for headline returns and the verdict tally.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_resolved_batch One book ~124
Get one graded book with every forecast and its outcome. A book (or batch) is one trading day's full S&P 500 slate, served once its long picks are fully graded, so other rows can still have null outcomes. Use list_resolved_batches to find the date, verify_batch for the book's proof and get_book_portfolio for its portfolio. An ungraded or unknown date is an error.
| Name | Type | Req | Description |
|---|---|---|---|
| trading_date | string | yes | The book's trading date, as YYYY-MM-DD. list_resolved_batches gives the graded dates. |
Structured output declared, but exposes no named fields.
No examples provided.
get_simulation_nav Portfolio value ~185
Get the paper portfolio's daily value (NAV), market-cap-weighted vs SPY ("cap", the default) or equal-weighted vs RSP ("equal"), with both benchmarks on every row. There is one row per resolved trading day. The series stops at the newest date by which every book is revealed, because a later value holds positions from books still sealed. Use this for portfolio value over time, and get_simulation_trades for the trades behind it.
| Name | Type | Req | Description |
|---|---|---|---|
| from_date | – | – | Earliest date to include, as YYYY-MM-DD. Omit for no lower bound. |
| to_date | – | – | Latest date to include, as YYYY-MM-DD. Omit for no upper bound. |
| weighting | string | – | "cap" for market-cap weights against SPY (the default), or "equal" for equal weights against RSP. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_simulation_trades Portfolio trades ~214
Get the paper portfolio's closed trades from resolved books, newest first, market-cap-weighted ("cap", the default) or equal-weighted ("equal"): the two trade at the same prices and differ in weight, and so in size and P&L. Open positions never appear. Date bounds apply to the day a trade opened; narrow them to see past the limit. Use this for individual trades, and get_simulation_nav for portfolio value.
| Name | Type | Req | Description |
|---|---|---|---|
| from_date | – | – | Earliest date to include, as YYYY-MM-DD. Omit for no lower bound. |
| limit | integer | – | Most trades to return, 1 to 500. Default 500. Older trades are cut off; there is no paging. |
| to_date | – | – | Latest date to include, as YYYY-MM-DD. Omit for no upper bound. |
| weighting | string | – | "cap" for market-cap weights against SPY (the default), or "equal" for equal weights against RSP. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_stock_resolved_history One stock's history ~121
Get one stock's rows from graded books only, newest first: its forecast, rank, pick side and outcome in each book. Use this to follow one ticker across books, explain_resolved_prediction for the evidence behind one row, and get_resolved_batch for a whole book. An unknown ticker returns an empty list.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Most rows to return, 1 to 500. Default 120. |
| ticker | string | yes | Stock ticker, for example AAPL. Upper or lower case both work. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_track_record_stats Headline stats ~136
Get aggregates computed only from fully resolved books: forecast counts, returns and hit rates, and how many books beat, matched (flat) or trailed SPY, each book's verdict graded on its cap-weighted long picks. The hit rates count the books graded under the published rule, from published_rule_from on; the 69 backtest books before it follow a rule of their own and are reported apart in the backtest_ fields, verdicts included. Use this for overall performance, get_calibration to test the ranking itself, and get_book_portfolio for a single book.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_universe_and_scoring_spec Record spec ~56
Get the versioned scoring rules, the metric definitions and the latest graded book's universe of stocks. Use this before interpreting a stat or a verdict, to learn how books are graded and which stocks are covered.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
list_resolved_batches Book history ~159
List graded books, newest first, one summary row each: date, returns, alpha against SPY and RSP, and verdict. A book (or batch) is one trading day's full S&P 500 slate. Use this to find a trading_date, then get_resolved_batch for every forecast in that book or verify_batch for its proof. Dates with no graded book return an empty list.
| Name | Type | Req | Description |
|---|---|---|---|
| from_date | – | – | Earliest date to include, as YYYY-MM-DD. Omit for no lower bound. |
| limit | integer | – | Most books to return, 1 to 500. Default 60. |
| to_date | – | – | Latest date to include, as YYYY-MM-DD. Omit for no upper bound. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
search_docs Search the docs ~116
Find the developer guides and site pages that match a few words. Each hit carries the page title, its canonical URL and a short excerpt. Use this for how Timefire works and what its terms mean, not for record data. No match returns an empty list, so try other words.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Most pages to return, 1 to 20. Default 5. |
| query | string | yes | A few words to search for, at most 8 words and 200 characters. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
verify_batch Verification record ~316
Get the public proof for one graded book: signed payload, hash, signature, content address and timestamp material, with the steps to check them. From 2026-04-28 on, a book is made after the close on its trading date (earlier books are a backtest, built later), and its return runs from that close over the next ten NYSE sessions (books before 2026-10-21 run from the first available close on or after that date over the next ten available sessions; the backtest books dated 2026-01-02 to 2026-04-13 run from the close before their date to nine sessions after it). The OpenTimestamps receipt proves the book existed before the Bitcoin block it names: compare that block's time with the next NYSE open after the trading date. sealed is true only while a book is still withheld. Every book served here is graded and revealed, so sealed is false, and that is not a failed check. The verified field is the server's own check of the hash and signature, not the timestamp; the evidence lets you repeat it yourself. Use this to check a book's signature and timestamp, and get_resolved_batch to read its forecasts and outcomes. An ungraded or unknown date is an error.
| Name | Type | Req | Description |
|---|---|---|---|
| trading_date | string | yes | The book's trading date, as YYYY-MM-DD. list_resolved_batches gives the graded dates. |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Timefire MCP server?
Timefire is a hosted endpoint at https://api.timefire.ai/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 · api.timefire.ai
claude mcp add --transport http ai-timefire-record 'https://api.timefire.ai/mcp/'
What is the Timefire MCP server?
Timefire is an MCP server listed in the public MCP registry as ai.timefire/record. Timefire's public record of AI stock forecasts: graded books, track record and proof. This page covers its hosted endpoint (https://api.timefire.ai/mcp/).
Is the Timefire MCP server safe to use?
Timefire scores 75 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 Timefire MCP server expose?
Timefire exposes 12 tools: list_resolved_batches, get_resolved_batch, get_track_record_stats, get_calibration, get_universe_and_scoring_spec, and 7 more. Their descriptions and schemas cost roughly 1,867 tokens of context every time the server is loaded.
Does the Timefire MCP server require authentication?
No. We connected to Timefire without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Timefire MCP server still maintained?
Timefire is still listed as active in the MCP registry. We last reached this channel on 21 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 Timefire MCP server?
VerifyMCP ran 12 checks on Timefire, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Timefire: HTTPS. 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.