# Japan AMeDAS Observations MCP (remote · jp-amedas-obs-mcp.donniertf.workers.dev)

Nationwide JMA AMeDAS temperature, humidity and precipitation observations.

- Trust score: 56/100 (low)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `jp-amedas-obs-mcp.donniertf.workers.dev`: 56/100 (this document), [markdown](https://verifymcp.io/servers/donniertf-hub-jp-amedas-obs-mcp/jp-amedas-obs-mcp.md), [page](https://verifymcp.io/servers/donniertf-hub-jp-amedas-obs-mcp/jp-amedas-obs-mcp)

## Channel facts

- Endpoint: `https://jp-amedas-obs-mcp.donniertf.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 54/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 193 tokens (~64/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 83/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 50% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### How do I install the Japan AMeDAS Observations MCP server?

Japan AMeDAS Observations MCP is a hosted endpoint at https://jp-amedas-obs-mcp.donniertf.workers.dev/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.

### Claude

```bash
claude mcp add --transport http donniertf-hub-jp-amedas-obs-mcp 'https://jp-amedas-obs-mcp.donniertf.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "donniertf-hub-jp-amedas-obs-mcp": {
      "url": "https://jp-amedas-obs-mcp.donniertf.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "donniertf-hub-jp-amedas-obs-mcp": {
      "type": "http",
      "url": "https://jp-amedas-obs-mcp.donniertf.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.donniertf-hub-jp-amedas-obs-mcp]
url = "https://jp-amedas-obs-mcp.donniertf.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "donniertf-hub-jp-amedas-obs-mcp": {
      "type": "remote",
      "url": "https://jp-amedas-obs-mcp.donniertf.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add donniertf-hub-jp-amedas-obs-mcp --url 'https://jp-amedas-obs-mcp.donniertf.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  donniertf-hub-jp-amedas-obs-mcp:
    url: "https://jp-amedas-obs-mcp.donniertf.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "donniertf-hub-jp-amedas-obs-mcp": {
      "Transport": "http",
      "Url": "https://jp-amedas-obs-mcp.donniertf.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add donniertf-hub-jp-amedas-obs-mcp -t streamable-http -u 'https://jp-amedas-obs-mcp.donniertf.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "donniertf-hub-jp-amedas-obs-mcp": {
      "type": "http",
      "url": "https://jp-amedas-obs-mcp.donniertf.workers.dev/mcp"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 56, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 55, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 54, +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.

### 2026-10-30 (score 53, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-29 (score 52)

First indexed and scored.

## MCP tools (3)

### `latest_obs_time` (~33 tokens)

FREE. Latest AMeDAS observation timestamp published by JMA, plus a sample of Tokyo-area stations if present.

### `station` (~50 tokens)

PRO. Observation for one AMeDAS station ID at the latest timestamp.

Input parameters:

- `access_token` (string): Subscriber token from /success (or Authorization: Bearer)
- `station_id` (string, required)

### `extremes` (~53 tokens)

PRO. Warmest and coldest AMeDAS stations in the latest map (by temp).

Input parameters:

- `access_token` (string): Subscriber token from /success (or Authorization: Bearer)
- `limit` (number)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/donniertf-hub-jp-amedas-obs-mcp/jp-amedas-obs-mcp#diagnostics

## Score history

- 2026-11-05: 56
- 2026-11-04: 55
- 2026-11-03: 55
- 2026-11-02: 54
- 2026-11-01: 54
- 2026-10-31: 53
- 2026-10-30: 53
- 2026-10-29: 52

## Common questions

### What is the Japan AMeDAS Observations MCP server?

Japan AMeDAS Observations MCP is listed in the public MCP registry as io.github.donniertf-hub/jp-amedas-obs-mcp. Nationwide JMA AMeDAS temperature, humidity and precipitation observations. This page covers its hosted endpoint (https://jp-amedas-obs-mcp.donniertf.workers.dev/mcp).

### Is the Japan AMeDAS Observations MCP server safe to use?

Japan AMeDAS Observations MCP scores 56 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 Japan AMeDAS Observations MCP server expose?

Japan AMeDAS Observations MCP exposes 3 tools: latest_obs_time, station, extremes. Their descriptions and schemas cost roughly 136 tokens of context every time the server is loaded.

### Does the Japan AMeDAS Observations MCP server require authentication?

No. We connected to Japan AMeDAS Observations MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Japan AMeDAS Observations MCP server still maintained?

Japan AMeDAS Observations MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Japan AMeDAS Observations MCP server?

VerifyMCP ran 12 checks on Japan AMeDAS Observations MCP, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Japan AMeDAS Observations MCP: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://jp-amedas-obs-mcp.donniertf.workers.dev/mcp
- Repository: https://github.com/donniertf-hub/uk-mcp-fleet
- Website: https://jp-amedas-obs-mcp.donniertf.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/donniertf-hub-jp-amedas-obs-mcp/jp-amedas-obs-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/donniertf-hub-jp-amedas-obs-mcp/jp-amedas-obs-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/donniertf-hub-jp-amedas-obs-mcp/jp-amedas-obs-mcp.json
- HTML version of this page: https://verifymcp.io/servers/donniertf-hub-jp-amedas-obs-mcp/jp-amedas-obs-mcp