Skip to main content
Glama
Japan FX Intervention

Japan FX Intervention

by pipeworx-io
README.md
# @pipeworx/japan-fx-intervention

Japan's foreign exchange intervention record from the Ministry of Finance: every dated operation since April 1991, the quarterly totals, and the latest monthly release.

Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1882+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

## Tools

- `japan_fx_intervention(start_date?, end_date?)` — dated operations in the range (ISO dates; amount in 100 million yen, direction, currency pair), quarterly totals for the quarters in the range, and the latest monthly release (period, total, release date). With no dates it returns the most recent operations (last 3 years), the matching quarterly totals and the latest monthly release. A quarter or month with no intervention is a published figure of 0 and is returned as 0, not omitted.

## Auth

Keyless.

## Data sources

- Ministry of Finance Japan, Foreign Exchange Intervention Operations: the historical record of operations, the quarterly totals, and the monthly release. Covers actual operations only, not verbal warnings or statements. Daily figures are rounded by the publisher, so they may not sum exactly to a quarterly total. Non-yen operations are converted to yen by the publisher at the Bank of Japan central rate. Every response carries `data_as_of`.

The historical file is Shift_JIS encoded and fetched live on each call; the monthly release is a human page parsed for its period and total, and the pack errors loudly if either format changes.

## Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

```json
{
  "mcpServers": {
    "japan-fx-intervention": {
      "url": "https://gateway.pipeworx.io/japan-fx-intervention/mcp"
    }
  }
}
```

### What this endpoint actually serves

`tools/list` at `https://gateway.pipeworx.io/japan-fx-intervention/mcp` returns the tools in the table
above **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,
`discover_tools`, `search_within`, `remember`/`recall` and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's `initialize` response states its exact scope, and
is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
`ask_pipeworx`, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed
directly, instead of just this one's:

```json
{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}
```

Both URLs reach the same gateway and the same 1882+ data sources. The
only difference is which pack's tools are listed **directly**; `ask_pipeworx`
reaches all of them from either one.

## No MCP client? Call it over HTTP

```bash
curl -X POST https://gateway.pipeworx.io/v1/tools/japan_fx_intervention \
  -H 'Content-Type: application/json' \
  -d '{"start_date":"2024-01-01","end_date":"2024-12-31"}'
```

No account needed for the first calls. Inspect any tool: `GET https://gateway.pipeworx.io/v1/tools/japan_fx_intervention`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{"query":"..."}`.

## Run it from npm

`@pipeworx/mcp-japan-fx-intervention` is a local stdio bridge to the Pipeworx gateway: your MCP client
starts it with `npx`, and it forwards every call to the same
`https://gateway.pipeworx.io/japan-fx-intervention/mcp` endpoint shown above. It needs network access;
there is no offline mode.

```json
{
  "mcpServers": {
    "japan-fx-intervention": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-japan-fx-intervention"]
    }
  }
}
```

Without a key it calls anonymously, capped at 50 calls a day. A free account
raises that to 200 a day: get a key at https://pipeworx.io/signup and add
`"env": { "PIPEWORX_API_KEY": "<your key>" }` to the server entry.
The key is sent as a Bearer token, the same way a hosted connection sends it,
so calls are metered and billed exactly as they are there.

It lists **only** this pack's tools by default. Set `PIPEWORX_META_TOOLS=1` to
also list `ask_pipeworx` and the other gateway-wide tools.

Behind an HTTPS proxy: Node's built-in `fetch` does not read `HTTPS_PROXY` by
default. Newer Node releases honour it when `NODE_USE_ENV_PROXY=1` is set; check
your Node version's documentation.

## Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English —
this works on the pack endpoint above as well as on the full gateway:

```
ask_pipeworx({ question: "your question about Japan Fx Intervention data" })
```

The gateway picks the right tool and fills the arguments automatically.

## More

- [Docs and guides](https://pipeworx.io/docs)
- [pipeworx.io](https://pipeworx.io)

## License

MIT