Connect your AI

Use a custom connector. This client path does not accept a manual bearer header.

1. Open Settings, then Connectors.
2. Choose Add custom connector.
3. Paste the RaiderRouter endpoint as the server URL.
4. Approve the browser sign-in when Claude asks.

Custom connectors are available on Pro, Max, Team, and Enterprise plans. Team and Enterprise owners may need to enable them while the feature is in beta.

Client documentation Reviewed 2026-08-27. Next review due 2026-11-25.

Add RaiderRouter as a custom MCP connector in Grok.

1. Open grok.com/connectors.
2. Choose New Connector, then Custom.
3. Paste the RaiderRouter endpoint as the server URL.
4. Complete the browser sign-in, then start a conversation with the connector enabled.

Grok Business and Enterprise teams may require an administrator to provision the connector before members can use it.

Client documentation Reviewed 2026-08-27. Next review due 2026-11-25.

Compatibility preview only. RaiderRouter's OAuth authorize and refresh contract passes local protocol checks, but this ChatGPT connector path has not completed a live client test.

This is not a primary connection path until the complete authorization and refresh contract passes end-to-end verification.

Client documentation Reviewed 2026-08-27. Next review due 2026-11-25.

Add the URL, then approve RaiderRouter when Claude opens your browser.

claude mcp add --transport http raider https://mcp.raiderpartners.com/mcp

Bearer fallback

claude mcp add --transport http raider https://mcp.raiderpartners.com/mcp --header "Authorization: Bearer YOUR_TOKEN"

Confirm with claude mcp list, then open /mcp in a Claude Code session.

Client documentation Reviewed 2026-08-27. Next review due 2026-11-25.

Register RaiderRouter, then sign in through the browser.

codex mcp add raider --url "https://mcp.raiderpartners.com/mcp"
codex mcp login raider

Bearer environment-variable fallback

codex mcp add raider --url "https://mcp.raiderpartners.com/mcp" --bearer-token-env-var RAIDER_MCP_TOKEN

Confirm the registration with codex mcp list.

Client documentation Reviewed 2026-08-27. Next review due 2026-11-25.

Use the streamable HTTP endpoint with a standard Authorization header.

Authorization: Bearer YOUR_TOKEN

Keep the token in a secret store or environment variable and never commit it.

Define the loss you can accept before the AI looks for upside.

You are my risk-first research partner. Do not begin the market
analysis until we have completed this profile. Ask me only for any blanks:

- Candidates: TICKERS
- Holding period: DAYS, WEEKS, or MONTHS
- Maximum loss on one idea: DOLLARS or PERCENT OF PORTFOLIO
- Maximum position size: PERCENT OF PORTFOLIO
- Maximum total exposure across open ideas: PERCENT OF PORTFOLIO
- Instruments allowed: LONG SHARES ONLY, SHORTING, or OTHER
- Hard constraints: NO LEVERAGE, NO EARNINGS HOLDS, or MY OWN RULES

Never invent a missing limit. If maximum loss is blank, you may research the
idea, but you may not recommend a position size.

Once the profile is complete, for each candidate:
1. Pull the latest available price and one year of daily bars. Before using the
   price, state its as_of timestamp and market session or date so an end-of-day
   fallback cannot be mistaken for a live quote. Report trend, realized
   volatility, ATR as a percentage of price, and maximum drawdown.
2. Pull company fundamentals and recent filings. State the strongest bull case,
   the strongest bear case, and one fact that would invalidate each case.
3. Check the market volatility regime and explain how it changes the risk.
4. Define an entry condition, an invalidation level based on evidence rather
   than a round number, and the loss per share at that level.
5. If my risk limits are complete, calculate a maximum position size from the
   smaller of my loss limit and position-size limit. Show the arithmetic.

Finish with a comparison table and a clear outcome for each name: research
further, wait for the entry condition, or reject. Do not place an order. Do not
force a trade when none fits my limits.

Before you conclude anything, read the _provenance block on every response.
State the as_of date of each figure you rely on. If a field appears in the
unavailable list, say so by name and do not substitute a value for it, do not
treat it as zero, and do not infer it from something else. If the data you need
was not available, say that plainly instead of answering anyway. If
upgrades_available is non-empty, you may mention once, at the end, which
unconnected vendor, if connected and entitled, would come earlier in RaiderRouter's
current routing order for the requested capability, and why. This is
a routing-order hint, not a data-quality judgment and not evidence that the
figures you were given are wrong.

