mcpbeat Sign in

Rising Shores Singapore MCP Server

by mazeasdamien Your server? Claim it
answering

Rising Shores Singapore is answering right now. Last checked 4 min ago. It exposes 10 tools.

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

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 25 days of history · worst day 99%
25 days agonow
100.0%
Uptime 24h
91 of 91 checks
10
Tools
read from the server
138 ms
Response time
average over 24h
open, no key
Access
streamable-http

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

run in your terminal
claude mcp add rising-shores-singapore --transport http https://risingshores.agentxr.app/mcp
Settings → Connectors → Add custom connector, then paste this address
https://risingshores.agentxr.app/mcp
~/.codex/config.toml
[mcp_servers.rising-shores-singapore]
url = "https://risingshores.agentxr.app/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "rising-shores-singapore": {
      "url": "https://risingshores.agentxr.app/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "rising-shores-singapore": {
      "type": "http",
      "url": "https://risingshores.agentxr.app/mcp"
    }
  }
}

Available tools 10

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

address
check_address
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.
area
area_impact
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.
areas
list_areas
The 55 URA planning areas the impact tools accept, with their resident populations.
flood
flood_impact
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.
map
map_link
A link that opens the Rising Shores map with the sea raised to a given rise (or a year and scenario).
most
most_affected_areas
The planning areas with the most residents in flooded areas at a sea-level rise (or a year and scenario).
places
places_underwater
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.
sea
sea_level
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.
sources
sources_and_method
What the numbers are made from, their licences, and their limits. Read this before quoting any figure.
when
when_does_it_flood
In which year each scenario reaches a given sea-level rise (metres above today's high tide), or "beyond 2150".

Endpoints

URLTransportStateLatencyChecked
https://risingshores.agentxr.app/mcp streamable-http answering 164 ms 4 min ago

Alternatives to Rising Shores Singapore

same job, measured the same way
IPCC AR6 Climate Retrieval
by aswanisahoo

Search IPCC AR6 WG1 and answer with page-level citations, or refuse when unsupported.

local only
W
Westbahnhof Studio
by workers-moran-studio-relay-moran-studio-relay

A place where nothing is expected of you: Moran in Vienna shares her real day and remembers you.

8 tools answering
Research Scope
by axelvernebooks

Plan research, score sources for freshness/COI, and enforce claim-level citations in reports.

local only
MCP Google Maps Places Scraper
by mambabuilt

Search Google Maps and get one row per place: phone, website, address, rating, and hours.

local only
P
ParcelSheet
by parcelsheet

Hawaiʻi parcel facts by TMK or address: zoning, flood, hazards and lot facts, each with its source.

6 tools answering
ish
by ishlabs

Simulated people experience what you are making and report what they noticed and felt.

answering
Buildability
by buildability

Source-cited, address-level answers on zoning, site constraints, permitting and what can be built.

12 tools answering
AIsa Social
by aisa

What people post and say across the major social platforms, in one place.

answering

Rising Shores Singapore — questions

Answers built from our own checks of this server.

What can Rising Shores Singapore do?
It exposes 10 tools, read directly from the server on our last check. Among them: area_impact, check_address, flood_impact, list_areas, map_link, most_affected_areas and 4 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Rising Shores Singapore working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 138 ms. The bar chart above shows every period we have measured.
Is Rising Shores Singapore still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect Rising Shores Singapore?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Rising Shores Singapore need an API key?
No. Rising Shores Singapore completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 10 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Rising Shores Singapore?
It answers our handshake in 138 ms on average, which is faster than 85% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.