How to Give Hermes Agent Stock Data, a Watchlist, and Alerts

Hermes Agent can reason about a stock, but useful investment research needs a current data source, explicit timestamps, and a way to remember what the investor follows. A remote stock market MCP server gives Hermes a small set of named tools for that job. The agent can search a ticker, read current stock intelligence, inspect a watchlist, notice changes, and manage alert rules without receiving brokerage access.

This guide uses Stocksbrew for Agents as the concrete data layer. The same design applies to any careful financial MCP integration: facts come from tools, coverage gaps remain visible, account changes require narrow scopes, and the human confirms writes.

What Hermes can do after the connection

• Answer questions about any supported US ticker using available price, fundamentals, technicals, scores, and market context.
• Read the detailed Stocksbrew call, target, drivers, and risks when research exists.
• Explain that a detailed brief is missing without pretending that baseline data is a completed brief.
• Ask before adding a stock to Radar, then queue or refresh research through the same action.
• Read holdings and watched stocks, review changes since a saved cursor, and create or deactivate alert rules.

Stocksbrew exposes no trading tools. Hermes cannot place an order, connect a brokerage, or move money through this integration.

Connect Hermes Agent to Stocksbrew MCP

Add the remote Streamable HTTP MCP endpoint to the Hermes configuration. Use OAuth so the user sees the requested permissions and can revoke the connection later.

{
  "mcpServers": {
    "stocksbrew": {
      "url": "https://www.stocksbrew.online/api/mcp",
      "auth": "oauth"
    }
  }
}

Restart or reload Hermes after saving the MCP configuration, then complete the browser approval flow. Product versions can differ, so check the current Hermes MCP documentation if the settings shape in your installed release is different.

Verify the connection

Show my Stocksbrew Radar. Then explain anything that changed today. Include the response timestamp and freshness.

A successful answer proves more than tool discovery. It verifies authentication, the radar:read scope, and access to the current member's Radar. If Hermes lists tools but cannot call them, reconnect and inspect the OAuth scopes granted to the client.

Choose the smallest permission set

Start with the job, then grant the scopes needed for it:

• Research only: stocks:read and market:read.
• Radar companion: add radar:read.
• Full research assistant: add radar:write, alerts:read, and alerts:write.

Old personal tokens and old OAuth grants may contain only the original read scopes. Reconnect Hermes or issue a new token before expecting write tools to appear.

Ask Hermes about a stock outside Radar

A stock should not need to be in a watchlist before an agent can say anything useful. The stock intelligence tool first returns the available baseline record. It also returns a coverage object that distinguishes the factual state of generated research.

{
  "instrument": { "ticker": "CCL", "name": "Carnival" },
  "market_data": { "price": 27.81 },
  "coverage": {
    "status": "baseline_only",
    "tracked_in_radar": false,
    "has_baseline_data": true,
    "has_detailed_call": false,
    "next_action": {
      "action": "ask_to_add_to_radar",
      "tool": "add_to_radar"
    }
  }
}

The response lets Hermes answer the immediate question with honest limits. It can discuss current price position and available metrics, then ask whether the user wants a deeper brief.

User: What do we know about CCL?

Hermes: CCL is trading at $27.81. Stocksbrew has baseline price, technical, and fundamental context, but the detailed research brief is missing. Want me to add CCL to Radar and queue the brief?

After the user says yes, Hermes calls add_to_radar. The action is idempotent. If the ticker is already tracked but research is missing or failed, the same call can request a refresh without creating a duplicate Radar row.

Handle queued, running, and failed research

Generated research is asynchronous. Hermes should read the state instead of promising that a brief exists immediately. Stable states include ready, queued, running, baseline_only, no_sources, failed, and unavailable.

• queued or running: give the baseline answer and offer to check again later.
• no_sources: explain that a usable brief could not be created from available sources.
• failed: ask before refreshing through add_to_radar.
• ready: use the detailed call and retain its as-of and freshness fields.

This prevents the worst agent failure mode in financial research: converting missing data into confident prose.

Turn Radar into a daily research checkpoint

get_my_radar returns tracked stocks. get_radar_changes is the better tool for a recurring check because it accepts a cursor and returns only newer attention items.

Every weekday before the open, check my Stocksbrew Radar using the saved cursor. Summarize only new earnings, directive changes, risk changes, and tracked price levels. Save the new cursor only after the summary succeeds.

Cursor handling matters. Save the returned cursor after delivery, not before. If sending fails, keeping the old cursor allows the next run to see the same items again. Stable item IDs let the agent deduplicate changes that share a timestamp.

Create stock alerts through conversation

Hermes can create and deactivate price threshold email alerts. Earnings, RSI extremes, call changes, anomalies, and news updates come through get_radar_changes. Hermes should confirm the exact action before a write.

User: Alert me when NVDA falls below $190.

Hermes: I can create a below-$190 email alert for NVDA. Create it?

User: yes

Hermes then calls create_alert and reports the returned alert ID, active state, condition, and delivery type. get_my_alerts reads configured rules. It does not claim to be a stream of already delivered messages.

Use REST when MCP is not the right fit

A scheduled script can use the same operations through REST with a personal token. This is useful when Hermes is part of a larger deterministic automation or when its MCP release has a transport issue.

curl -H "Authorization: Bearer $STOCKSBREW_TOKEN"   "https://www.stocksbrew.online/api/v1/radar/changes?since=YOUR_CURSOR"

Keep personal tokens out of chat and logs. Store them in the agent's secret mechanism, rotate exposed credentials, and use OAuth for interactive clients whenever possible.

Hermes troubleshooting checklist

• Confirm the endpoint is exactly https://www.stocksbrew.online/api/mcp.
• Confirm the installed Hermes version supports remote MCP and OAuth.
• Reconnect if new Radar or alert tools are absent from an older grant.
• Check whether the Pro subscription is active.
• Respect HTTP 429 and the returned retry delay.
• Keep baseline data and generated research clearly separated in the answer.