"Real-time trading and chart data service" matching MCP tools:

• get_my_designA

  Human DesignA

  Get the account holder's own Human Design chart. If it reports that nothing is saved, that is the normal state of a new connection: ask for their birth date, time and place and call save_person with is_me=true, which answers with this same chart — no need to call this again.

  ConnectorOAuth

• save_personA

  Human DesignA

  Save a new person's birth data so their chart can be fetched later with get_person_design. is_me is required on every call and has no default — true for the account holder, false for anyone else. With is_me=true this becomes the account holder's own chart and the call answers with it — one call sets the account up and tells you their design; it also clears the flag on any previous 'me'. For the user themselves prefer it over calculate_chart, which remembers nothing. Ask how sure the user is of the birth time and pass birth_time_confidence; an unknown time is still worth saving, as 'unknown'. Create-only: an existing name fails and reports what is stored; relay that rather than retrying. Correcting someone already saved is update_person (or set_birth_time for their birth time alone), never a second save.

  ConnectorOAuth

• set_birth_timeA

  Human DesignA

  Correct a saved person's birth time, and how sure the user is of it. How a placeholder or half-remembered time becomes a real one without the user leaving the conversation. Only the time and its confidence change; date, place, name and the 'me' marker stay as saved. Take the confidence from what the user said, and call this only for a time they gave you; to try a time out, call compare_birth_times, which changes nothing. Answers with the payoff: an 'exact' time returns the refreshed chart, an approximate one returns the birth-day sweep re-scored against the new time. Either way the result carries a `birth_time_change` block: say what moved and what held.

  ConnectorOAuth

• drawing_addA

  BasisA

  Draw on the chart. Points are {time, price} in chart coordinates — time in seconds, matching the candle timestamps a data handle reports. A horizontal line needs one point; a trendline or box needs two. Both numbers must be copied from a tool result — a summary's max with its maxAt, a crossing with its time — never read off your own prose or carried over from a different computation. The result echoes back what was drawn: check it against the figures you are about to quote, because a line that disagrees with the paragraph beside it is worse than no line. Changes the chart you are building; call chart_link when you are done so the person can open it.

  ConnectorNo auth

• asterwise_get_crystal_recommendations_natalA

  AsterwiseA

  Recommends crystals from a Vedic natal chart using house lordship rules for gem selection. This is the only API that derives crystal recommendations from a computed natal chart — not from zodiac sign or chakra preference. WORKFLOW: BEFORE: None — this tool internally computes the natal chart. No separate natal chart call required. AFTER: asterwise_get_crystal — get full detail (hardness, origins, affirmation, full caution text) on any recommended crystal by slug. AFTER: asterwise_get_remedies — broader classical remedial programme alongside gem recommendations. INPUT CONTRACT: Standard BirthData (date, time, lat, lon, timezone, ayanamsa). Defaults to Lahiri ayanamsa. time (required): Ascendant (Lagna) is time-sensitive. Inaccurate birth time changes the Lagna → changes all house lords → changes recommendations entirely. DO NOT CONFUSE WITH: asterwise_get_gemstone_recommendations — also a chart-based gem endpoint but uses a different engine (Atmakaraka + role-based prescription vs house lordship scoring); returns gem names not crystal database entries; does not include match_score or match_reasons. asterwise_get_crystal_recommendations — recommends crystals by zodiac sign, chakra, or intention keyword (no natal chart computation; Western metaphysical matching, not classical Jyotish). asterwise_get_crystal_by_planet — lists all crystals for a Vedic planet without house context — use this for reference, not prescription. Full output and error contract: https://docs.asterwise.com/mcp/tools/get-crystal-recommendations-natal/

  ConnectorOAuth

• get_solana_market_statusA

  TWZRD Agent IntelligenceA

  Health probe for the Solana Market API data backend. Call this to gate or degrade gracefully BEFORE the other get_solana_market_* tools: it does a short-timeout hit on the data service and reports whether it is reachable, so an agent can tell "market has no data" from "service is down" without failing a real query. Free discovery tool. When the market data service exposes /status, the response includes prod_key_configured, data_first_available, and an actionable note describing what to configure for full on-chain visibility.

  ConnectorNo auth

