Analytics

agentxr.app

Provides tools for querying projected sea-level rise and flood impacts in Singapore by year, emissions scenario, address, or planning area.

1 endpoint10 known toolsFirst detected October 17, 2026Last detected October 17, 2026

ENDPOINT 1

https://risingshores.agentxr.app/mcp

No auth detected

MCP server metadata

Name: rising-shores-singapore
Version: 1.0.0

Capabilities

tools

Server instructions

Sea-level rise and flood impacts for Singapore, from the Rising Shores map. Levels are metres of rise above today's high-tide sea level; give rise_m, or year + scenario. Every tool takes lang "en" or "fr". Quote figures with their caveat; call sources_and_method before relying on them.

Known tools 10

sea_level

Projected sea-level rise at Singapore for a year and an emissions scenario (CCRS V3 2024, Ng et al.

Inferred read-only

when_does_it_flood

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

Inferred read-only

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.

Inferred read-only

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.

Inferred read-only

area_impact

Residents living in flooded parts of one planning area (e.

Inferred read-only

most_affected_areas

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

Inferred read-only

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.

Inferred read-only

list_areas

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

Inferred read-only

map_link

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

Inferred read-only

sources_and_method

What the numbers are made from, their licences, and their limits.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.rising-shores-singapore]
url = "https://risingshores.agentxr.app/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "rising-shores-singapore": {
      "type": "http",
      "url": "https://risingshores.agentxr.app/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: rising-shores-singapore
Remote MCP URL: https://risingshores.agentxr.app/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "rising-shores-singapore",
  "transport": "streamable-http",
  "url": "https://risingshores.agentxr.app/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.