Analytics
prereason.com
Provides market briefings, metrics, and data with pre-reasoned signals and trend analysis for financial domains.
ENDPOINT 1
https://api.prereason.com/api/mcp
MCP server metadata
- Name
- prereason
- Version
- 0.7.0
Known tools 5
list_briefingsList all available pre-reasoned market briefings with tier requirements.
Inferred read-onlylist_metricsList all available individual metrics (119 metrics across bitcoin, macro, and calculated categories).
Inferred read-onlyget_contextGet a pre-reasoned market briefing with trend signals, confidence scores, regime classification, and causal narratives for the requested domain (Bitcoin, macro, cross-asset, FX).
Inferred read-onlyget_metricGet a single metric with pre-reasoned signal interpretation, trend analysis (7d/30d/90d), confidence score with factor breakdown, momentum, and percentile ranking.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.prereason]
url = "https://api.prereason.com/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"prereason": {
"type": "http",
"url": "https://api.prereason.com/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: prereason
Remote MCP URL: https://api.prereason.com/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"prereason": {
"url": "https://api.prereason.com/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"prereason": {
"type": "http",
"url": "https://api.prereason.com/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "prereason",
"transport": "streamable-http",
"url": "https://api.prereason.com/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.