• asterwise_get_crystal_recommendations_natalA

  AsterwiseA

  Recommends crystals from a Vedic natal chart using house lordship rules for gem selection. This is the only API that derives crystal recommendations from a computed natal chart — not from zodiac sign or chakra preference. WORKFLOW: BEFORE: None — this tool internally computes the natal chart. No separate natal chart call required. AFTER: asterwise_get_crystal — get full detail (hardness, origins, affirmation, full caution text) on any recommended crystal by slug. AFTER: asterwise_get_remedies — broader classical remedial programme alongside gem recommendations. INPUT CONTRACT: Standard BirthData (date, time, lat, lon, timezone, ayanamsa). Defaults to Lahiri ayanamsa. time (required): Ascendant (Lagna) is time-sensitive. Inaccurate birth time changes the Lagna → changes all house lords → changes recommendations entirely. DO NOT CONFUSE WITH: asterwise_get_gemstone_recommendations — also a chart-based gem endpoint but uses a different engine (Atmakaraka + role-based prescription vs house lordship scoring); returns gem names not crystal database entries; does not include match_score or match_reasons. asterwise_get_crystal_recommendations — recommends crystals by zodiac sign, chakra, or intention keyword (no natal chart computation; Western metaphysical matching, not classical Jyotish). asterwise_get_crystal_by_planet — lists all crystals for a Vedic planet without house context — use this for reference, not prescription. Full output and error contract: https://docs.asterwise.com/mcp/tools/get-crystal-recommendations-natal/

  ConnectorOAuth

• update_personA

  Human DesignA

  Correct a person already saved: their name, birth data, or which of them is the account holder. Call it whenever the user says a saved record is wrong — "that is not my chart", "that was my child's", a corrected birth date, or the name they want to be called. Addressed by person_id ('me', or an id from list_people), never by name: two people on one account can share a name, and the row that is wrong nearly always carries the user's own. Pass only the fields that change. Everything else stays exactly as saved, and the result names what moved and what held — say that and no more. is_me=true makes this person the account holder and clears the marker wherever it was, which is the fix when the account holds the wrong person entirely. Answers with the payoff when birth data moved: the refreshed chart for an 'exact' time, the birth-day sweep for an approximate one. Birth data includes the confidence — a time that just became 'exact' is a chart that just became readable — so a confidence-only correction comes back with the chart too. A rename alone returns the confirmation and no chart. To change only a birth time, prefer set_birth_time, which reports how much of the chart that time settles.

  ConnectorOAuth

• varrd_aiA

  VARRD — Statistically Validated Trading Edges + AI Research EngineA

  Talk to VARRD AI (~$0.25/turn). Describe any trading idea in plain language and the system handles everything — loading decades of market data, charting your pattern, running statistical tests, backtesting with stops, and generating exact trade setups. MULTI-TURN: First call creates a session. Keep calling with the same session_id, following context.next_actions each time. 1. Your idea -> VARRD charts pattern 2. 'test it' -> statistical test (event study or backtest) 3. 'show me the trade setup' -> exact entry/stop/target prices HYPOTHESIS INTEGRITY (critical): VARRD tests ONE hypothesis at a time — one formula, one setup. Never combine multiple setups into one formula or ask to 'test all' — each idea must be tested as a separate hypothesis for the statistics to be valid. Say 'start a new hypothesis' between ideas to reset cleanly. - ALLOWED: Test the SAME setup across multiple markets ('test this on ES, NQ, and CL') — same formula, different data. - NOT ALLOWED: Test multiple DIFFERENT formulas/setups at once — each is a separate hypothesis requiring its own chart-test-result cycle. If ELROND council returns 4 setups, test each one separately: chart setup 1 -> test -> results -> 'start new hypothesis' -> chart setup 2 -> etc. KEY CAPABILITIES you can ask for: - 'Use the ELROND council on [market]' -> 8 expert investigators - 'Optimize the stop loss and take profit' -> SL/TP grid search - 'Test this on ES, NQ, and CL' -> multi-market testing - 'Simulate trading this with 1.5 ATR stop' -> backtest with stops EDGE VERDICTS in context.edge_verdict after testing: - STRONG EDGE: Significant vs zero AND vs market baseline - MARGINAL: Significant vs zero only (beats nothing, but real signal) - PINNED: Significant vs market only (flat returns but different from market) - NO EDGE: Neither significant test passed TERMINAL STATES: Stop when context.has_edge is true (edge found) or false (no edge — valid result). Always read context.next_actions.

  ConnectorNo auth

