Rising Shores Singapore
REMOTE · RISINGSHORES.AGENTXR.APP
Sea-level rise in Singapore: when a place or address floods, areas and people affected, IPCC AR6.
Available components
Last scanned (1 hour ago)
Scores higher than 47% of remote servers
Reachable. Last reached 19 Oct 2026.
Category Maps and Location
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability66
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 98% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 19 Oct 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.
- 17 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 16 Oct 26 63
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 19 Oct 2026 · Probed https://risingshores.agentxr.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agentxr.app | CN=WE1,O=Google Trust Services,C=US | 8 Oct 2026 | 6 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 53eae6f7b2e24cfa13bcd67b6926442e |
| SANs: agentxr.app, risingshores.agentxr.app, *.risingshores.agentxr.app | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of risingshores.agentxr.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| agentxr.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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://risingshores.agentxr.app/mcp | Verified | 200 | |
| http (plaintext) | http://risingshores.agentxr.app/mcp | Inconclusive | 405 |
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 →
area_impact ~205
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.
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | yes | 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. |
No output schema declared.
No examples provided.
check_address ~81
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.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language of the answer: "en" (default) or "fr". |
| query | string | yes | A postal code (e.g. 018956) or a place name. |
No output schema declared.
No examples provided.
flood_impact ~172
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
list_areas ~47
The 55 URA planning areas the impact tools accept, with their resident populations.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language of the answer: "en" (default) or "fr". |
No output schema declared.
No examples provided.
map_link ~163
A link that opens the Rising Shores map with the sea raised to a given rise (or a year and scenario).
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
most_affected_areas ~183
The planning areas with the most residents in flooded areas at a sea-level rise (or a year and scenario).
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
places_underwater ~207
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
sea_level ~163
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | A year, 2025-2150 (with scenario), instead of rise_m. |
No output schema declared.
No examples provided.
sources_and_method ~51
What the numbers are made from, their licences, and their limits. Read this before quoting any figure.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language of the answer: "en" (default) or "fr". |
No output schema declared.
No examples provided.
when_does_it_flood ~82
In which year each scenario reaches a given sea-level rise (metres above today's high tide), or "beyond 2150".
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language of the answer: "en" (default) or "fr". |
| rise_m | number | yes | Sea-level rise in metres above today's mean high water (0-9). |
No output schema declared.
No examples provided.
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.
remote · risingshores.agentxr.app
claude mcp add --transport http mazeasdamien-rising-shores-singapore 'https://risingshores.agentxr.app/mcp'
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.