Prereason MCP server
{
"mcpServers": {
"prereason": {
"type": "http",
"url": "https://api.prereason.com/api/mcp"
}
}
}{
"mcpServers": {
"prereason": {
"type": "http",
"url": "https://api.prereason.com/api/mcp"
}
}
}{
"mcpServers": {
"prereason": {
"type": "http",
"url": "https://api.prereason.com/api/mcp"
}
}
}{
"servers": {
"prereason": {
"type": "http",
"url": "https://api.prereason.com/api/mcp"
}
}
}{
"mcpServers": {
"prereason": {
"type": "http",
"url": "https://api.prereason.com/api/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsoninstall npx -y @prereason/mcpversion 0.4.0
What it does
This server provides pre-reasoned Bitcoin and macroeconomic financial briefings for AI agents. It exposes 18 market briefings covering Bitcoin, macro indicators, cross-asset regimes, and liquidity signals with trend indicators and confidence scores. It is for developers building AI agents that need structured financial market context rather than raw price data.
- Fetch pre-reasoned market briefings like BTC momentum, macro snapshots, or regime classification to inform trading or analysis decisions.
- Query individual metrics (Bitcoin price, hash rate, Fed balance, VIX, etc.) with trend signals and percentile rankings.
- List available briefings and metrics to understand what data is accessible at your account tier.
Tools this server exposes
| Tool | Does |
|---|---|
| list_briefings | List all 18 pre-reasoned market briefings with their tier requirements (free, basic, or pro). |
| list_metrics | List all 30 available metrics across Bitcoin, macro, and calculated categories. |
| get_health | Check API health status, version, and your account tier. |
| get_context | Fetch a single pre-reasoned market briefing in markdown or JSON format. |
| get_metric | Fetch a single metric with trend signal, confidence score, and percentile ranking. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.