• chart_factsA

  caelus-mcpA

  A chart's validated facts as ranked, citable atoms for interpretation. Each fact has a stable id (e.g. "aspect:moon~neptune:conjunction"), the bodies it concerns, a salience score (luminaries, angular placements, the chart ruler, tight/hard aspects, configurations rank high), and a plain-language statement. Facts span placements, aspects, configurations, the structural signature, dispositors and receptions, a body's tight conjunction with a bright fixed star (e.g. "star:jupiter:Sirius"), and the Part of Fortune and Spirit (e.g. "lot:fortune"). Read the facts, write the interpretation in your own words, and cite the [id] each statement rests on — do not introduce facts not listed. Returns the ranked facts plus a ready-to-interpret `brief`. By default a real birth chart: pass date+lat+lon. The chart's grounding is first-class via `realm` (what it is: observed/forecast/fictional/mythic/archetypal/…) and the time: an exact `date`, an uncertain `earliest`+`latest` range (the brief then frames it as provisional and trusts the Moon/angles/houses less), `constraints` for an archetypal chart with no time (synthesized via the compiler), or a full structured `when` (relative-to-another-event or a narrative calendar). A `when` of kind `relative` looks its `anchorId` up in `anchors` (a map of id → UTC instant supplied in the request). Omit lat+lon for a placeless chart (nominal houses).

  ConnectorNo auth

• book_window_cleaningA

  Sonlight Window CleaningA

  Reserve a REAL calendar slot with Sonlight Window Cleaning. The customer immediately receives an SMS + email confirmation and a technician arrives at the chosen time. Payment is collected after service. Nothing is charged at booking. ALWAYS confirm name, phone, address, selected services, date, and time with the user before calling this. Requires a prior get_quote for the same address (prices are re-validated server-side).

  Connector

  Destructive

  No auth

• particle_podcast_get_rankingsA

  particle-proA

  Podcast chart rankings from Apple Podcasts and Spotify, in four modes: - `chart` (default): the current chart for a source/country/category slot, or — with `podcast_slug` — every chart slot that podcast currently holds. - `movers`: the biggest rank changes over `window_days` (risers, fallers, debuts, exits). - `history`: past snapshots for a chart slot, or — with `podcast_slug` — one podcast's chart history over time. - `slots`: the valid slot values — every source, country, and category_slug with live chart data — so filter values are discovered, not guessed. `source` narrows the country/category listings; other filters are ignored. Each row carries the matched `podcast_slug` when the chart entry is in the catalog — feed it into `particle_podcast_resolve` or any podcast tool. For a single podcast's at-a-glance chart presence, `particle_podcast_resolve` with `include: ["rankings"]` is one call instead of two.

  ConnectorOAuth

• calculate_chartA

  Human DesignA

  Calculate a Human Design chart from birth data for someone who is not saved. Nothing is stored. A saved person's chart comes from get_person_design, never retyped from their birth data. State in your reply the date and time the chart was calculated from. When the user says how sure they are of the time — "around three", "exactly 14:30" — pass birth_time_confidence, and the chart states the verdict a saved person's chart states.

  ConnectorOAuth

