PreReason
REMOTE · API.PREREASON.COM · 2 COMPONENTS
Financial market context for AI agents, with listed companies' results: www.prereason.com/agents.md
Available components
Last scanned (48 minutes ago)
Scores higher than 96% 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 Security80
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2235 tokens (~203/item across 11 items; 7 tools + 4 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 (71% 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 5 Nov 26 0
- Tool “get_health” now declares an output schema ▲ functional
- Tool “get_news” now declares an output schema ▲ functional
- Tool “list_briefings” now declares an output schema ▲ functional
- Tool “list_metrics” now declares an output schema ▲ functional
- Tool “get_changes” now declares an output schema ▲ functional
- First check of Tool coverage: 71 functional
- 1 Nov 26 +4
- Stability: fail → pass ▲ security
- “get_changes” reworded the description of “companies” cosmetic
- “get_context” reworded the description of “entity” cosmetic
- 28 Oct 26 0
- “get_changes” reworded the description of “companies” cosmetic
- “get_context” reworded the description of “entity” cosmetic
2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 27 Oct 26 0
- “get_changes” reworded the description of “companies” cosmetic
- “get_context” reworded the description of “entity” cosmetic
2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 22 Oct 26 0
- Tool “get_changes” rewrote its description, which is the text the model reads security
- Tool “get_context” rewrote its description, which is the text the model reads security
- Tool “get_health” rewrote its description, which is the text the model reads security
- Tool “get_metric” rewrote its description, which is the text the model reads security
- Tool “get_news” rewrote its description, which is the text the model reads security
- Tool “list_briefings” rewrote its description, which is the text the model reads security
- Tool “list_metrics” rewrote its description, which is the text the model reads security
- Schema quality: 241 → 196 ▲ functional
- 20 Oct 26 −4
- Stability: pass → fail ▼ security
- 19 Oct 26 0
- Tool “list_briefings” rewrote its description, which is the text the model reads security
- 18 Oct 26 0
- Tool “list_briefings” rewrote its description, which is the text the model reads security
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://api.prereason.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.prereason.com | CN=YR2,O=Let's Encrypt,C=US | 2 Oct 2026 | 31 Dec 2026 | RSA 2048 | SHA256-RSA | 561d13acb5ec6f19606793da11e810b3ab7 |
| SANs: api.prereason.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.prereason.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| prereason.com. | absent | 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; preload |
| content-security-policy | default-src 'self';script-src 'self';style-src 'self' 'unsafe-inline';img-src 'self' data: https:;connect-src 'self';font-src 'self';object-src 'none';frame-src 'none';base-uri 'self';form-action 'self';upgrade-insecure-requests;frame-ancestors 'self';script-src-attr 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| 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.prereason.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://api.prereason.com/api/mcp | HTTPS enforced | 308 | https://api.prereason.com/api/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 →
get_changes Get Changes ~364
What changed since your last call: the change events PreReason records. A live briefing's state label changing, a tracked release becoming known, and, for the companies you name, figures stored for a newer period, an event driven situation turning on, and filed news. Each event says what changed, when it happened, when PreReason knew it and where to read it next (the briefing or metric to fetch with get_context or get_metric); it carries no value. For the filed and official records themselves, by date, use get_news. Pass the next_cursor of your previous call to read only what is new; without one, the last 24 hours. Needs a PreReason account with basic access or above: a signed in connection or an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| companies | array | – | Companies whose events to read: the ticker or CIK of a company filing with the US securities regulator (NVDA), a Japanese securities code (7203), a Korean stock code (005930), an Indian company's ISI… |
| cursor | string | – | The next_cursor of your previous call. Left out, the read starts from the last day of events. |
| limit | integer | – | Events one call returns, 1 to 100. Default 50. |
| types | array | – | The event types to read. Every type when left out. |
| Name | Type | Req | Description |
|---|---|---|---|
| events | array | yes | – |
| has_more | boolean | yes | – |
| next_cursor | string | yes | – |
No examples provided.
get_context Get Market Briefing ~546
Get a pre-reasoned market briefing with trends and confidence scores, plus regime classification and a rule based note on what moved with the price in the briefings that carry them, for the requested domain (macro, rates, bonds, FX, commodities, a listed company, cross-asset or Bitcoin; the same families as the server instructions). Output is written to be read directly by reasoning agents, not parsed for individual values. Find the briefing id with list_briefings first, which also gives each briefing's plan; for one data series rather than a briefing, use get_metric. Needs a PreReason account: a signed in connection or an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| block | string | – | One part of the company briefing, with entity (for example "valuation" or "against_guidance"); today only, except "numbers", which also takes date (its figures as known on that day). Leave out for th… |
| briefing | string | yes | Briefing ID to fetch |
| date | string | – | A past date, YYYY-MM-DD: the briefing as of the end of that day (UTC; a company's numbers at the end of the day in its own market), for the periods released by then. Each figure says when it was publ… |
| entity | string | – | The company for a per company briefing: the ticker or CIK of a company filing with the US securities regulator (NVDA), a Japanese securities code (7203), a Korean stock code (005930), an Indian compa… |
| format | string | – | Response format: markdown (human-readable, default) or json (structured data) |
| history | boolean | – | With block "numbers" alone: the numbers block with its core lines over the last eight quarters, or the half years a company files instead, and five fiscal years, as filed. One call; never part of the… |
No output schema declared.
No examples provided.
get_health Health Check ~74
Check API health status, version, and available endpoints. Use it to confirm the server answers or to read its version; it carries no market data, so use list_briefings or list_metrics to find data. No authentication required.
| Name | Type | Req | Description |
|---|---|---|---|
| verbose | boolean | – | Include detailed endpoint descriptions and data coverage info. Defaults to false. |
| Name | Type | Req | Description |
|---|---|---|---|
| account | object | yes | – |
| endpoints | object | yes | – |
| status | string | yes | – |
| timestamp | string | yes | – |
| version | string | yes | – |
No examples provided.
get_metric Get Metric Analysis ~238
Get a single metric with pre-reasoned signal interpretation, trend analysis (7d/30d/90d), confidence score with factor breakdown, momentum, and percentile ranking. Name the metric; list_metrics lists them and searches them by word. Needs a PreReason account: a signed in connection or an API key. Returns analyzed context (signal, trend direction, momentum, percentile among every stored daily close), not raw values. The signal is bullish, bearish or neutral on crypto series, and above-trend, below-trend or at-trend on every other metric, where the value sits against its trend, so a high yield reads above-trend. Use it to read where a metric stands against its trend and its own history, not just its number; for a reasoned view across several series, use get_context with a briefing. Every plan reads each metric's latest reading. Pro and above read every metric in full; on other plans, a metric outside the plan returns its latest reading only.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Response format: markdown (default) or json |
| metric | string | yes | Metric name to fetch |
No output schema declared.
No examples provided.
get_news Get News ~281
Dated records of what companies filed and what federal agencies and the Federal Reserve published, newest first, each with its source, its date or time and a link. Name a company in `about` for its filings alone; `kind` narrows to filed or official records; `since` and `until`, or `as_of`, set the window. Every answer names the sources it read. It states records, not reasons. For what changed since your last call, use get_changes; this tool reads the records themselves, by date. Needs a PreReason account: a signed in connection or an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| about | string | – | One company, by ticker or ISIN. Left out, records of every company and agency read. |
| as_of | string | – | Only records dated on or before this date, YYYY-MM-DD; in place of until. |
| kind | string | – | filed (company filings) or official (federal agency and Federal Reserve documents). Both when left out. |
| limit | integer | – | Records one call returns, 1 to 25. Default 10. |
| since | string | – | The first date of the window, YYYY-MM-DD. Seven days before until when left out. |
| until | string | – | The last date of the window, YYYY-MM-DD. Today (UTC) when left out. |
| Name | Type | Req | Description |
|---|---|---|---|
| about | – | yes | – |
| coverage | string | yes | – |
| records | array | yes | – |
| window | object | yes | – |
No examples provided.
list_briefings List Briefings ~246
List the pre-reasoned market briefings, each with its tier requirement, and the company briefing (equities.company), one listed company per call. Covers macro, rates, bonds, FX, commodities, listed companies, cross-asset and Bitcoin. Call it first to find the briefing id for a question, then read that briefing with get_context. Pass search with the question's words to get only the briefings that match, best first; when it names a company, the answer also lists the matching covered companies, each with the entity to pass to get_context. For one data series rather than a briefing, use list_metrics. Every covered company, by market, is listed at GET https://api.prereason.com/api/companies, with no key needed. No authentication required.
| Name | Type | Req | Description |
|---|---|---|---|
| search | string | – | The question or its key words (for example "is the yield curve inverted" or "Toyota earnings"). Returns the matching briefings, best first, at most five, and any covered companies it names (at most f… |
| tier | string | – | Filter briefings by subscription tier (free, basic, or pro). Returns all tiers if omitted. |
| Name | Type | Req | Description |
|---|---|---|---|
| briefings | array | yes | – |
| count | number | yes | – |
No examples provided.
list_metrics List Metrics ~132
List the individual metrics, among them the Fed balance sheet, M2 supply, Treasury yields, net liquidity, the dollar, cross-asset indices (SPY, QQQ, VXX, UUP) and Bitcoin price and hash rate. Use it to find a metric's name for get_metric; for a reasoned view across several series, use list_briefings. Filter by category or by a search word. No authentication required.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by metric category: bitcoin, calculated, eth, macro |
| search | string | – | Search term to filter metrics by name or description |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| free_key | string | yes | – |
| metrics | array | yes | – |
| pro_only_metrics | array | yes | – |
No examples provided.
How do I install the PreReason MCP server?
PreReason is a hosted endpoint at https://api.prereason.com/api/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.prereason.com
claude mcp add --transport http com-prereason-mcp 'https://api.prereason.com/api/mcp'
What is the PreReason MCP server?
PreReason is an MCP server listed in the public MCP registry as com.prereason/mcp. Financial market context for AI agents, with listed companies' results: www.prereason.com/agents.md. This page covers its hosted endpoint (https://api.prereason.com/api/mcp).
Is the PreReason MCP server safe to use?
PreReason scores 88 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 PreReason MCP server expose?
PreReason exposes 7 tools: list_briefings, list_metrics, get_health, get_context, get_metric, and 2 more. Their descriptions and schemas cost roughly 1,881 tokens of context every time the server is loaded.
Does the PreReason MCP server require authentication?
No. We connected to PreReason without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the PreReason MCP server still maintained?
PreReason 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.