MCP.Market

PreReason MCP server

online · 100% uptime
by prereason.com·com.prereason/mcp·v0.9.1·8 stars
No reviews yet

Financial market context for AI agents, with listed companies' results: www.prereason.com/agents.md

A92/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
Growing

8 stars276 downloads/wk

Reviews

Write one

Nobody has reviewed PreReason yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

PreReason tools (7)

write = sends, deletes, buys or posts
  • get_changesFree

    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.

  • get_contextFree

    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.

  • get_healthFree

    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.

  • get_metricFree

    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.

  • get_newsFree

    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.

  • list_briefingsFree

    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.

  • list_metricsFree

    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.

Public scan report

scanner v0.1.10 · 2026-11-01 · same rubric, same numbers if you re-run it

no findings
  • Code scan10 source files scanned25/25
  • Live reliabilityremote reachable in 1067ms20/20
  • Tool poisoning7 tool descriptions checked15/15
  • Auth qualityAPI key sent as a header8/15
  • Maintenancelast push 2 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; website matches verified namespace9/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How PreReason compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
92/100
higher than 95% of 48,255 servers
Tools
7
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
417 ms
faster than 35% of 30,031 servers
GitHub stars
8
more than 86% of 28,688 servers
Downloads a week
276
more than 80% of 12,191 servers with a package

What its tools let an agent do: 7 read

Release history: 4 versions in the registry since 2026-03-18, latest 2026-10-28, typically one every 22 days.

Install PreReason in Claude Code, Cursor or VS Code

claude mcp add --transport http mcp https://api.prereason.com/api/mcp
Add to Cursor

What the publisher says

From the PreReason repository's README, as published. We do not edit it. Read it on GitHub

@prereason/mcp

MCP server for PreReason.

Bitcoin and macro market briefings for AI agents: trend signals, regimes, liquidity and ETF flows.

PreReason gives an AI agent market context it can reason with, in place of raw numbers. One call returns a briefing on Bitcoin, macro liquidity, FX or the links between assets, and the analysis is already in it: a signal line, trend direction over several windows, a regime label, confidence scores, percentile ranks, correlations and a plain language narrative. The catalogue holds 18 live briefings and 119 individual metrics, covering Bitcoin price and momentum, network and miner health, spot Bitcoin ETF flows, corporate Bitcoin treasuries, the Fed balance sheet, M2, net liquidity, Treasury yields and the dollar. It is served over MCP (a remote server and an npm bridge) and over REST, as Markdown or JSON. The catalogue tools need no key, and an agent can get a free key from inside the session: it shows one link, a person approves it, and the key arrives.

Quick Start

Option 1: Claude Desktop, no key needed

Requires Node.js 18+

Add this to claudedesktopconfig.json and restart Claude Desktop:

{
  "mcpServers": {
    "prereason": {
      "command": "npx",
      "args": ["-y", "@prereason/mcp"],
      "env": { "PREREASON_CLIENT": "claude-desktop" }
    }
  }
}

The catalogue tools work at once. The first time a briefing needs a key, the bridge asks for access: ask Claude for any briefing and the answer starts with Approve at https://www.prereason.com/claim/PR-XXXX-XXXX. Open the link, sign in or create a free account, click Approve. The key arrives in the bridge on its own, is saved to ~/.prereason/credentials.json, and the next call works. Nothing is created in your account until you click Approve.

Config file location:

  • macOS: ~/Library/Application Support/Claude/claudedesktopconfig.json
  • Windows: %APPDATA%\Claude\claudedesktopconfig.json
  • Linux: ~/.config/Claude/claudedesktopconfig.json

Already have a key? Add it to the env block as "PREREASONAPIKEY": "prlive..." and the bridge never asks.

Option 2: Direct HTTP with an API key (Claude Code, Cursor, Windsurf, Codex, Gemini CLI, VS Code, scripts)

Clients that hold their own config can call the endpoint directly, with the key as a header:

# Claude Code
claude mcp add --transport http prereason https://api.prereason.com/api/mcp --header "Authorization: Bearer YOUR_API_KEY"
{
  "mcpServers": {
    "prereason": {
      "type": "http",
      "url": "https://api.prereason.com/api/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

Windsurf uses serverUrl instead of url; Gemini CLI uses httpUrl; Codex uses url plus bearertokenenvvar in config.toml. No key yet? Point the client at the endpoint without a header and ask the assistant to call requestaccess; it walks you through the same one link approval and shows the key once, which you then paste into the config.

Option 3: Claude.ai and Claude Desktop custom connector

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

PreReason: common questions

Is PreReason MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the PreReason safety report
How do I install PreReason?
It runs remotely at api.prereason.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does PreReason need an API key?
Yes. The registry entry asks for PREREASON_API_KEY, X-API-Key.
Is PreReason maintained?
The last commit was 4 days ago (2026-10-31). The latest release is v0.9.1.
Is PreReason up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does PreReason compare with other MCP servers?
safety score 92/100 (higher than 95% of 48,255 servers); tools 7 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.