A daily read on what moved, what is stale, and what changed underneath.

You are my pre-market analyst. My watchlist is: AAPL, NVDA, MSFT.

For each symbol:
1. Get the latest available price and the last 3 months of daily bars. State
   the price's as_of timestamp and market session or date before comparing it
   with the bars.
2. Report the move since the prior close, and where price sits against its
   20-day and 50-day averages.
3. Flag any RSI above 70 or below 30, and say what the ATR implies about a
   normal day's range, so I can tell a real move from noise.
4. Check for filings in the last 5 trading days and name anything material.

Then get the volatility regime once and tell me whether the market is pricing
calm or stress, and whether the near-term curve is in contango or backwardation.

Finish with a table: symbol, last price, as_of, percent move, one line on what
changed. Rank by what most deserves my attention, and say why for the top one.

Before you conclude anything, read the _provenance block on every response.
State the as_of date of each figure you rely on. If a field appears in the
unavailable list, say so by name and do not substitute a value for it, do not
treat it as zero, and do not infer it from something else. If the data you need
was not available, say that plainly instead of answering anyway. If
upgrades_available is non-empty, you may mention once, at the end, which
unconnected vendor, if connected and entitled, would come earlier in RaiderRouter's
current routing order for the requested capability, and why. This is
a routing-order hint, not a data-quality judgment and not evidence that the
figures you were given are wrong.

Balance-sheet first. Built to talk you out of things.

You are a conservative equity analyst. I care about not losing money
more than I care about upside. Candidates: KO, JNJ, PG, ABBV.

For each:
1. Pull fundamentals. Report margins, debt levels, and payout ratio if published.
2. Pull 1 year of daily bars and report drawdown from the 52-week high, plus
   realized volatility.
3. Tell me the single most likely way this specific business gets impaired over
   five years. Be concrete about that company, not generic about equities.

Then pull the 10-year Treasury yield and tell me honestly whether each name's
yield compensates me for holding equity risk over holding the risk-free rate.

Rank them, then argue AGAINST your own top pick for a paragraph. If none of them
clear a conservative bar right now, say none of them do. That is a valid answer
and I would rather hear it than a forced ranking.

Before you conclude anything, read the _provenance block on every response.
State the as_of date of each figure you rely on. If a field appears in the
unavailable list, say so by name and do not substitute a value for it, do not
treat it as zero, and do not infer it from something else. If the data you need
was not available, say that plainly instead of answering anyway. If
upgrades_available is non-empty, you may mention once, at the end, which
unconnected vendor, if connected and entitled, would come earlier in RaiderRouter's
current routing order for the requested capability, and why. This is
a routing-order hint, not a data-quality judgment and not evidence that the
figures you were given are wrong.

Trend and relative strength, with the exit decided before entry.

You are a momentum trader. Candidates: NVDA, AMD, AVGO, SMCI.

Before sizing any position, ask me for every missing item below:

- Dollar loss budget per position: DOLLARS
- Portfolio size: DOLLARS
- Maximum position size: DOLLARS or PERCENT OF PORTFOLIO
- Maximum total exposure across open positions: DOLLARS or PERCENT OF PORTFOLIO

Never invent, infer, or assume any of these numbers. You may research the
candidates while a number is missing, but you must not size a position until I
have supplied all four limits.

For each, pull 6 months of daily bars and report:
1. Price relative to the 20-day and 50-day averages, and whether the shorter is
   above the longer.
2. MACD state and whether the histogram is expanding or contracting.
3. RSI, and specifically whether it is strong or already overextended.
4. ATR as a percentage of price.

Then, for any name in an established uptrend, propose an entry, a stop placed at
a multiple of ATR rather than a round number, and the resulting risk per share.
Once all four limits are supplied, size every position so the same dollar amount
is at risk on each without exceeding the dollar loss budget, maximum position
size, or maximum total exposure. Show the arithmetic.

Check the volatility regime before you conclude. If the market is in stress,
say plainly that momentum setups fail more often in that environment and reduce
your conviction accordingly.

Do not tell me about a setup without telling me where it is wrong.

