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.
langyearrequiredscenariostorm_surge
io.github.mazeasdamienPublished by GitHub account mazeasdamienv1.0.0Updated Oct 26, 2026
Sea-level rise in Singapore: when a place or address floods, areas and people affected, IPCC AR6.
Remote MCP server that answers sea-level-rise questions for Singapore: projected rise, flood timing, affected areas, residents and places.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.mazeasdamien%2Frising-shores-singapore/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"rising-shores-singapore": {
"type": "http",
"url": "https://risingshores.agentxr.app/mcp"
}
}
}This repository has no README.
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.
langyearrequiredscenariostorm_surgeIn which year each scenario reaches a given sea-level rise (metres above today's high tide), or "beyond 2150".
langrise_mrequiredFor 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.
langqueryrequiredIsland-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.
langyearrise_mscenariostorm_surgeResidents 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.
arearequiredlangyearrise_mscenariostorm_surgeThe planning areas with the most residents in flooded areas at a sea-level rise (or a year and scenario).
nlangyearrise_mscenariostorm_surgeNamed public places (hawker centres, schools, places of worship) reached by the sea at a rise, optionally of one kind or in one planning area.
areakindlangyearlimitrise_mscenariostorm_surgeThe 55 URA planning areas the impact tools accept, with their resident populations.
langA link that opens the Rising Shores map with the sea raised to a given rise (or a year and scenario).
langyearrise_mscenariostorm_surgeWhat the numbers are made from, their licences, and their limits. Read this before quoting any figure.
lang75% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
Declare a license in the repository or the registry entry.