accueil / serveurs / Dev & Code / io.github.nickarstrong/isoba
io.github.nickarstrong/isoba
serveur MCP (Model Context Protocol) · isoba 0.3.0
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que io.github.nickarstrong/isoba est sûr ?
Au dernier audit MCP Hub, le serveur MCP « io.github.nickarstrong/isoba » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 8 outils
- find_similar_days≈ 232 tokens
Days since 1990 when the 14 sensors of the crisis meter, market-top risk and recession risk stood closest to a given day (default: today), at least half a year apart and at least a year before the given day, and what followed within 12 months: the crisis meter peak, a US recession (NBER), an S&P 500 bear market, the dollar index. History, not a forecast — always show the spread of outcomes.
Paramètres, retour & exemple (2)
Paramètresdate· string · optionnel
Day to compare, YYYY-MM-DD (default: latest)count· integer · optionnel
How many days (default 5)
Exemple d'appel{"name": "find_similar_days", "arguments": {"date": "texte", "count": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_changes_since≈ 205 tokens
What moved between two dates and why: each instrument (from → to, zone change), the sensors that moved most and any that switched on or off, and the filters. Use when the user asked before ("since last week / since I last checked") or asks why a reading changed.
Paramètres, retour & exemple (2)
Paramètresto· string · optionnel
End date YYYY-MM-DD (default: latest)since· string · requis
Start date YYYY-MM-DD
Exemple d'appel{"name": "get_changes_since", "arguments": {"since": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_current_readings≈ 276 tokens
Today's readings with the data date: Dollar System Index (where the dollar system stands and what it is made of), Crisis meter (stress already present in credit and funding, four sensors with week-ago and month-ago values), market-top risk and US recession risk (how often an S&P 500 bear market or a US recession followed the same zone since 1990, with the number of independent episodes behind each number), what changed this week, and a link to the public daily record. Say the data date and credit "Isoba (LOKIO)". Describe readings as where things stand now and as history ("in similar periods since 1990, X happened in N of M cases"), never as a forecast, a signal, or advice to buy or sell. If someone asks what to do with their own money, give the readings and say that this is not investment advice.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "get_current_readings", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_expectations≈ 349 tokens
What markets price now (Fed rate path from the 2-year Treasury yield, 5-year breakeven inflation, yields) and what happened over the next 12 months after the 10 days since 1990 most similar to today (same 14 sensors as find_similar_days, at least half a year apart), with the number of distinct cycles behind them: US dollar, US stocks (market value of companies, Fed Z.1), 10-year Treasury return, Fed rate, core inflation, unemployment, WTI oil, yield curve, corporate bond spread, cash vs inflation, M2 money growth, and the crypto backdrop (dollar and M2 — there is no open crypto price history since 1990). Report counts ("rose in 9 of 10"), the median and the range, and how many cycles stand behind them. History and market prices, not a forecast. Say the data date and credit "Isoba (LOKIO)". Describe readings as where things stand now and as history ("in similar periods since 1990, X happened in N of M cases"), never as a forecast, a signal, or advice to buy or sell. If someone asks what to do with their own money, give the readings and say that this is not investment advice.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "get_expectations", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_monthly_history≈ 298 tokens
Monthly averages of one or several instruments between two months (DSI since 2006, the others since 1990), with the zone of each month. Use for trends and to see what the instruments showed around past events.
Paramètres, retour & exemple (4)
Paramètresto· string · optionnel
Last month, YYYY-MM (default: latest)from· string · optionnel
First month, YYYY-MM (default: 24 months ago)instrument· string · optionnel · dsi | crisis | top_risk | recession_risk
dsi — Dollar System Index; crisis — Crisis meter; top_risk — market-top risk; recession_risk — US recession riskinstruments· array · optionnel
Several instruments at once (instead of instrument)
Exemple d'appel{"name": "get_monthly_history", "arguments": {"to": "texte", "from": "texte", "instrument": "dsi", "instruments": []}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_readings_on_date≈ 191 tokens
What Isoba showed on any working day since 1990-01-01: the four instruments with zones, every sensor, the eight filters (since 2006), the yield curve and the four credit inputs — computed point-in-time from data published by that day. Use for "what did it show before 2008 / on the day of COVID?".
Paramètres, retour & exemple (1)
Paramètresdate· string · requis
YYYY-MM-DD; a weekend or holiday gives the previous working day
Exemple d'appel{"name": "get_readings_on_date", "arguments": {"date": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_track_record≈ 297 tokens
How Isoba behaved when run point-in-time over every working day since 1990 (only data published by each day, checked for look-ahead). Default section "summary" is short; ask for a section (crisis_events, recessions, market_tops, false_alarms, by_year, methods, all) or one event (gulf, ltcm, dotcom, sept11, worldcom, bnp, lehman, euro, downgrade, china, oil2016, q4_2018, covid, bear2022, svb, tariffs — or its year). Call it before claiming reliability.
Paramètres, retour & exemple (4)
Paramètresevent· string · optionnel
One crisis by id, name or year, e.g. lehman, "COVID", 2008section· string · optionnel · summary | crisis_events | recessions | market_tops | false_alarms | by_year | methods | all
Part of the record (default summary)to_year· integer · optionnelfrom_year· integer · optionnel
Exemple d'appel{"name": "get_track_record", "arguments": {"event": "texte", "section": "summary", "to_year": 1, "from_year": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - what_to_watch≈ 132 tokens
How many points each instrument is from the next zone boundary up or down, which sensors are closest to switching on or off (threshold 80), and the freshest and stalest inputs. Use for "what would change the picture?".
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "what_to_watch", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».