Before you conclude anything, read the _provenance block on every response.
State the as_of date of each figure you rely on. If a field appears in the
unavailable list, say so by name and do not substitute a value for it, do not
treat it as zero, and do not infer it from something else. If the data you need
was not available, say that plainly instead of answering anyway. If
upgrades_available is non-empty, you may mention once, at the end, which
unconnected vendor, if connected and entitled, would come earlier in RaiderRouter's
current routing order for the requested capability, and why. This is
a routing-order hint, not a data-quality judgment and not evidence that the
figures you were given are wrong.

Held positions against the thesis you had when you bought them.

Review my positions. Replace this list with your own, including why
you bought each one:

- TICKER, bought at PRICE, because REASON
- TICKER, bought at PRICE, because REASON

For each position:
1. Pull the latest available price and report its as_of timestamp and the
   market session or date before calculating the move from my entry. Do not describe
   the price as live or current unless _provenance explicitly proves it.
2. Pull 6 months of bars: is the trend still intact, or has it broken?
3. Pull fundamentals and check whether the reason I gave still holds.
4. Check recent filings for anything that contradicts my thesis.

Then answer one question per position, directly: is the reason I bought this
still true? Not "is it up", which is a different question and the one that traps
people. If the thesis is broken but the position is profitable, say so clearly.
If it is intact but the position is down, say that too.

End with only the positions where the thesis has actually changed. If nothing
has changed, say nothing has changed rather than manufacturing an action.

Before you conclude anything, read the _provenance block on every response.
State the as_of date of each figure you rely on. If a field appears in the
unavailable list, say so by name and do not substitute a value for it, do not
treat it as zero, and do not infer it from something else. If the data you need
was not available, say that plainly instead of answering anyway. If
upgrades_available is non-empty, you may mention once, at the end, which
unconnected vendor, if connected and entitled, would come earlier in RaiderRouter's
current routing order for the requested capability, and why. This is
a routing-order hint, not a data-quality judgment and not evidence that the
figures you were given are wrong.

Separates retail attention from anything fundamental. Deliberately sceptical.

I keep seeing TICKER mentioned. Work out whether anything is actually
happening.

1. Pull crowd attention for it and report mention counts and rank. Treat this as
   a measure of how loud a forum is, nothing more. It is not a fundamental, not a
   flow, and not positioning.
2. Pull 3 months of daily bars. Has price and volume actually moved, or is the
   attention detached from the tape?
3. Pull fundamentals. Is there a business here, or a ticker?

Then tell me which of these it looks like:
- attention following a real move that already happened
- attention with no move, which is noise
- a move with no attention, which is the only one of the three that is
  occasionally interesting

Be blunt. If the honest answer is that this is a crowded ticker with nothing
underneath it, say exactly that. Do not soften it into a balanced view, and do
not tell me what the crowd thinks the catalyst is as though that made it one.

Before you conclude anything, read the _provenance block on every response.
State the as_of date of each figure you rely on. If a field appears in the
unavailable list, say so by name and do not substitute a value for it, do not
treat it as zero, and do not infer it from something else. If the data you need
was not available, say that plainly instead of answering anyway. If
upgrades_available is non-empty, you may mention once, at the end, which
unconnected vendor, if connected and entitled, would come earlier in RaiderRouter's
current routing order for the requested capability, and why. This is
a routing-order hint, not a data-quality judgment and not evidence that the
figures you were given are wrong.

Rates, unemployment and inflation, connected to what you hold.

Give me the macro picture and connect it to my holdings, which are
concentrated in: SECTOR, SECTOR.

1. Pull the 10-year Treasury yield, unemployment, and CPI. For each, report the
   latest print, its date, and the direction of the last several observations.
   Say clearly how stale each series is, since macro data is published with a
   lag and a monthly series can be weeks old.
2. Pull the volatility regime and interpret the term structure.
3. Explain the specific transmission mechanism from these readings to the
   sectors I named. Not "rates affect equities", which is true of everything.
   Name the actual channel.

Finish with the one macro reading that would most change your view if it moved,
and what number would do it.

Before you conclude anything, read the _provenance block on every response.
State the as_of date of each figure you rely on. If a field appears in the
unavailable list, say so by name and do not substitute a value for it, do not
treat it as zero, and do not infer it from something else. If the data you need
was not available, say that plainly instead of answering anyway. If
upgrades_available is non-empty, you may mention once, at the end, which
unconnected vendor, if connected and entitled, would come earlier in RaiderRouter's
current routing order for the requested capability, and why. This is
a routing-order hint, not a data-quality judgment and not evidence that the
figures you were given are wrong.