Singapore new launches
REMOTE · PROPERTY.BLUEBED.AI
Reviewed Singapore new-launch floor plans, area details and buyer rules. Trial.
Available components
Last scanned (4 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
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
- Authorisation not fully verified: no authorisation is required to call this server, and 11 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1648 tokens (~149/item across 11 items; 11 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 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 11 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 5 Nov 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.
- 3 Nov 26 0
- Tool “get_area” rewrote its description, which is the text the model reads security
- Tool “get_launch” rewrote its description, which is the text the model reads security
- Tool “list_launches” rewrote its description, which is the text the model reads security
- Tool “rules_for_buyer” rewrote its description, which is the text the model reads security
- Tool “search_floor_plans” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- “rules_for_buyer” added an optional parameter “slug” cosmetic
- “search_floor_plans” added an optional parameter “property_types” cosmetic
- 2 Nov 26 67
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 5 Nov 2026 · Probed https://property.bluebed.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.bluebed.ai | CN=YR1,O=Let's Encrypt,C=US | 18 Sept 2026 | 17 Dec 2026 | RSA 2048 | SHA256-RSA | 67be5a44b5056ea559e9c6b95e9b5c009e7 |
| SANs: *.bluebed.ai, bluebed.ai | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of property.bluebed.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| bluebed.ai. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://property.bluebed.ai/mcp | Verified | 200 | |
| http (plaintext) | http://property.bluebed.ai/mcp | HTTPS enforced | 308 | https://property.bluebed.ai/mcp |
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 →
about ~37
Says who runs this service, the agent's CEA registration and agency licence, how the service is paid for, and how to reach the agent.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
book_call ~68
Booking a call through your assistant is not open yet. Calling this holds nothing and takes no details: it returns a WhatsApp link to the agent, with a short neutral message already written, and the address of the contact page. Show your user the link if they want to talk to the agent.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
cancel_booking ~68
Booking a call through your assistant is not open yet. Calling this holds nothing and takes no details: it returns a WhatsApp link to the agent, with a short neutral message already written, and the address of the contact page. Show your user the link if they want to talk to the agent.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
check_booking ~68
Booking a call through your assistant is not open yet. Calling this holds nothing and takes no details: it returns a WhatsApp link to the agent, with a short neutral message already written, and the address of the contact page. Show your user the link if they want to talk to the agent.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
confirm_booking ~68
Booking a call through your assistant is not open yet. Calling this holds nothing and takes no details: it returns a WhatsApp link to the agent, with a short neutral message already written, and the address of the contact page. Show your user the link if they want to talk to the agent.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_area ~192
Returns the reviewed area details of a launch by slug: address, tenure, nearby amenities with straight-line distances, schools within two kilometres, and food places the agent has visited himself. Where the area has been measured, it also returns the three nearest MRT or LRT stations with straight-line and walking distances, stop counts to six key stations, and primary school bands per block, each labelled with its source and date. Schools are listed for orientation only and the reply says where to verify them. Available for launches that show area details in list_launches, even when floor plans are not yet available. Every answer carries its source, the date it was reviewed, the stage of the launch, and the agent's licence details. Anything the developer material does not settle is returned as a gap with the question to ask, never as a guess.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The launch slug, as returned by list_launches |
No output schema declared.
No examples provided.
get_launch ~158
Returns one launch by slug: its property type (condo or ec, which adds a notice on executive condominiums), its reviewed facts with source and page, the price statement with its kind and date, and the gaps the material leaves open. Prices are guidance from developer price lists: indicative before launch, reset on booking day, and subject to promotions afterwards. Treat them as a starting point and confirm with the agent. Every answer carries its source, the date it was reviewed, the stage of the launch, and the agent's licence details. Anything the developer material does not settle is returned as a gap with the question to ask, never as a guess.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The launch slug, as returned by list_launches |
No output schema declared.
No examples provided.
get_unit_type ~184
Returns one unit type of a launch by slug and type name: size, bathrooms, powder rooms and WCs, stacks (stacks_note explains an asterisk), the plan image, the answers read from the plan, and the questions the plan does not settle. Prices are guidance from developer price lists: indicative before launch, reset on booking day, and subject to promotions afterwards. Treat them as a starting point and confirm with the agent. Every answer carries its source, the date it was reviewed, the stage of the launch, and the agent's licence details. Anything the developer material does not settle is returned as a gap with the question to ask, never as a guess.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The launch slug, as returned by list_launches |
| type | string | yes | The unit type name, as returned by search_floor_plans or get_launch |
No output schema declared.
No examples provided.
list_launches ~118
Lists the new launches this service covers: name, property type (condo or ec, an executive condominium), district, street, number of units, stage, launch date, whether it is sold out, and whether floor plans and area details are available. It covers a selection of launches during the trial. Every answer carries its source, the date it was reviewed, the stage of the launch, and the agent's licence details. Anything the developer material does not settle is returned as a gap with the question to ask, never as a guess.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
rules_for_buyer ~260
Quotes the Singapore property rules that apply to a buyer, exactly as published, with the authority, source link, effective date and the date each was last checked: additional buyer's stamp duty, buyer's stamp duty, financing limits and seller's stamp duty. It quotes and does not work out any duty or rate; read the figure from the quote. Seller's stamp duty depends on the purchase date, so supply purchase_date to get the right regime. Supply slug for an executive condominium launch to add the EC rules that apply to its site. A rule that is being re-checked is named without its quote. This is general information and not advice on a particular purchase; confirm with the agent.
| Name | Type | Req | Description |
|---|---|---|---|
| profile | string | yes | The buyer's status: sc (Singapore Citizen), spr (Singapore Permanent Resident), foreigner or entity |
| properties_owned | number | yes | Residential properties the buyer already owns: 0, 1 or 2 (2 means two or more) |
| purchase_date | string | – | Date the property was or will be bought, as YYYY-MM-DD. Chooses the seller's stamp duty regime. |
| slug | string | – | A launch slug. For an executive condominium, the reply adds the EC rules for that site. |
No output schema declared.
No examples provided.
search_floor_plans ~427
Searches floor plans across the reviewed launches, a selection during the trial. Filter by property type (condo or ec), bedrooms, size in square feet, postal district, launch stage, features such as a kitchen window, and a maximum budget in Singapore dollars. Plans in matches meet every constraint you supplied; plans in close miss exactly one, or could not be checked on one, as shown in each plan's fit (met, missed or unknown). The close list holds at most 20 plans, those with the fewest unknowns first; close_total says how many came close and close_truncated whether some were left out, so narrow the filters to see them. Cull both lists against what your user actually wants. Each result gives the plan, its stacks (stacks_note explains an asterisk), a link to the plan image, and a price with its kind and date. When nothing matches or comes close, the reply names which filters excluded the plans. Prices are guidance from developer price lists: indicative before launch, reset on booking day, and subject to promotions afterwards. Treat them as a starting point and confirm with the agent. Every answer carries its source, the date it was reviewed, the stage of the launch, and the agent's licence details. Anything the developer material does not settle is returned as a gap with the question to ask, never as a guess.
| Name | Type | Req | Description |
|---|---|---|---|
| bedrooms | number | – | Whole number of bedrooms, 1 to 6 |
| budget_max | number | – | Maximum price in Singapore dollars |
| districts | array | – | Postal districts, 1 to 28 |
| include_sold_out | boolean | – | Include sold-out launches. Not scored as a constraint. |
| max_sqft | number | – | Maximum size in square feet |
| min_sqft | number | – | Minimum size in square feet |
| property_types | array | – | condo or ec. Leave out to include both. |
| stages | array | – | pre-marketing, preview, launch or after-launch |
| tags | array | – | Feature ids, for example kitchen_window |
No output schema declared.
No examples provided.
How do I install the Singapore new launches MCP server?
Singapore new launches is a hosted endpoint at https://property.bluebed.ai/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 · property.bluebed.ai
claude mcp add --transport http ai-bluebed-property-new-launches 'https://property.bluebed.ai/mcp'
What is the Singapore new launches MCP server?
Singapore new launches is an MCP server listed in the public MCP registry as ai.bluebed.property/new-launches. Reviewed Singapore new-launch floor plans, area details and buyer rules. Trial. This page covers its hosted endpoint (https://property.bluebed.ai/mcp).
Is the Singapore new launches MCP server safe to use?
Singapore new launches scores 68 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 Singapore new launches MCP server expose?
Singapore new launches exposes 11 tools: list_launches, search_floor_plans, get_launch, get_unit_type, get_area, and 6 more. Their descriptions and schemas cost roughly 1,648 tokens of context every time the server is loaded.
Does the Singapore new launches MCP server require authentication?
No. We connected to Singapore new launches without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Singapore new launches MCP server still maintained?
Singapore new launches is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.