"Information on the Theory of Evolution" matching MCP tools:

• compare_analytical_vs_simulatedA

  QueueSimA

  Run the same M/M/c configuration through BOTH the closed-form Erlang-C formula AND the discrete-event simulator, returning a side-by-side comparison with deltas. Use this when the user is validating QueueSim's engine against textbook values, learning queueing theory by watching simulation converge on the formula, or auditing a result that 'feels off' — agreement within ~5%% is the canonical sanity check for an M/M/c run. Pure-Exponential M/M/c only; the closed-form Erlang-C is undefined for other service distributions. Large deltas usually mean the simulation run was too short for steady-state — raise simulationDays. ANTI-FABRICATION: both sides come from real computation — closed-form is deterministic, simulation is stochastic but engine-backed. Quote both verbatim. Do not synthesize an 'average of the two' or recompute the formula from training-data recall.

  ConnectorNo auth

• find_compatible_keysA

  FreqBlog Music MetadataA

  Given a Camelot key (e.g. "8A", "12B"), return the harmonically compatible keys for DJ mixing — the same key, the relative major/minor, and the adjacent +/-1 keys on the Camelot wheel. With `extended=true` also returns the +7/-7 energy-boost / energy-drop keys. Pure music theory — no catalog lookup and no quota cost. Pair with find_tracks_by_key to then pull actual tracks in each compatible key.

  ConnectorNo auth

• interpret_resultA

  QueueSimA

  Given an M/M/c configuration (arrivalRate, serviceRate, servers) and optionally an observed average wait, returns a queueing-theory framed interpretation: where you sit on the utilization curve, what ρ means in plain language, what one more or fewer server would qualitatively do, and which complexity factors (priority, abandonment, skills routing) might be hiding in real data the M/M/c model can't see. Use this to TEACH while answering — when the user wants context around a number, not just the number itself. Pure text computation, no simulation, no RNG — deterministic output.

  ConnectorNo auth

• get_liquidation_mapA

  LiquidVision — Crypto Derivatives DataA

  [modeled, RISK AHEAD, CEX, now] ESTIMATED open leveraged positions on Binance/Bybit/OKX per price bin at their liquidation price, from candles and open-interest deltas (the CEXs do not publish positions). Current snapshot only; for its evolution over time use get_liquidation_heatmap; for REAL positions use get_hl_liquidation_map (Hyperliquid) or get_lighter_liquidation_map (Lighter); for what already got liquidated use the PAST tools. Returns notional per bin split by leverage tier (5/10/20/25/50/100x) and by exchange, plus cumulative long/short curves from the current price outward. exchange: all | binance | bybit | okx. range: 12h | 1d | 3d | 7d. It ranks levels ("if price reaches this level, how much is there": top quarter of traded levels holds ~30-32% of liquidated USD, chance ~24%); it does NOT predict where price will go. Live scoring: get_accuracy.

  ConnectorNo auth

• get_liquidation_mapA

  LiquidVision — Crypto Derivatives DataA

  [modeled, RISK AHEAD, CEX, now] ESTIMATED open leveraged positions on Binance/Bybit/OKX per price bin at their liquidation price, from candles and open-interest deltas (the CEXs do not publish positions). Current snapshot only; for its evolution over time use get_liquidation_heatmap; for REAL positions use get_hl_liquidation_map (Hyperliquid) or get_lighter_liquidation_map (Lighter); for what already got liquidated use the PAST tools. Returns notional per bin split by leverage tier (5/10/20/25/50/100x) and by exchange, plus cumulative long/short curves from the current price outward. exchange: all | binance | bybit | okx. range: 12h | 1d | 3d | 7d. It ranks levels ("if price reaches this level, how much is there": top quarter of traded levels holds ~30-32% of liquidated USD, chance ~24%); it does NOT predict where price will go. Live scoring: get_accuracy.

  ConnectorNo auth

• design-it-twiceA

  ClairvoyanceA

  Generates and compares at least two fundamentally different design alternatives on concrete criteria before committing. Use when the user asks to design something twice, or before committing to any significant design of classes, modules, APIs, or architecture. Also use when asked how to structure or architect a feature, or when writing the design or alternatives section of an RFC, design doc, or ADR. Not for judging strategic vs. tactical investment in existing code (use strategic-mindset) or whether a change degrades design (use code-evolution).

  ConnectorNo auth

• address_related_addressesA

  NansenA

  Get information about related addresses of an input address. Note: This only includes the the "special" connections 'First Funder', 'Signer', 'Previous Signer', 'Multisig Signer of', 'Previous Multisig Signer of', 'Deployed via', 'Deployed by', 'Deployed Contract', 'Created Contract', 'Created by'. To get related wallets, also check address counterparties. First funder exchange withdrawal address does usually NOT belong to the same entity as the address, only deposit addresses. Only information is that it has been funded by the exchange.

  ConnectorNo auth

• address_related_addressesA

  NansenA

  Get information about related addresses of an input address. Note: This only includes the the "special" connections 'First Funder', 'Signer', 'Previous Signer', 'Multisig Signer of', 'Previous Multisig Signer of', 'Deployed via', 'Deployed by', 'Deployed Contract', 'Created Contract', 'Created by'. To get related wallets, also check address counterparties. First funder exchange withdrawal address does usually NOT belong to the same entity as the address, only deposit addresses. Only information is that it has been funded by the exchange.

  ConnectorNo auth

