JP Data

REMOTE · JP-DATA-API-PRODUCTION.UP.RAILWAY.APP · SCANNED AUG 3

Japan, Korea and UK official data for AI agents: filings, FX, weather, travel, patents, AI tools.

Available components

remote · jp-data-api-production.up.railway.app 58

+4 this week 58 58 Trust /100

Trust breakdown (6 categories)

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. How we score →

Endpoint Security57

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
Authorisation not fully verified: no authorisation is required to call this server, and 13 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability54

AI-judged instruction clarity (fair).Partial
Tool/resource definitions use about 573 tokens (~44/item across 13 items; 13 tools + 0 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage74

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
22% of tool parameters carry a description.Partial

Capabilities60

Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · jp-data-api-production.up.railway.app

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http a-mashiro-art-jp-data https://jp-data-api-production.up.railway.app/mcp

# ~/.codex/config.toml

[mcp_servers.a-mashiro-art-jp-data]
url = "https://jp-data-api-production.up.railway.app/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "a-mashiro-art-jp-data": {
      "type": "remote",
      "url": "https://jp-data-api-production.up.railway.app/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add a-mashiro-art-jp-data --url https://jp-data-api-production.up.railway.app/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  a-mashiro-art-jp-data:
    url: "https://jp-data-api-production.up.railway.app/mcp"

// mcp.json

{
  "mcpServers": {
    "a-mashiro-art-jp-data": {
      "type": "http",
      "url": "https://jp-data-api-production.up.railway.app/mcp"
    }
  }
}

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

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

3 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
31 Jul 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
29 Jul 26 +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.
28 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
26 Jul 26 54

First indexed and scored.

Show 6 earlier entries Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://jp-data-api-production.up.railway.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=*.up.railway.app	CN=YE1,O=Let's Encrypt,C=US	29 Jul 2026	27 Oct 2026	ECDSA 256	ECDSA-SHA384	6da79bb561da3efeb0e751ca21abd3999fe
SANs: *.up.railway.app, up.railway.app
CN=YE1,O=Let's Encrypt,C=US (CA)	CN=Root YE,O=ISRG,C=US	3 Sept 2025	2 Sept 2028	ECDSA 384	ECDSA-SHA384	5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA)	CN=ISRG Root X2,O=Internet Security Research Group,C=US	13 May 2026	2 Sept 2032	ECDSA 384	ECDSA-SHA384	872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA)	CN=ISRG Root X1,O=Internet Security Research Group,C=US	13 May 2026	2 Sept 2032	ECDSA 384	SHA256-RSA	6c8f1dc727c7117f7baf853ac980f9cd

DNSSEC insecure

Validation of jp-data-api-production.up.railway.app. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
app.	present	23684	8	Verified
railway.app.	absent			Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation

Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result	No authorisation required
HTTP status	200

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://jp-data-api-production.up.railway.app/mcp	Verified	200
http (plaintext)	http://jp-data-api-production.up.railway.app/mcp	HTTPS enforced	301	https://jp-data-api-production.up.railway.app/mcp

MCP tools — 13 exposed · ~573 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

anime_pilgrimage ~31

Real-world locations featured in popular anime (seichi junrei).

Input Output Examples

Name	Type	Req	Description
q	string	—	—

No output schema declared.

No examples provided.

japan_events ~27

Japanese festivals and annual events by month (1-12).

Input Output Examples

Name	Type	Req	Description
month	string	—	—

No output schema declared.

No examples provided.

japan_onsen_guide ~36

Famous Japanese hot spring (onsen) towns with water type, features, access.

Input Output Examples

Name	Type	Req	Description
q	string	—	—

No output schema declared.

No examples provided.

japan_rail_lines ~25

Major Japanese railway lines and key stations.

Input Output Examples

Name	Type	Req	Description
q	string	—	—

No output schema declared.

No examples provided.

japan_regional_food ~45

Japanese regional specialty dishes (sushi, ramen, wagyu, curry, gyoza...) with origin and description. Optional keyword filter.

Input Output Examples

Name	Type	Req	Description
q	string	—	—

No output schema declared.

No examples provided.

jp_company_brief ~67

AI company research brief from official registries (Japan EDINET, Korea DART, UK Companies House). PAID TOOL: costs $0.25 USDC per call via x402.

Input Output Examples

Name	Type	Req	Description
country	string	—	JP \| KR \| UK
name	string	yes	—

No output schema declared.

No examples provided.

jp_data_api_catalog ~45

List all 29 paid pay-per-call endpoints of JP Data API (x402/USDC): filings, FX, weather, anime, sports, prediction markets and more.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

jp_filings_list ~49

Daily Japanese corporate disclosures from EDINET (Japan FSA). PAID TOOL: costs $0.01 USDC per call via x402.

Input Output Examples

Name	Type	Req	Description
date	string	yes	YYYY-MM-DD

No output schema declared.

No examples provided.

jp_memory_get ~48

Retrieve a value from persistent agent memory. PAID TOOL: costs $0.001 USDC per call via x402.

Input Output Examples

Name	Type	Req	Description
key	string	yes	—
ns	string	yes	—

No output schema declared.

No examples provided.

jp_memory_set ~59

Store a value in persistent agent memory that survives across sessions. PAID TOOL: costs $0.002 USDC per call via x402.

Input Output Examples

Name	Type	Req	Description
key	string	yes	—
ns	string	yes	—
value	string	yes	—

No output schema declared.

No examples provided.

jp_summarize ~55

Summarize any text into a concise English brief. PAID TOOL: costs $0.02 USDC per call via x402.

Input Output Examples

Name	Type	Req	Description
style	string	—	bullets \| paragraph
text	string	yes	—

No output schema declared.

No examples provided.

jp_translate ~56

Japanese-English translation (both directions), natural context-aware output. PAID TOOL: costs $0.02 USDC per call via x402.

Input Output Examples

Name	Type	Req	Description
text	string	yes	—
to	string	—	en \| ja (optional)

No output schema declared.

No examples provided.

world_city_guide ~30

Travel guide for world major cities: attractions, food, transit.

Input Output Examples

Name	Type	Req	Description
city	string	—	—

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	54
27 Jul	54
28 Jul	55
29 Jul	56
30 Jul	55
31 Jul	57
1 Aug	57
2 Aug	57
3 Aug	58