MoneySignals Documentation

Give your code — or your AI agent — the measured market edge: event-driven signals with a public, audited track record, ML predictions with honest realized accuracy, and full market context. Available as a REST API and as a one-file MCP server you can connect to any agent in a single step.

Overview

Everything MoneySignals knows is reachable two ways, over the same data:

• REST API — https://api.moneysignals.us. JSON over HTTPS, one API key.
• MCP server — a thin Model Context Protocol wrapper over that API, so Claude Desktop, Claude Code, or any MCP client can call it as tools.

The product is built around one finding: selective, event-driven signals carry a measured edge, while always-on per-ticker ML is near coin-flip out-of-sample. The API surfaces both — and is honest about which is which (see Where the edge is).

Quick start

1. Verify the edge — no key needed

The audited track record is public, so you can check it before signing up:

# live win rate, avg return, resolved-call count for the event signals
curl https://api.moneysignals.us/track-record

2. Get a free API key — it comes with the free email signup

Join the free daily email and confirm your address — your API key arrives in the welcome email, no card required. It unlocks the ML predictions and every market-context endpoint. Pass it as the X-API-Key header:

curl -H "X-API-Key: at_sk_your_key" \
  https://api.moneysignals.us/api/v1/market/regime

Paid keys (from $49/mo) add the event signals — the measured edge — plus alt-data and higher limits.

3. Or connect an agent in one command — hosted MCP, nothing to install

claude mcp add --transport http moneysignals https://api.moneysignals.us/mcp \
  --header "X-API-Key: at_sk_your_key"

Then ask your agent: “What’s the market regime, and how accurate were MoneySignals’ recent predictions?” — see Connect via MCP.

Authentication, tiers & limits

• Header: X-API-Key: at_sk_… on every request except the public ones below.
• Public (no key): GET /track-record and GET /demo/snapshot — so you can connect and verify immediately.
• Free key: included with the free email signup — confirm your email and the key is in the welcome email. Lost it? Sign up again with the same address and confirm: the old key is revoked and a fresh one is emailed to you.
• Your key’s status: GET /api/v1/account/me works on every key and returns your tier, rate limits, and total usage. (Detailed 30-day analytics via GET /api/v1/account/usage is API Pro.) A 429 means slow down or upgrade.
• Errors come back as JSON: 401 (missing/invalid key) and 403 (tier doesn’t include the endpoint) point you to pricing.

Connect an AI agent (MCP)

Any MCP client (Claude Code, Claude Desktop, your own agent) gets all of MoneySignals as callable tools — no SDK to learn, no endpoints to wire up. Two ways to connect, same 21 tools either way: the hosted server (recommended — one command, nothing to install) or a downloadable one-file stdio server.

Hosted — one command, nothing to install

claude mcp add --transport http moneysignals https://api.moneysignals.us/mcp \
  --header "X-API-Key: at_sk_your_key"

No Python, no download, always the latest tools. Your key rides on the connection as an HTTP header — leave the --header off to connect keyless and try get_track_record first. Any client that speaks MCP Streamable HTTP works the same way: point it at https://api.moneysignals.us/mcp and send X-API-Key (or Authorization: Bearer) on each request. Building your own agent? It’s plain JSON-RPC:

curl -X POST https://api.moneysignals.us/mcp \
  -H "Content-Type: application/json" -H "X-API-Key: at_sk_your_key" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
       "params":{"name":"get_market_regime","arguments":{}}}'

Or run it locally (stdio)

Prefer a local process — or your client can’t send custom headers (Claude Desktop’s config, for one)? Download the one-file server:

pip install "mcp>=1.2" httpx
# download the one-file server (always the latest)
curl -O https://moneysignals.us/mcp/server.py

Claude Code — local stdio variant

claude mcp add moneysignals \
  --env MONEYSIGNALS_API_KEY=at_sk_your_key \
  -- python /path/to/server.py

Claude Desktop — config

Settings → Developer → Edit Config, then add:

{
  "mcpServers": {
    "moneysignals": {
      "command": "python",
      "args": ["/path/to/server.py"],
      "env": { "MONEYSIGNALS_API_KEY": "at_sk_your_key" }
    }
  }
}

Restart the client. Without a key, only get_track_record works — enough to confirm the connection. The free key unlocks predictions, market context and the ETF pullback signal; paid keys add the event signals. Override the base URL with MONEYSIGNALS_API_BASE if needed.

The 21 tools

no key public. free key works with the free key from the email signup. starter / pro need a paid API plan (from $49/mo).

Automated execution — pair with a broker

MCP servers don’t call each other; they’re both tools your agent uses. So automated investing is: connect both the MoneySignals MCP (for what to trade) and a broker MCP — e.g. Robinhood’s Agentic Trading MCP — (for execution), and let the agent orchestrate.

Two tools make this turnkey:

• get_daily_brief — the whole gated decision in one call: is the regime safe, what are the top picks, is a macro event imminent.
• get_trade_plan — the picks already shaped as {action, ticker, conviction} so each item maps straight onto a broker order.

{
  "count": 2,
  "plan": [
    {"action":"buy", "ticker":"SMH", "conviction":0.61, "type_win_rate":0.76},
    {"action":"sell_or_short", "ticker":"QPQ", "conviction":0.48}
  ],
  "disclaimer": "Model-derived suggestions — NOT financial advice."
}

Example agent prompt:

REST API reference

Base URL https://api.moneysignals.us. All endpoints below are prefixed /api/v1 unless noted, return JSON, and need the X-API-Key header. Try them live in the interactive API reference (or ReDoc).

Signals — the edge

API Starter and up — except /track-record (public) and /signals/etf-pullback (free key).

Predictions

Works with the free key (/predictions/batch is API Pro).

Market context

Works with the free key.

Social, alt-data & account

Social is API Pro; alternative data is API Starter and up. /account/me works on any key (/account/usage is API Pro).

Where the edge is

We did the walk-forward homework so you don’t over-trust the wrong thing:

Conviction ranks signals by a sample-size-shrunk type win-rate × the signal’s own confidence, so a lucky small-sample type can’t top the list.

Honesty & limits

• The track record is built from resolved signals (their stated horizon has elapsed) — no live-signal leakage, no cherry-picking. First-order types are included so the numbers aren’t flattering by selection.
• Aggregate returns are direction-signed P&L — a correct bearish call counts positive, so winning shorts aren’t averaged away. Ledger rows show the raw price move; direction + outcome carry the sign there.
• Win rates on small samples are noisy and can decay; treat any single number as evidence, not a guarantee.
• Some feeds lag (e.g. options-derived PCR carries a stale flag); the API tells you when.
• Nothing here is financial advice. Predictions and signals are automated, uncertain, and frequently wrong. See the Terms.