"Star Trek" matching MCP tools:

• get_numerologyA

  Kundlit Vedic AstrologyA

  Returns a Vedic numerology reading from a date of birth alone: the mulank (root / psychic number, from the day of the month) and the bhagyank (destiny / life-path number, from the whole date), each with its ruling planet and traditional meaning, plus the classical lucky attributions -- numbers, colours, weekday, direction, gemstone. Optionally adds the Chaldean naam-ank when a name is supplied. Use this when the user asks about their number, life path or lucky colour/day/stone. It is NOT astrology and shares nothing with the chart tools: for a birth chart use get_janam_kundali, for a birth star use get_birth_details. Read-only deterministic arithmetic over the classical Chaldean number table -- no ephemeris is touched, and the result's Source line says so. No writes, no auth, at least 30 requests/min/IP per server instance. Birth time and place are not used, so none is asked for.

  ConnectorNo auth

• flag_emailA

  Mailbox MCPA

  Flag messages - the same star/flag marker Outlook and webmail show, and the state search_emails's `flagged` filter finds. Purely a marker for the user's own attention; it does not move, read, or otherwise change the messages, and it does not mark anything read. Pass the whole set in ONE call. Verified rather than assumed: the flags are read back off the server, so a message that could not be changed is named individually instead of being folded into a success. A uid only means something in the folder it came from, so pass `mailbox` when the uids did not come from INBOX. Flagging a message that is already flagged changes nothing and is not an error. unflag_email clears it, and is the more dangerous half of the pair.

  ConnectorOAuth

• departi_search_accommodationA

  Departi – Travel Compliance & Curated BookingA

  Searches bookable accommodation in a destination for given dates and returns a ranked list of stays, each with: name, property type, nightly price (in the requested currency), star rating, guest rating, key facilities (e.g. wifi, kitchen), a persona/traveler-type fit score, and a booking deep-link. Curated and scored for the traveller's persona and trip type — e.g. long-stay nomad apartments with kitchen + fast wifi vs weekend hotels. Use when the user needs a place to stay; for getting there use departi_search_transport, for things to do use departi_search_experiences. Returns an empty list if no inventory matches.

  ConnectorNo auth

• lookup_restaurantA

  Seemor Restaurant IntelligenceA

  Look up a specific restaurant by its Seemor ID. Returns grade, summary, cuisine, neighborhood, and other details. Use the fields parameter to request richer data (standard or premium; fully analyzed restaurants only). coverage_level 'full' rows carry a letter grade; 'basic' rows are Seemor quick reads: review-analysis bands (grade null, preliminary_band such as 'B-range') with a one-line tldr, graded from review analysis rather than star ratings; 'none' rows have no analysis yet. Use search_restaurants or find_restaurant first to get restaurant IDs. Use this for a single place the user asks about, not for every result of recommend.

  ConnectorNo auth

• explain_signalA

  mcpA

  Explain WHY a ticker has its current verdict — the factor attribution behind it. get_signal gives the verdict; get_trade_plan gives the execution; explain_signal gives the *reasoning*. It decomposes the quantum signal into the individual factors that drove the call — directional probability, expected upside, tail downside, confidence-band width, band calibration, market-condition gating, and risk-reward — each with a direction, a 0..1 contribution weight, the raw value, and a plain-English sentence. Pure transform over the same data get_signal returns; no new model run. TWO-SIDED BY DESIGN (north-star honesty): the response always carries a `dominant_factor` (the single biggest mover) AND `dissenting_factors` (what argues against the verdict). A stand-aside verdict (WAIT/AVOID) flags any strong directional read it overrode — so an agent sees the bull case it is declining, not just the conclusion. An empty dissent list means nothing material pushed the other way, NOT that the call is certain. Use this when an agent (or its user) needs to defend, audit, or reject a signal — never pitch a one-sided trade from the verdict alone. Args: ticker: Stock ticker symbol (e.g. "AAPL", "MSFT", "NVDA"). Case-insensitive. Returns a dict with verdict, factors[], dominant_factor, dissenting_factors, generated_at and disclaimer embedded in the payload.

  ConnectorNo auth

