mcp · Japan

risk-space-dashboard

Japan Risk Probability Field - Crime, Disaster, Traffic, Weather integrated dashboard

Claim this listing

Represent risk-space-dashboard? Send a claim for review so we can discuss listing updates. Claims do not automatically grant ownership or verification.

Explore paid sponsorship →

What's in it

Data offered docs-verified: crime · disaster · traffic · weather · Event Loss Table (ELT) · GLM frequency/severity fits · loss development triangles · IBNR · VaR95, VaR99, CVaR99, max drawdown · parametric cat-bond pricing · reinsurance XL/QS pricing · parametric triggers · RCP2.6/4.5/8.5 scenarios across 2030/2050/2100 horizons · NGFS pathways · EIOPA 2026 shadow stress scenarios
Coverage docs-verified: Japan
Formats docs-verified: JSON
Access docs-verified: No auth for static JSON datasets under /data/. Data licence CC-BY 4.0 (attribution required to upstream authorities such as NPA, JMA, NIED); code licence MIT.

Useful for

Use cases llm-inferred: TCFD-style physical climate risk screening of Japan assets using RCP scenario outputs · Sense-check of reinsurance or parametric cover using ELT annual rate x mean loss to derive national AAL · Japan site-level disaster and crime exposure screening via the query API for due diligence
Audience llm-inferred: actuaries · reinsurance and insurance analysts · climate risk and sustainability reporting teams · catastrophe modellers

Limitations

Constraints llm-inferred: Japan only; no UK coverage, so of limited relevance to UK-focused projects · Spatial and temporal resolution and historical time span are not stated in DOCS · Example endpoints use a <pages> placeholder; the actual hosting URL is not given · DOCS do not document MCP tool names or transport; the entry's tools list contains repository files, not MCP tools · Known issues and data gaps are listed in issues.md, whose contents are not in DOCS · Scenario, stress-test and compliance-framework outputs are described in DOCS but not validated here

Licence: Unknown — check provider terms
Authentication: No API key required (repository README, auto-extracted; check upstream requirements)
GitHub stars: 1
Last commit: 15/10/2026
Last successful page check: 14/10/2026
Page health: healthy
Package: Not recorded
Verification: Not independently verified

Auto-extracted, unverified fields: tools, auth. Check upstream documentation.

Provenance & evidence

Daily discovery 2026-10-15: GitHub search; verified via GitHub API. Tools/install/auth auto-extracted from README.

Metadata observed 14/10/2026 · daily-2026-10-15 (github-search)