Isoba — Dollar & Crisis Index
REMOTE · ISOBA.LOKIO.ORG
US dollar index, crisis meter, recession and market-top risk from public-domain data since 1990.
Available components
Last scanned (1 hour ago)
Scores higher than 60% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1453 tokens (~181/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 85% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_current_readings” rewrote its description, which is the text the model reads security
- Tool “get_monthly_history” rewrote its description, which is the text the model reads security
- Tool “get_track_record” rewrote its description, which is the text the model reads security
- Schema quality: 155 → 181 ▼ functional
- Tool coverage: 100% → 85% ▼ functional
- Schema quality: 465 → 1158 ▼ functional
- The server now declares the “prompts” capability functional
- First check of Schema quality: 100 functional
- Schema quality: good → excellent functional
- New prompt “explain_for_beginner” functional
- New prompt “morning_brief” functional
- Server version: 0.2.0 → 0.3.0 functional
- Server version: 0.1.0 → 0.2.0 functional
- New tool “get_expectations” functional
- New tool “find_similar_days” functional
- New tool “get_changes_since” functional
- New tool “get_readings_on_date” functional
- New tool “what_to_watch” functional
- “get_monthly_history” added an optional parameter “instruments” cosmetic
- “get_track_record” added an optional parameter “event” cosmetic
- “get_track_record” added an optional parameter “from_year” cosmetic
- “get_track_record” added an optional parameter “section” cosmetic
- “get_track_record” added an optional parameter “to_year” cosmetic
- “get_monthly_history” made “instrument” optional cosmetic
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 16 Oct 26 66
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Oct 2026 · Probed https://isoba.lokio.org/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lokio.org | CN=WE1,O=Google Trust Services,C=US | 16 Oct 2026 | 14 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 529083d2ddfb1f18136777d151680dc0 |
| SANs: lokio.org, isoba.lokio.org, *.isoba.lokio.org | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of isoba.lokio.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 26974 | 8 | Verified |
| lokio.org. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://isoba.lokio.org/mcp | Verified | 200 | |
| http (plaintext) | http://isoba.lokio.org/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
find_similar_days Isoba: similar days in history ~135
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.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | How many days (default 5) |
| date | string | – | Day to compare, YYYY-MM-DD (default: latest) |
No output schema declared.
No examples provided.
get_changes_since Isoba: what changed since a date ~95
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.
| Name | Type | Req | Description |
|---|---|---|---|
| since | string | yes | Start date YYYY-MM-DD |
| to | string | – | End date YYYY-MM-DD (default: latest) |
No output schema declared.
No examples provided.
get_current_readings Isoba: today's readings ~190
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_expectations Isoba: 12-month expectations ~271
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_monthly_history Isoba: monthly history ~140
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | First month, YYYY-MM (default: 24 months ago) |
| instrument | string | – | dsi — Dollar System Index; crisis — Crisis meter; top_risk — market-top risk; recession_risk — US recession risk |
| instruments | array | – | Several instruments at once (instead of instrument) |
| to | string | – | Last month, YYYY-MM (default: latest) |
No output schema declared.
No examples provided.
get_readings_on_date Isoba: readings on a date ~105
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?".
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | YYYY-MM-DD; a weekend or holiday gives the previous working day |
No output schema declared.
No examples provided.
get_track_record Isoba: tested on history ~196
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.
| Name | Type | Req | Description |
|---|---|---|---|
| event | string | – | One crisis by id, name or year, e.g. lehman, "COVID", 2008 |
| from_year | integer | – | – |
| section | string | – | Part of the record (default summary) |
| to_year | integer | – | – |
No output schema declared.
No examples provided.
what_to_watch Isoba: what is closest to changing ~56
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?".
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Isoba — Dollar & Crisis Index MCP server?
Isoba — Dollar & Crisis Index is a hosted endpoint at https://isoba.lokio.org/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · isoba.lokio.org
claude mcp add --transport http nickarstrong-isoba 'https://isoba.lokio.org/mcp'
What is the Isoba — Dollar & Crisis Index MCP server?
Isoba — Dollar & Crisis Index is an MCP server listed in the public MCP registry as io.github.nickarstrong/isoba. US dollar index, crisis meter, recession and market-top risk from public-domain data since 1990. This page covers its hosted endpoint (https://isoba.lokio.org/mcp).
Is the Isoba — Dollar & Crisis Index MCP server safe to use?
Isoba — Dollar & Crisis Index scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Isoba — Dollar & Crisis Index MCP server expose?
Isoba — Dollar & Crisis Index exposes 8 tools: get_current_readings, get_readings_on_date, get_changes_since, find_similar_days, what_to_watch, and 3 more. Their descriptions and schemas cost roughly 1,188 tokens of context every time the server is loaded.
Does the Isoba — Dollar & Crisis Index MCP server require authentication?
No. We connected to Isoba — Dollar & Crisis Index without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Isoba — Dollar & Crisis Index MCP server still maintained?
Isoba — Dollar & Crisis Index is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.