MCP · Model Context Protocol

Paste one URL. Sign in once.

Mountainhead ships a hosted MCP server with 22 tools — ranked signals, congress & cabinet trades, SEC filings, insider clusters, market data, and a disclosure-aware daily brief. Most clients need no API key. Hand them the URL and approve once in your browser.

Endpoint

https://www.mountainhead.ai/api/mcpStreamable HTTP

Auth is OAuth 2.1 (PKCE + dynamic client registration), so a compliant client discovers everything from the URL alone. Prefer a static Authorization: Bearer mh_live_… header for CI? That works everywhere too.

Browse the 22 tools

Connect

Pick your client.

Every config is verified against the vendor's own docs — the config key differs per client, and the wrong one fails silently. Switch to “API key” if you're wiring up CI or a server.

Claude

claude.ai, Claude Desktop and mobile, as a custom connector.

  1. 1Copy the server URL below.
  2. 2In Claude, open Customize → Connectors, click +, then Add custom connector.
  3. 3Name it Mountainhead, paste the URL and click Add.
  4. 4Click Connect, then sign in to Mountainhead and approve access.
  5. 5In a chat, open + → Connectors and switch Mountainhead on.
Open Claude connectors
url
https://www.mountainhead.ai/api/mcp

No key and no config file. Claude connects from Anthropic's cloud, so one connector works on the web, desktop and mobile apps.

Customize → Connectors lists Mountainhead as connected, and a new chat shows it under + → Connectors.

  • Claude's Free plan allows one custom connector. On Team and Enterprise plans an Owner adds Mountainhead under Organization settings → Connectors first, then each member clicks Connect.
  • To change a connector, remove it and add it again. Always paste the `www` URL exactly.

Then just ask

Your agent picks the right tool on its own — no tool names to memorize.

  • “Give me today's Mountainhead daily brief.”
  • “What has Congress been trading in NVDA lately?”
  • “Search Mountainhead signals for elon-musk.”

Tools

22 tools, grouped by job.

Every tool maps to a scoped /api/v1 endpoint, billed and rate-limited exactly like REST. Start with get_daily_brief and search_signals.

Start here

2 tools

The two calls that answer most questions on their own.

  • get_daily_brief

    One-call morning rollup: newly-disclosed congress PTRs, cabinet 278-T trades, Form 4 buys/sells, 13F moves, cluster + convergence signals, key dates, co-locations, and top news.

  • search_signals

    The primary product. Ranked, cited signals fusing flights, news, chatter, insider/congress/institutional trades, and co-locations into one feed. Filter by owner, ticker, kind, severity, or date.

Signals & entities

5 tools

Drill into a single signal, owner, or the news/chatter behind it.

  • get_signal

    Fetch one signal by its stable id.

  • list_owners

    Tracked-owner dossiers: entity type, category, bio, holdings, net worth.

  • list_news

    Normalized publisher feed with a closed source_type enum and free-text search.

  • get_insider_chatter

    Pre-indexed community sources for a tracked owner — higher-signal than generic news.

  • list_events

    Sanitized flight-event feed (airport-level only, no raw coordinates).

Markets

5 tools

Quotes, company terminals, macro, and SEC filings.

  • get_market_snapshot

    Batched quote/price/delta/volume for up to 10 tickers.

  • get_company_terminal

    Single-call company overview: fundamentals, earnings, filings, news, tracked owners.

  • get_macro_snapshot

    Curated FRED + OECD macro bundle across 7 themes.

  • list_sec_filings

    Recent SEC EDGAR submissions for a ticker or CIK.

  • read_sec_filing

    Plain-text body of an SEC filing, ready for summarization.

Political & financial intelligence

8 tools

Congress + White House trading, institutional moves, officials, and lobbying.

  • list_congress_trades

    STOCK Act House + Senate disclosures (transaction + filing dates).

  • get_congress_summary

    Leaderboard: most active traders, most-traded tickers, bipartisan convergence, disclosure lag.

  • list_official_activity

    Unified disclosures across US (STOCK Act + OGE 278/278-T executive branch), UK, CA, EU.

  • get_official_profile

    One-call dossier for an official: bio, committees, recent trades + holdings, 90-day stats.

  • list_insider_trades

    SEC Form 4 insider transactions by officers, directors, 10%+ owners.

  • list_insider_clusters

    Cross-ticker discovery of 3+ insiders trading the same direction, conviction-scored.

  • list_institutional_holdings

    13F-HR quarterly holdings from major fund managers.

  • list_lobbying

    LDA lobbying filings: registrant, client, amount, issue codes, targets.

Account

2 tools

Inspect the key and region preferences the connection is using.

  • get_me

    Plan, scopes, rate-limit window, and month-to-date usage for the key.

  • get_preferences

    The user's tracked regions (US, GB, CA, EU).

The live SSE stream, raw position tracks, and destination predictions are intentionally not exposed as tools. Need them? See the REST surface.

Troubleshooting

When it doesn't connect.

It says “needs authentication” and never connects.

That means discovery worked — you just haven't approved it yet. In Claude Code run /mcp, select Mountainhead, and choose Authenticate; a browser opens once. In the Claude app, click Connect on the connector. Other clients surface the same prompt in their MCP panel. Revoke or re-approve any time at Account → MCP.

The client connects but shows 0 tools, or the handshake times out.

You're almost certainly pointed at the apex domain. Use the www host — https://www.mountainhead.ai/api/mcp. The apex redirects to www, and MCP clients don't reliably follow redirects on the POST handshake.

401 Unauthorized on every call.

If you're using a static key it's missing, malformed, or revoked — the header value must keep the word Bearer, as in Bearer mh_live_…. Mint a fresh one at Account → API keys. On the browser-sign-in path, a 401 just means the token expired — re-run the authenticate step.

403 forbidden_scope on a specific tool.

Your plan lacks the scope that tool needs (e.g. read:filings for congress / insider / official tools). Check scopes and quota with the get_me tool, or see rate limits & errors.

Claude won't add or connect the connector.

Paste the exact www URL under Customize → Connectors → Add custom connector, then click Connect. Claude's Free plan allows one custom connector. On Team and Enterprise plans an Owner adds it under Organization settings → Connectors before members can connect. To change a connector, remove it and add it again.

Using a static API key in Claude Desktop?

The custom connector always signs in, so a key setup bridges through mcp-remote, which needs Node 18+. On the API-key config, keep the header split exactly as shown (no space in Authorization:${MH_KEY}, with Bearer … in env) and fully restart the app.

Wrong config key for my client.

It varies: url (Cursor, generic), httpUrl (Gemini CLI), and serverUrl (Antigravity) all mean the same endpoint. Use the exact block for your client above.

Prefer raw REST?

Every MCP tool has a matching /api/v1 endpoint with the same auth, metering, and scopes.

API docsInteractive reference

Stuck? Email yo@mountainhead.ai.