# Isoba — Dollar & Crisis Index (remote · isoba.lokio.org)

US dollar index, crisis meter, recession and market-top risk from public-domain data since 1990.

- Trust score: 70/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `isoba.lokio.org`: 70/100 (this document), [markdown](https://verifymcp.io/servers/nickarstrong-isoba/isoba.md), [page](https://verifymcp.io/servers/nickarstrong-isoba/isoba)

## Channel facts

- Endpoint: `https://isoba.lokio.org/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-23.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 79/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 85% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http nickarstrong-isoba 'https://isoba.lokio.org/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "nickarstrong-isoba": {
      "url": "https://isoba.lokio.org/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "nickarstrong-isoba": {
      "type": "http",
      "url": "https://isoba.lokio.org/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.nickarstrong-isoba]
url = "https://isoba.lokio.org/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nickarstrong-isoba": {
      "type": "remote",
      "url": "https://isoba.lokio.org/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add nickarstrong-isoba --url 'https://isoba.lokio.org/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  nickarstrong-isoba:
    url: "https://isoba.lokio.org/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "nickarstrong-isoba": {
      "Transport": "http",
      "Url": "https://isoba.lokio.org/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add nickarstrong-isoba -t streamable-http -u 'https://isoba.lokio.org/mcp'
```

### Other

```json
{
  "mcpServers": {
    "nickarstrong-isoba": {
      "type": "http",
      "url": "https://isoba.lokio.org/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-22 (score 70, +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.

### 2026-10-20 (score 69, +1)

- [security] 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
- [functional regression] Schema quality: 155 → 181
- [functional regression] Tool coverage: 100% → 85%
- [functional regression] 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”
- [cosmetic] “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

### 2026-10-19 (score 68, +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.

### 2026-10-17 (score 67, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-16 (score 66)

First indexed and scored.

## MCP tools (8)

### `get_current_readings` (~190 tokens)

Isoba: today's readings

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.

### `get_readings_on_date` (~105 tokens)

Isoba: readings on a date

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?".

Input parameters:

- `date` (string, required): YYYY-MM-DD; a weekend or holiday gives the previous working day

### `get_changes_since` (~95 tokens)

Isoba: what changed since a date

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.

Input parameters:

- `since` (string, required): Start date YYYY-MM-DD
- `to` (string): End date YYYY-MM-DD (default: latest)

### `find_similar_days` (~135 tokens)

Isoba: similar days in history

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.

Input parameters:

- `count` (integer): How many days (default 5)
- `date` (string): Day to compare, YYYY-MM-DD (default: latest)

### `what_to_watch` (~56 tokens)

Isoba: what is closest to changing

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?".

### `get_expectations` (~271 tokens)

Isoba: 12-month expectations

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.

### `get_monthly_history` (~140 tokens)

Isoba: monthly history

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.

Input parameters:

- `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)

### `get_track_record` (~196 tokens)

Isoba: tested on history

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.

Input parameters:

- `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)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/nickarstrong-isoba/isoba#diagnostics

## Score history

- 2026-10-23: 70
- 2026-10-22: 70
- 2026-10-21: 69
- 2026-10-20: 69
- 2026-10-19: 68
- 2026-10-18: 67
- 2026-10-17: 67
- 2026-10-16: 66

## Common questions

### 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.

## Links

- Remote endpoint: https://isoba.lokio.org/mcp
- Website: https://isoba.lokio.org/
- Changelog RSS feed: https://verifymcp.io/servers/nickarstrong-isoba/isoba.xml
- Changelog JSON feed: https://verifymcp.io/servers/nickarstrong-isoba/isoba.json
- HTML version of this page: https://verifymcp.io/servers/nickarstrong-isoba/isoba