Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

SG Parking Live

REMOTE · SG-PARKING-LIVE.ROWB.APP

Live HDB carpark availability for Singapore from the official data.gov.sg feed.

+3 this week 66 Trust /100

Last scanned (20 hours ago)

Scores higher than 56% of remote servers

Reachable. Last reached 18 Oct 2026.

Category Maps and Location

Trust breakdown (7 categories)

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 Security46
Transport & Reachability100
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 213 tokens (~53/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
  • Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
Changelog

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.

  • 16 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 33. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Oct 26 +2

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 27. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 17. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 4 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 2 Oct 26 59

    First indexed and scored.

Diagnostics

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 18 Oct 2026 · Probed https://sg-parking-live.rowb.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=rowb.app CN=WE1,O=Google Trust Services,C=US 2 Oct 2026 31 Dec 2026 ECDSA 256 ECDSA-SHA256 6f7fdde864afbb7c13f80c26d1684cc7
SANs: rowb.app, sg-parking-live.rowb.app, *.sg-parking-live.rowb.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 sg-parking-live.rowb.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
rowb.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://sg-parking-live.rowb.app/mcp Verified 200
http (plaintext) http://sg-parking-live.rowb.app/mcp Inconclusive 405
MCP tools · 4 exposed · ~213 tokens

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 →

Tool Tokens
get_carpark_availability ~47

Current lots available per lot type for one HDB carpark code (live from data.gov.sg).

NameTypeReqDescription
codestringyescarpark code, e.g. HE12

No output schema declared.

No examples provided.

get_carpark_history ~67

Our stored snapshot history for one carpark code (availability sampled since launch). Deterministic read of our own snapshots.

NameTypeReqDescription
codestringyescarpark code, e.g. HE12
limitinteger–max snapshots (default 50, cap 500)

No output schema declared.

No examples provided.

health_check ~33

Report whether this service is up and which version answered. Use it to confirm the endpoint is reachable before running a real job.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_carparks ~66

List HDB carpark codes known from the live Singapore data.gov.sg feed (optionally filtered by code prefix).

NameTypeReqDescription
limitinteger–max entries (default 50, cap 200)
prefixstring–carpark code prefix filter, e.g. HE

No output schema declared.

No examples provided.

Install

How do I install the SG Parking Live MCP server?

SG Parking Live is a hosted endpoint at https://sg-parking-live.rowb.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 · sg-parking-live.rowb.app

# add to Claude Code
claude mcp add --transport http app-rowb-sg-parking-live-carpark-availability 'https://sg-parking-live.rowb.app/mcp'
Common questions

What is the SG Parking Live MCP server?

SG Parking Live is an MCP server listed in the public MCP registry as app.rowb.sg-parking-live/carpark-availability. Live HDB carpark availability for Singapore from the official data.gov.sg feed. This page covers its hosted endpoint (https://sg-parking-live.rowb.app/mcp).

Is the SG Parking Live MCP server safe to use?

SG Parking Live scores 66 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 SG Parking Live MCP server expose?

SG Parking Live exposes 4 tools: health_check, list_carparks, get_carpark_availability, get_carpark_history. Their descriptions and schemas cost roughly 213 tokens of context every time the server is loaded.

Does the SG Parking Live MCP server require authentication?

No. We connected to SG Parking Live without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the SG Parking Live MCP server still maintained?

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