# Rising Shores Singapore (remote · risingshores.agentxr.app)

Sea-level rise in Singapore: when a place or address floods, areas and people affected, IPCC AR6.

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-19

## Components

- remote · `risingshores.agentxr.app`: 65/100 (this document), [markdown](https://verifymcp.io/servers/mazeasdamien-rising-shores-singapore/risingshores.md), [page](https://verifymcp.io/servers/mazeasdamien-rising-shores-singapore/risingshores)

## Channel facts

- Endpoint: `https://risingshores.agentxr.app/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-10-19.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - 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**: 66/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1421 tokens (~142/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 98% 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Rising Shores Singapore MCP server?

Rising Shores Singapore is a hosted endpoint at https://risingshores.agentxr.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.

### Claude

```bash
claude mcp add --transport http mazeasdamien-rising-shores-singapore 'https://risingshores.agentxr.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "mazeasdamien-rising-shores-singapore": {
      "url": "https://risingshores.agentxr.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "mazeasdamien-rising-shores-singapore": {
      "type": "http",
      "url": "https://risingshores.agentxr.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.mazeasdamien-rising-shores-singapore]
url = "https://risingshores.agentxr.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mazeasdamien-rising-shores-singapore": {
      "type": "remote",
      "url": "https://risingshores.agentxr.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mazeasdamien-rising-shores-singapore --url 'https://risingshores.agentxr.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  mazeasdamien-rising-shores-singapore:
    url: "https://risingshores.agentxr.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "mazeasdamien-rising-shores-singapore": {
      "Transport": "http",
      "Url": "https://risingshores.agentxr.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add mazeasdamien-rising-shores-singapore -t streamable-http -u 'https://risingshores.agentxr.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "mazeasdamien-rising-shores-singapore": {
      "type": "http",
      "url": "https://risingshores.agentxr.app/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-10-19 (score 65, +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-17 (score 64, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-16 (score 63)

First indexed and scored.

## MCP tools (10)

### `sea_level` (~163 tokens)

Projected sea-level rise at Singapore for a year and an emissions scenario (CCRS V3 2024, Ng et al. 2025, IPCC AR6), in metres above today's high-tide level.

Input parameters:

- `lang` (string): Language of the answer: "en" (default) or "fr".
- `scenario` (string): moderate = SSP2-4.5, high = SSP5-8.5, upper = SSP5-8.5 high end (planning). Default high.
- `storm_surge` (boolean): Add an extreme storm surge and high tide (+1.3 m) on top.
- `year` (integer, required): A year, 2025-2150 (with scenario), instead of rise_m.

### `when_does_it_flood` (~82 tokens)

In which year each scenario reaches a given sea-level rise (metres above today's high tide), or "beyond 2150".

Input parameters:

- `lang` (string): Language of the answer: "en" (default) or "fr".
- `rise_m` (number, required): Sea-level rise in metres above today's mean high water (0-9).

### `check_address` (~81 tokens)

For a Singapore postal code or place name: the sea-level rise at which it first connects to the sea, and roughly when each scenario gets there.

Input parameters:

- `lang` (string): Language of the answer: "en" (default) or "fr".
- `query` (string, required): A postal code (e.g. 018956) or a place name.

### `flood_impact` (~172 tokens)

Island-wide impact at a sea-level rise (or a year and scenario): share of Singapore's land flooded, buildings reached, residents living in flooded areas.

Input parameters:

- `lang` (string): Language of the answer: "en" (default) or "fr".
- `rise_m` (number): Sea-level rise in metres above today's mean high water (0-9).
- `scenario` (string): moderate = SSP2-4.5, high = SSP5-8.5, upper = SSP5-8.5 high end (planning). Default high.
- `storm_surge` (boolean): Add an extreme storm surge and high tide (+1.3 m) on top.
- `year` (integer): A year, 2025-2150 (with scenario), instead of rise_m.

### `area_impact` (~205 tokens)

Residents living in flooded parts of one planning area (e.g. Kallang, Punggol) at a sea-level rise or a year and scenario, and the first rise at which the area is reached.

Input parameters:

- `area` (string, required): A Singapore planning area (URA), e.g. "Kallang".
- `lang` (string): Language of the answer: "en" (default) or "fr".
- `rise_m` (number): Sea-level rise in metres above today's mean high water (0-9).
- `scenario` (string): moderate = SSP2-4.5, high = SSP5-8.5, upper = SSP5-8.5 high end (planning). Default high.
- `storm_surge` (boolean): Add an extreme storm surge and high tide (+1.3 m) on top.
- `year` (integer): A year, 2025-2150 (with scenario), instead of rise_m.

### `most_affected_areas` (~183 tokens)

The planning areas with the most residents in flooded areas at a sea-level rise (or a year and scenario).

Input parameters:

- `lang` (string): Language of the answer: "en" (default) or "fr".
- `n` (integer): How many areas (default 8, max 55).
- `rise_m` (number): Sea-level rise in metres above today's mean high water (0-9).
- `scenario` (string): moderate = SSP2-4.5, high = SSP5-8.5, upper = SSP5-8.5 high end (planning). Default high.
- `storm_surge` (boolean): Add an extreme storm surge and high tide (+1.3 m) on top.
- `year` (integer): A year, 2025-2150 (with scenario), instead of rise_m.

### `places_underwater` (~207 tokens)

Named public places (hawker centres, schools, places of worship) reached by the sea at a rise, optionally of one kind or in one planning area.

Input parameters:

- `area` (string): Limit to one planning area.
- `kind` (string)
- `lang` (string): Language of the answer: "en" (default) or "fr".
- `limit` (integer): Most names to list (default 20).
- `rise_m` (number): Sea-level rise in metres above today's mean high water (0-9).
- `scenario` (string): moderate = SSP2-4.5, high = SSP5-8.5, upper = SSP5-8.5 high end (planning). Default high.
- `storm_surge` (boolean): Add an extreme storm surge and high tide (+1.3 m) on top.
- `year` (integer): A year, 2025-2150 (with scenario), instead of rise_m.

### `list_areas` (~47 tokens)

The 55 URA planning areas the impact tools accept, with their resident populations.

Input parameters:

- `lang` (string): Language of the answer: "en" (default) or "fr".

### `map_link` (~163 tokens)

A link that opens the Rising Shores map with the sea raised to a given rise (or a year and scenario).

Input parameters:

- `lang` (string): Language of the answer: "en" (default) or "fr".
- `rise_m` (number): Sea-level rise in metres above today's mean high water (0-9).
- `scenario` (string): moderate = SSP2-4.5, high = SSP5-8.5, upper = SSP5-8.5 high end (planning). Default high.
- `storm_surge` (boolean): Add an extreme storm surge and high tide (+1.3 m) on top.
- `year` (integer): A year, 2025-2150 (with scenario), instead of rise_m.

### `sources_and_method` (~51 tokens)

What the numbers are made from, their licences, and their limits. Read this before quoting any figure.

Input parameters:

- `lang` (string): Language of the answer: "en" (default) or "fr".

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/mazeasdamien-rising-shores-singapore/risingshores#diagnostics

## Score history

- 2026-10-19: 65
- 2026-10-18: 64
- 2026-10-17: 64
- 2026-10-16: 63

## Common questions

### What is the Rising Shores Singapore MCP server?

Rising Shores Singapore is an MCP server listed in the public MCP registry as io.github.mazeasdamien/rising-shores-singapore. Sea-level rise in Singapore: when a place or address floods, areas and people affected, IPCC AR6. This page covers its hosted endpoint (https://risingshores.agentxr.app/mcp).

### Is the Rising Shores Singapore MCP server safe to use?

Rising Shores Singapore scores 65 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 Rising Shores Singapore MCP server expose?

Rising Shores Singapore exposes 10 tools: sea_level, when_does_it_flood, check_address, flood_impact, area_impact, and 5 more. Their descriptions and schemas cost roughly 1,354 tokens of context every time the server is loaded.

### Does the Rising Shores Singapore MCP server require authentication?

No. We connected to Rising Shores Singapore without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Rising Shores Singapore MCP server still maintained?

Rising Shores Singapore is still listed as active in the MCP registry. We last reached this channel on 19 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://risingshores.agentxr.app/mcp
- Repository: https://github.com/mazeasdamien/rising-shores-sg
- Website: https://risingshores.agentxr.app/
- Changelog RSS feed: https://verifymcp.io/servers/mazeasdamien-rising-shores-singapore/risingshores.xml
- Changelog JSON feed: https://verifymcp.io/servers/mazeasdamien-rising-shores-singapore/risingshores.json
- HTML version of this page: https://verifymcp.io/servers/mazeasdamien-rising-shores-singapore/risingshores