JP Data
REMOTE · JP-DATA-API-PRODUCTION.UP.RAILWAY.APP · SCANNED SEP 20
Japan, Korea and UK official data for AI agents: filings, FX, weather, travel, patents, AI tools.
Available components
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 → Why this is hard to 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 connect, but we couldn't read the tool list to see what that exposes. 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the JP Data MCP server?
JP Data is a hosted endpoint at https://jp-data-api-production.up.railway.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · jp-data-api-production.up.railway.app
claude mcp add --transport http a-mashiro-art-jp-data 'https://jp-data-api-production.up.railway.app/mcp'
{
"mcpServers": {
"a-mashiro-art-jp-data": {
"url": "https://jp-data-api-production.up.railway.app/mcp"
}
}
} {
"servers": {
"a-mashiro-art-jp-data": {
"type": "http",
"url": "https://jp-data-api-production.up.railway.app/mcp"
}
}
} [mcp_servers.a-mashiro-art-jp-data] url = "https://jp-data-api-production.up.railway.app/mcp"
{
"$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
}
}
} openclaw mcp add a-mashiro-art-jp-data --url 'https://jp-data-api-production.up.railway.app/mcp' --transport streamable-http
mcp_servers:
a-mashiro-art-jp-data:
url: "https://jp-data-api-production.up.railway.app/mcp" {
"McpServers": {
"a-mashiro-art-jp-data": {
"Transport": "http",
"Url": "https://jp-data-api-production.up.railway.app/mcp"
}
}
} assistant mcp add a-mashiro-art-jp-data -t streamable-http -u 'https://jp-data-api-production.up.railway.app/mcp'
{
"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.
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.
- 26 Aug 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
- 11 Aug 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
- 7 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.37 → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 31 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
- 30 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
- 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 0
First indexed and scored.
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 20 Sept 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 |
Background: What to check on a remote MCP endpoint →
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 | 404 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://jp-data-api-production.up.railway.app/mcp | HTTP error | 404 | |
| http (plaintext) | http://jp-data-api-production.up.railway.app/mcp | HTTPS enforced | 301 | https://jp-data-api-production.up.railway.app/mcp |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
anime_pilgrimage ~31
Real-world locations featured in popular anime (seichi junrei).
| 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).
| 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.
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | – | – |
No output schema declared.
No examples provided.
japan_rail_lines ~25
Major Japanese railway lines and key stations.
| 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.
| 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.
| 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 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.
| 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.
| 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.
| 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.
| 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.
| 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.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | – |
No output schema declared.
No examples provided.
What is the JP Data MCP server?
JP Data is an MCP server listed in the public MCP registry as io.github.a-mashiro-art/jp-data. Japan, Korea and UK official data for AI agents: filings, FX, weather, travel, patents, AI tools. This page covers its hosted endpoint (https://jp-data-api-production.up.railway.app/mcp).
Is the JP Data MCP server safe to use?
JP Data scores 23 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the JP Data MCP server expose?
JP Data exposes 13 tools: japan_regional_food, japan_onsen_guide, japan_events, japan_rail_lines, anime_pilgrimage, and 8 more. Their descriptions and schemas cost roughly 573 tokens of context every time the server is loaded.
Does the JP Data MCP server require authentication?
No. We connected to JP Data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the JP Data MCP server still maintained?
JP Data is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.