• get_ticketA

  Sweeppea MCPA

  Get full details of a support ticket by case number. Use fetch_open_tickets or fetch_closed_tickets first to find tickets, then use this tool with the case number to get complete information including notes, files, collaborators, and statistics. Present only human-readable information (case number, subject, dates, notes). # get_ticket ## When to use Get full details of a support ticket by case number. Use fetch_open_tickets or fetch_closed_tickets first to find tickets, then use this tool with the case number to get complete information including notes, files, collaborators, and statistics. Present only human-readable information (case number, subject, dates, notes). ## Parameters to validate before calling - case_number (string, required) — The ticket case number (e.g., "HYXTNJV")

  ConnectorNo auth

• getAdditionalInformationOptionsA

  Nomad StaysA

  List valid values for one of the Additional Information picklists used in updateStayOrganisationalData: Children Allowed, Pets Allowed, or Parking. These are NOT booleans — they're lookup IDs (e.g. 'Yes', 'No', 'On Request') — call this to find the right value before writing petsAllowedId/childrenAllowedId/parkingId. Requires NOMADSTAYS_MCP_AGENT_TOKEN.

  ConnectorNo auth

• get_wiki_pageA

  AcuiQA

  Read one AcuiQ wiki page, or list what the wiki holds. Reference notes on acupuncture nomenclature, point safety and the theory the prescriptions were written in – the context the protocol tools cannot supply. Call with no arguments to list every page with its section and summary; pass "path" ("nomenclature/point-codes") to get one page's summary, sources and markdown-twin URL. Each page states what it rests on and when those claims were last checked. To find the page for a topic, call search_wiki first.

  ConnectorNo auth

• cours_historiqueA

  Gold & Silver CompanyA

  Evolution of Gold & Silver Company's own published buying grid over the last 7 to 365 days (one point per day), for a gold fineness (18K default, 9K, 14K, 22K) or a listed coin/bar: first, last, low, high, variation. Indicative, built only from the house's public grid, no external market data, no advice.

  ConnectorNo auth

• strategic-mindsetA

  ClairvoyanceA

  Assesses whether code reflects strategic or tactical thinking, including the 10-20% investment rule and tactical-tornado patterns. Use when evaluating design investment, when code was written under time pressure, or when working code consistently degrades the system. Not for judging whether a specific diff looks designed-in or bolted-on (use code-evolution).

  ConnectorNo auth

• design-reviewA

  ClairvoyanceA

  Orchestrates a structured design review, running the other skills as a diagnostic funnel from complexity triage to a full red-flags sweep. Use when the user asks for a comprehensive or prioritized design assessment of a file, module, or PR. Not for an open-ended "anything off here?" or "take a look at this" prompt that names no review goal (use red-flags), a plain diff review before merge or analyzing how code changed over time (use code-evolution), or applying one specific lens (use that skill directly).

  ConnectorNo auth

• get_block_infoA

  blockscout-mcp-serverA

  Get block information like timestamp, gas used, burnt fees, transaction count etc. Can optionally include the list of transaction hashes contained in the block. Transaction hashes are omitted by default; request them only when you truly need them, because on high-traffic chains the list may exhaust the context.

  ConnectorOAuth

• explain_conceptA

  ReliaSimA

  Definitional primer for ReliaSim's framework concepts — Constraint, Buffer, Interrupt, Converter, cascading losses, OEE, Gain/Loss methodology, Buffer Tradeoff. Returns bundled theory content, NOT interpretation of any specific simulation run. Use for 'what is X?' / 'how does X work?' / 'explain the framework' questions. For line-specific claims (throughput, availability, what-if), call the sim tools instead.

  ConnectorNo auth

• explain_queueing_theoryA

  QueueSimA

  Return a ~500-word educational explainer of M/M/c queueing theory: Little's Law, utilization, why averages mislead, how simulation relates to Erlang-C. No inputs. Use this when the user asks a conceptual 'why' or 'how does this work' question rather than asking for a number.

  ConnectorNo auth

• get_mission_statsA

  mcp-serverA

  Get aggregate statistics about missions on the HomeVisto platform. Returns total counts, status breakdown, and average bounty information. Useful for understanding platform activity.

  ConnectorNo auth

• get_block_infoA

  mcp-serverA

  Get block information like timestamp, gas used, burnt fees, transaction count etc. Can optionally include the list of transaction hashes contained in the block. Transaction hashes are omitted by default; request them only when you truly need them, because on high-traffic chains the list may exhaust the context.

  ConnectorNo auth

• explain_reliability_basicsA

  ReliaStatsA

  Return a textbook-tier explainer of reliability fundamentals: the four reliability functions R(t)/F(t)/f(t)/h(t), MTBF vs MTTF vs MTTR, the availability identity A = MTBF/(MTBF+MTTR), the bathtub curve, and series/parallel system reliability. No inputs. Use when a user asks 'what is reliability theory' / 'explain MTBF' / 'how does availability work' / 'what's a hazard rate'. ANTI-FABRICATION: text is sourced from docs/reliability-theory.md (the canonical ChiAha reliability primer). Quote sections verbatim; do not paraphrase reliability theory from training-data recall.

  ConnectorNo auth

• chem-compatA

  ToolcallA

  Can chemical A be safely mixed or stored with chemical B? Pass two CAS numbers or names. Returns a verdict (incompatible / caution / no_known_hazard), the reason, expected effects (gas evolution, heat, fire, toxic fumes) and confidence, from expert reasoning over PubChem GHS data and CAMEO-derived reactivity profiles. JSON response. [Paid: $0.03 USDC per call via x402 on Base; the calling client pays automatically.]

  ConnectorNo auth