Koskamo

Japan Authority Updates MCP

An MCP server that provides AI agents with machine-readable JSON summaries of recent announcements from Japan's Financial Services Agency (FSA), Bank of Japan (BOJ), and Ministry of Finance (MOF). It aggregates RSS feeds every 5 minutes, offering tools to retrieve latest updates, search by date range, or fetch changes since a specific timestamp. Paid tools utilize the x402 protocol for microtransactions via USDC on Base.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Japan Authority Updates MCP logo, by SITIONCommunity listingStreamable HTTPNo sign-inEndpoint checked 2026-11-06Published by SITION
MCP endpoint (Streamable HTTP)
https://sition-data-api.sition-data-api-worker.workers.dev/mcp
Vendor documentation

What its tools do

4 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

4 of 4 have a description · 0 of 4 declare behavior hints · 2 of 2 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Retrieve the latest regulatory updates from FSA, BOJ, and MOF
  • Search for authority announcements within a specific date range
  • Fetch new items observed after a specific timestamp
  • Check the health status of data feeds

Source and maintenance

Community listingRegistry 1.0.0

Protocol and capabilities

Server
sition-jp-authorities 1.0.0
MCP protocol negotiated in check
2025-11-25
Tools
4 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": true
  }
}

Tools

4 advertised

jp_authorities_health
Advertised by the server during the last successful anonymous check.

Feed health (feed_status) of Japan Authority Updates (FSA, BOJ, MOF). Free.

jp_authorities_health input schema
{
  "type": "object",
  "properties": {}
}
jp_authorities_latest
Advertised by the server during the last successful anonymous check.

Japanese authority (FSA, BOJ, MOF) updates published in the last 24 hours. Price: $0.02 per call (x402, USDC).

jp_authorities_latest input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
jp_authorities_since
Advertised by the server during the last successful anonymous check.

Japanese authority (FSA, BOJ, MOF) updates first observed after timestamp t. Price: $0.01 per call (x402, USDC).

jp_authorities_since input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "t"
  ],
  "properties": {
    "t": {
      "type": "string",
      "description": "ISO-8601 timestamp with Z or ±hh:mm (not in the future). Returns items with observed_at > t, oldest first."
    }
  }
}
jp_authorities_search
Advertised by the server during the last successful anonymous check.

Search Japanese authority (FSA, BOJ, MOF) updates by publication date range and authority. Price: $0.05 per call (x402, USDC).

jp_authorities_search input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "from"
  ],
  "properties": {
    "to": {
      "type": "string",
      "description": "YYYY-MM-DD (23:59:59Z) or ISO-8601 timestamp; default now. At most 92 days after from."
    },
    "from": {
      "type": "string",
      "description": "YYYY-MM-DD (00:00:00Z) or ISO-8601 timestamp. Returns items with published_at >= from."
    },
    "authority": {
      "enum": [
        "FSA",
        "BOJ",
        "MOF"
      ],
      "type": "string",
      "description": "FSA, BOJ or MOF."
    }
  }
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

  1. 2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
1128 ms
95th percentile latency
1128 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 1128 ms · metadata changed · 4 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http japan-authority-updates-mcp https://sition-data-api.sition-data-api-worker.workers.dev/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add japan-authority-updates-mcp --url https://sition-data-api.sition-data-api-worker.workers.dev/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable japan-authority-updates-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "japan-authority-updates-mcp": {
      "url": "https://sition-data-api.sition-data-api-worker.workers.dev/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "japan-authority-updates-mcp": {
      "type": "streamableHttp",
      "url": "https://sition-data-api.sition-data-api-worker.workers.dev/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start japan-authority-updates-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "japan-authority-updates-mcp": {
      "type": "http",
      "url": "https://sition-data-api.sition-data-api-worker.workers.dev/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http japan-authority-updates-mcp https://sition-data-api.sition-data-api-worker.workers.dev/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://sition-data-api.sition-data-api-worker.workers.dev/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "japan-authority-updates-mcp": {
      "serverUrl": "https://sition-data-api.sition-data-api-worker.workers.dev/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Japan Authority Updates MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.