• get_safety_ratingA

  OpenDealer MCP ServerA

  Get NHTSA 5-Star Safety Ratings for a year/make/model (no VIN required). Answers questions like "is a 2023 RAV4 safe for my family" with: • Overall and crash-test star ratings (when published) • Rollover rating / possibility • NHTSA-evaluated ADAS availability (ESC, FCW, LDW) Ratings are model-year granular from the NHTSA NCAP cache. If no confident rating exists, the tool reports that honestly rather than guessing. For VIN-specific listing details use get_vehicle; for open recalls use check_recalls. CRITICAL: Only use the 'sourceUrl' field from the response for NHTSA links. NEVER invent URLs.

  ConnectorNo auth

• astro_planet_eventsA

  CycleCalcs AstronomyA

  The apparition cycle of the inferior planets as dated events: inferior and superior conjunctions, greatest eastern and western elongations, peak brightness (a Venus-only event: Mercury's brightness peaks behind the Sun where it cannot be seen), and the rare transits across the Sun. With no dates it also reports where each body is in its cycle right now: morning star or evening star, the conjunctions bounding the current apparition, and the live elongation, phase, magnitude and apparent size. The right tool for "when does Venus become the morning star", "when is Venus brightest", or "Mercury's next greatest elongation". For tonight's visibility of all eight planets use astro_planet_board. Conjunction instants use the classical heliocentric convention, named on each event.

  ConnectorNo auth

• post_vedic_astrology_kp_planets_intervalA

  Vedic Astrology and Kundli MCP Server by RoxyAPIA

  Calculate positions of all 9 planets (Sun through Saturn, Rahu, Ketu) at regular time intervals with full KP hierarchy: sign lord, star lord, sublord, and sub-sublord. Returns longitude, zodiac sign, nakshatra, sublord, sub-sublord, and KP number (1-249) for each planet at each timestamp. Ideal for tracking planetary motion, finding optimal muhurta windows, analyzing transit patterns, and building KP ephemeris tables. Maximum range of 7 days with 15-minute to 24-hour intervals.

  ConnectorNo auth

• search_hotelsA

  TripuckA

  Tripuck hotel search — real-time availability and prices for a city on given dates. Use this tool whenever the user asks about hotels, accommodation, or places to stay, e.g. "hotels in Antalya next weekend", "4-star hotel in Istanbul near Taksim", "İstanbul'da otel", "فندق في دبي", "Hotel in Berlin". Inputs: a city name plus optional check-in / check-out dates (YYYY-MM-DD) and guest counts. Supports structured filtering by minimum star rating, minimum guest-review score, and sorting. Returns live hotel options with price, star rating, review score and a thumbnail, each deep-linking to Tripuck.com for full details and booking. The LLM MUST infer the user language from the conversation and pass it via the `locale` parameter ("tr" Turkish, "en" English, "ar" Arabic, "az" Azerbaijani, "de" German, "ka" Georgian, "uz" Uzbek). All widget UI text and the text response are then returned in that language. If `currency` is not specified, a sensible default is picked from the locale (tr→TRY, en→USD, de→EUR, ar→USD, az→AZN, ka→GEL, uz→UZS).

  ConnectorNo auth

• check_late_arrivalsA

  Quotor — Home & Auto Insurance QuotesA

  Save-the-sale tool — call when the customer signals dissatisfaction with the current options ("too expensive", "let me think", "what else do you have", "is this the best you can do", "I'll check elsewhere", "can you do better"). Some carriers (Foremost STAR, etc.) run slower than the initial set and may have come back with a better rate while the customer was deliberating. This tool: 1. Pulls a fresh read of all rated carriers. 2. Compares the current cheapest bundle/LOB price to the original first-quoted best. 3. Returns has_improvement=true ONLY if a late carrier beats the original by >= $100/yr OR >= 5% — a threshold meaningful enough to justify interrupting the customer. CALL THIS ONLY WHEN: - check_quote_status has returned 'quoted' at least once (there's a baseline to compare). - The customer just expressed price resistance or hesitation (not a closed positive). - You have NOT called check_late_arrivals in the last 2 turns (don't spam). DO NOT CALL WHEN: - The customer is actively committing ("yeah let's go with A") — that's a close moment, not a wavering moment. - The customer hasn't seen the initial options yet. WHAT TO DO WITH THE RESULT: - has_improvement=true → narrate the improvement naturally ("Quick update — one more carrier just came in $X/yr cheaper. Want me to refresh your options?") and the iframe auto-updates with the new state. - has_improvement=false → acknowledge the customer's concern, pivot to value positioning against the options on the table. Don't bluff a "better one is coming" if it isn't. Use the carriers_still_pending count if relevant ("a couple more carriers are still finalizing in the background — I'll flag if anything comes in lower").

  ConnectorNo auth

• get_panchangA

  Kundlit Vedic AstrologyA

  Returns the Hindu panchang (daily Vedic almanac) for one date at one place: the five angas (tithi with paksha, nakshatra, yoga, karana, vara with its weekday lord) each with its end time, the lunar month in AMANTA reckoning with its adhika-masa flag (omitted entirely, never substituted, if the engine cannot supply the amanta month; plus the purnimanta month where the engine supplies it), sunrise/sunset/moonrise/moonset, abhijit muhurta, the auspicious choghadiya windows, and the inauspicious periods (rahu kaal, yamaganda, gulika kala). Use this for 'what is today's panchang / tithi / nakshatra' questions. If the user wants the FULL timing surface (all 16 choghadiya, the 24 horas, varjyam, bhadra, panchak, brahma muhurta) to choose a moment for an activity, call get_muhurta_timings instead. Nakshatra here is the DAY's nakshatra, not a person's birth star -- for that use get_birth_details. Read-only deterministic computation (Swiss Ephemeris, Lahiri ayanamsa); no writes, no auth, at least 30 requests/min/IP per server instance, plus a shared engine budget of at least 60/min/IP across all engine-backed tools. Any city worldwide; window times derive from that location's actual sunrise and sunset, so they differ city to city on the same date.

  ConnectorNo auth

• ashares_quoteA

  China StocksA

  Real-time quote(s) for Chinese A-share stocks by 6-digit code (Shanghai 6xxxxx, Shenzhen 0xxxxx/3xxxxx, STAR 688xxx, ChiNext 30xxxx, Beijing 8xxxxx/4xxxxx). Returns name, current price, change and change %, open, previous close, day high/low, volume, turnover, and the quote timestamp. Accepts one code or a comma-separated list. Example: ashares_quote({ symbols: "600519,000858" }) for Kweichow Moutai and Wuliangye. Source: Sina (keyless).

  ConnectorNo auth

• get_birth_detailsA

  HinduCalendar — panchang, festivals & muhurtaA

  Return birth star (nakshatra), birth name syllable (naam akshar / pada), Chandra rashi (Moon sign), and Lagna rashi (ascendant sign) for a child born at the given time and location — all from the app's own engine, so they match the HinduCalendar app's kundali exactly. Args: time: ISO 8601 datetime of birth (e.g. "2025-08-15T10:30:00Z"). Include timezone offset if known (e.g. "2025-08-15T10:30:00+05:30"). lat: Latitude of birth place in decimal degrees (e.g. 28.6139 for Delhi). lon: Longitude of birth place in decimal degrees (e.g. 77.2090 for Delhi). ayanamsa: "Lahiri" (Vedic sidereal, default) or "Sayan" (tropical). Returns: Dict with: - time (ISO) - ayanamsa - nakshatra: { index (1–27), name } - pada: { index (1–4), overall_index (1–108), naam_akshar (birth name syllable) } - chandra_rashi: { index (1–12), name } ← Moon sign - lagna_rashi: { index (1–12), name } ← Ascendant sign Plus a rendered South Indian kundali chart (PNG image).

  ConnectorNo auth

• recommend_travel_gearA

  VoyageHacksA

  Turn a trip description into a packing and gear kit drawn from the VoyageHacks travel gear catalog: one product per category, each with the published reason it was picked, its Amazon ASIN, a link to the Amazon product page and the guide that reviews it. Takes a plain-language trip summary ("10 days in Japan in October, carry-on only, long-haul red-eye, working remotely") plus optional structured hints (destination, trip length in days, season, activities, luggage constraint, traveler type, budget), all of which are used to weight which categories make the kit. Answers questions of the form "what should I pack for X", "what gear do I need for Y" and "I only have carry-on, what should I bring". It draws on the VoyageHacks editorial catalog, not a search of all of Amazon, and returns published picks only: prices, star ratings, review counts and stock are not available and are never returned, and it produces no clothing sizes and no itinerary. For one named product category, search_travel_gear is narrower. The Amazon links are affiliate links: VoyageHacks may earn a commission from qualifying purchases at no additional cost to the buyer, which should be disclosed when the links are presented.

  ConnectorNo auth

• unflag_emailA

  Mailbox MCPA

  Clear the flag/star marker on messages, restoring their unflagged state. Pass the whole set in ONE call. BE MORE CAREFUL WITH THIS ONE THAN WITH mark_unread: a flag is to-do state the person set by hand, one message at a time, and clearing it destroys a decision rather than a side effect - there is nothing to restore it from except their memory of what they had flagged. Clear the ones you were asked about and no others, and check the set first if the request was vague. Verified the same way the other flag tools are: the flags are read back off the server, so a message that could not be changed is named rather than assumed done. A uid only means something in the folder it came from, so pass `mailbox` when the uids did not come from INBOX. Clearing a flag that is not set changes nothing and is not an error.

  ConnectorOAuth

• create_chartA

  Birthstar Vedic Astrology MCPA

  Compute a full Vedic natal chart and cache it, returning a short handle. Call this FIRST. It returns a `chart_id` plus a small summary. Pass that chart_id to the other tools (get_grahas, get_houses, get_current_dasha, get_panchanga, get_yogas) to read specific parts of the chart without recomputing it. Args: dob: Date of birth, YYYY-MM-DD (proleptic Gregorian). tob: Time of birth, HH:MM or HH:MM:SS, 24-hour, local to `tz`. tz: IANA timezone name (e.g. "Asia/Kolkata") or fixed offset "+05:30". lat: Latitude in decimal degrees, North positive. lon: Longitude in decimal degrees, East positive. ayanamsha: Sidereal zero-point — lahiri, raman, kp, true_chitra, yukteshwar, or fagan_bradley. house_system: whole_sign, sripati, equal, placidus, or kp. node_type: "true" or "mean" lunar nodes. transit_date: YYYY-MM-DD the "now" questions are answered against — which dasha is running, where the transits are, whether Sade Sati is active. Defaults to today *in `tz`*, not in UTC, so a caller in Asia/Kolkata at 01:00 local gets their own date rather than the previous one. Set it to ask about another date; a chart made yesterday still answers as of yesterday. Returns the chart_id and the headline placements (birth star, moon sign, ascendant) — not the full document, which is far too large to return.

  ConnectorNo auth

• calculate_birth_starA

  Birthstar Vedic Astrology MCPA

  Compute just a person's Vedic birth star (nakshatra) and core anchors. A one-shot shortcut: use this when the birth star is the whole question. If you expect follow-up questions about the same person's chart, prefer create_chart, which caches the full chart behind a reusable handle. Args: dob: Date of birth, YYYY-MM-DD (proleptic Gregorian). tob: Time of birth, HH:MM or HH:MM:SS, 24-hour. tz: IANA timezone name (e.g. "Asia/Kolkata") or fixed offset "+05:30". lat: Latitude in decimal degrees, North positive. lon: Longitude in decimal degrees, East positive. ayanamsha: Sidereal zero-point. Default lahiri. Returns the birth star (Moon's nakshatra), its pada and ruling planet, the Moon sign, the ascendant, and the Sun's nakshatra.

  ConnectorNo auth

• get_listing_detailA

  cyclesite-mcp-serverA

  Full details for a specific bike listing on Cyclesite — specs, condition, frame number presence, photos, delivery, seller's city. Provide the URL slug returned by search_bikes or get_recent_listings. Example: after the user says 'tell me more about that 2022 Trek Domane', call this with the slug from the prior result.

  ConnectorNo auth

• make_enquiryA

  cyclesite-mcp-serverA

  Send an enquiry to a Cyclesite seller on the buyer's behalf. It's saved to the buyer's Cyclesite inbox and the seller is notified. Per-buyer-per-listing daily cap (2/day) prevents spam. Read the seller's reply with get_my_messages. Requires OAuth scope `enquiries:respond` (note: the scope name is shared with seller-side replies). Example: 'message the seller of that Trek and ask if they'd take £1,400 collection only in Manchester next Saturday'.

  Connector

  Destructive

  No auth

• search_filersA

  HoldingsIntelA

  Searches funds by name and returns canonical CIKs for discovery or disambiguation. WHEN TO USE: The user asks to find funds, a partial name may match several funds, or a workflow specifically needs a canonical CIK. Examples: - "Find funds with Pershing in the name" - "Which Renaissance filer did you mean?" WHEN NOT TO USE: - Call analyze_fund or clone_fund directly for an ordinary fund name; those tools resolve names themselves - Call compare_funds directly for ordinary fund names RETURNS: Up to the requested limit (maximum 10) of matching funds, each with CIK + name + AUM + star rating. VERIFICATION: Cite record-level `source_url` filing or disclosure links when present.

  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