• GetOptionContractA

  equiblesA

  Get the full snapshot for ONE option contract by its OCC symbol (e.g. O:AAPL260724C00110000): greeks, implied volatility, open interest, the latest daily price, and bid/ask when the plan entitles quotes. Last, day range and volume name the provider's trading-session timestamp when supplied and otherwise mark it unknown; open interest names its separate effective date when supplied; implied volatility and greeks are the provider's model values computed at fetch time and can differ slightly from a chain response. Bid/ask use consolidated real-time OPRA on Pro and a 15-minute delayed indicative feed on Plus; the Free plan covers end-of-day data only and is answered with an upgrade note.

  ConnectorNo auth

• plot_line_chartA

  Math MCP LearningA

  Create a line chart from data points (requires matplotlib). Note: Use for general XY data. For time-series price data with optional moving average, use plot_financial_line instead. Examples: plot_line_chart([1, 2, 3, 4], [1, 4, 9, 16], title="Squares") plot_line_chart([0, 1, 2], [0, 1, 4], color='red', x_label='Time', y_label='Distance')

  ConnectorNo auth

• stocktoken_listA

  AI Agent Tokenized Stock OSB

  AI Agent Tokenized Stock OS: list canonical tokenized stocks (Robinhood Stock Tokens), ETFs, USDG, and WETH on Robinhood Chain ID 4663. Use for AI agents trading tokenized equities/RWAs. Do NOT use for US brokerage equities (use Robinhood Trading MCP). Only registry addresses are real tokenized stocks.

  ConnectorNo auth

• stocktoken_listA

  AI Agent Tokenized Stock OSC

  AI Agent Tokenized Stock OS: list canonical tokenized stocks (Robinhood Stock Tokens), ETFs, USDG, and WETH on Robinhood Chain ID 4663. Use for AI agents trading tokenized equities/RWAs. Do NOT use for US brokerage equities (use Robinhood Trading MCP). Only registry addresses are real tokenized stocks.

  ConnectorNo auth

• relay_crypto_newsA

  agentdata-nlA

  Real-time crypto market news with sentiment analysis and top headlines ranked by importance, for $0.01 per call. One request, no parameters needed — get the latest market-moving stories as structured JSON, ready for trading agents and research pipelines. Relayed live from a proven upstream source; if the source is down you get a 503 and pay nothing. Pay per call in USDC on Base — no account, no API key.

  ConnectorNo auth

• calendar.macro_ddayA

  AlphaPipeline Agent MCPA

  Use this tool when an agent plans trading schedules around major US macroeconomic volatility, specifically days remaining until FOMC rate decisions, CPI prints, or NFP jobs reports. Zero-dependency static 2026 macro calendar with 100% uptime and no upstream failure risk. Do not use for real-time market price data or economic forecast consensus figures. No input parameters. Paid in USDC on Base.

  ConnectorNo auth

• calendar.macro_ddayA

  alphapipelineA

  Use this tool when an agent plans trading schedules around major US macroeconomic volatility, specifically days remaining until FOMC rate decisions, CPI prints, or NFP jobs reports. Zero-dependency static 2026 macro calendar with 100% uptime and no upstream failure risk. Do not use for real-time market price data or economic forecast consensus figures. No input parameters. Paid in USDC on Base.

  ConnectorNo auth

• asterwise_get_natal_chartA

  AsterwiseA

  Computes the full sidereal natal chart from BirthData and returns planet rows, houses, aspects, arudhas, upapada, bhava cusps, and avakhada metadata. WORKFLOW: BEFORE: None — this tool is standalone. AFTER: RECOMMENDED — asterwise_get_yogas — layer classical combinations after the base chart exists. INPUT CONTRACT: BirthData enforces date YYYY-MM-DD, time HH:MM, lat -90..90, lon -180..180, ayanamsa enum locally (Pydantic). Unknown birth time may be entered as time='00:00' without error; lagna-sensitive results are then unreliable and callers must handle that — the API does not flag it. DO NOT CONFUSE WITH: asterwise_get_divisional_chart — sixteen vargas only, not the primary radix bundle returned here. Full output and error contract: https://docs.asterwise.com/mcp/tools/get-natal-chart/

  ConnectorOAuth