Model Context Protocol (MCP) server for freee API integration
Nothing to run from here
Isoba — Dollar & Crisis Index is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
7
tools declared
remote
at its publisher
—
calls last 7d
What it does
US dollar index, crisis meter, recession and market-top risk from public-domain data since 1990.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http isoba-dollar-crisis-index-mcp https://isoba.lokio.org/mcp
# 2 — ask your agent for something these tools do
# get_current_readings, get_readings_on_date, get_changes_since and 4 more
Isoba — Dollar & Crisis Index costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
NIAll 1 server
nickarstrong1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http isoba-dollar-crisis-index-mcp https://isoba.lokio.org/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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
No parameter schema on file.
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?".
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | yes | YYYY-MM-DD; a weekend or holiday gives the previous working day |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| since | string | yes | Start date YYYY-MM-DD |
| to | string | no | End date YYYY-MM-DD (default: latest) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | no | Day to compare, YYYY-MM-DD (default: latest) |
| count | integer | no | How many days (default 5) |
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?".
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| instrument | string | no | dsi — Dollar System Index; crisis — Crisis meter; top_risk — market-top risk; recession_risk — US recession risk |
| instruments | array | no | Several instruments at once (instead of instrument) |
| from | string | no | First month, YYYY-MM (default: 24 months ago) |
| to | string | no | Last month, YYYY-MM (default: latest) |
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, tarif
| Parameter | Type | Required | Notes |
|---|---|---|---|
| section | string | no | Part of the record (default summary) |
| event | string | no | One crisis by id, name or year, e.g. lehman, "COVID", 2008 |
| from_year | integer | no | — |
| to_year | integer | no | — |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Isoba — Dollar & Crisis Index or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 0.3.0 · scanned 28 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest9a76685c1e4a07a692db3a552cbd72f0cd55c07409d32f6fe9286956799fa474
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_current_readings | no tags | |
| get_readings_on_date | no tags | |
| get_changes_since | no tags | |
| find_similar_days | no tags | |
| what_to_watch | no tags | |
| get_monthly_history | no tags | |
| get_track_record | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest9a76685c1e4a07a6
Scanned2026-10-28
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.3.0.
0.3.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Isoba — Dollar & Crisis Index can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.