Plan Comply — SANS 10400 Building Plan Pre-Screening AI
REMOTE · API.PLANCOMPLY.CO.ZA
SANS 10400 architectural building plan compliance checks, municipal checklists, and SLA lookups.
Available components
Last scanned (3 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 5 Nov 2026.
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 7 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 Usability67
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1150 tokens (~164/item across 7 items; 7 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 Management23
- Stability observed for 7 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 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.
- 1 Nov 26 −6
- Authorization: partial → unverified ▼ security
- Tool “calculate_sans_fenestration” rewrote its description, which is the text the model reads security
- Tool “calculate_stair_compliance” rewrote its description, which is the text the model reads security
- Tool “check_municipal_requirements” rewrote its description, which is the text the model reads security
- Tool “get_common_rejection_pitfalls” rewrote its description, which is the text the model reads security
- Tool “get_credit_pricing” rewrote its description, which is the text the model reads security
- Tool “get_sans_rules” rewrote its description, which is the text the model reads security
- Tool “pre_check_building_plan” rewrote its description, which is the text the model reads security
- Schema quality: 359 → 164 ▲ functional
- The server now declares the “prompts” capability functional
- The server now declares the “resources” capability functional
- Schema quality: excellent → good functional
- “calculate_sans_fenestration” reworded the description of “actual_glazed_area_m2” cosmetic
- “calculate_sans_fenestration” reworded the description of “actual_openable_area_m2” cosmetic
- “calculate_sans_fenestration” reworded the description of “floor_area_m2” cosmetic
- “calculate_sans_fenestration” reworded the description of “room_name” cosmetic
- “calculate_stair_compliance” reworded the description of “baluster_gap_mm” cosmetic
- “calculate_stair_compliance” reworded the description of “balustrade_height_mm” cosmetic
- “calculate_stair_compliance” reworded the description of “going_mm” cosmetic
- “calculate_stair_compliance” reworded the description of “headroom_mm” cosmetic
- “calculate_stair_compliance” reworded the description of “riser_mm” cosmetic
- “check_municipal_requirements” reworded the description of “municipality” cosmetic
- “get_sans_rules” reworded the description of “category” cosmetic
- “get_sans_rules” reworded the description of “sans_part” cosmetic
- “pre_check_building_plan” reworded the description of “external_wall_thickness_mm” cosmetic
- “pre_check_building_plan” reworded the description of “gully_height_above_ground_mm” cosmetic
- “pre_check_building_plan” reworded the description of “habitable_room_height_mm” cosmetic
- “pre_check_building_plan” reworded the description of “has_rodding_eyes_at_bends” cosmetic
- “pre_check_building_plan” reworded the description of “has_sacap_declaration” cosmetic
- “pre_check_building_plan” reworded the description of “has_safety_glass_below_800mm” cosmetic
- “pre_check_building_plan” reworded the description of “has_sans_forms” cosmetic
- “pre_check_building_plan” reworded the description of “municipality” cosmetic
- “pre_check_building_plan” reworded the description of “project_name” cosmetic
- Tool “calculate_sans_fenestration” changed its title: Calculate Sans Fenestration cosmetic
- Tool “calculate_stair_compliance” changed its title: Calculate Stair Compliance cosmetic
- Tool “check_municipal_requirements” changed its title: Check Municipal Requirements cosmetic
- Tool “get_common_rejection_pitfalls” changed its title: Get Common Rejection Pitfalls cosmetic
- Tool “get_credit_pricing” changed its title: Get Credit Pricing cosmetic
- Tool “get_sans_rules” changed its title: Get Sans Rules cosmetic
- Tool “pre_check_building_plan” changed its title: Pre Check Building Plan cosmetic
- 31 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.
- 30 Oct 26 +7
- Authorization: unverified → partial ▲ security
- Tool “calculate_sans_fenestration” rewrote its description, which is the text the model reads security
- Tool “calculate_stair_compliance” rewrote its description, which is the text the model reads security
- Tool “check_municipal_requirements” rewrote its description, which is the text the model reads security
- Tool “get_common_rejection_pitfalls” rewrote its description, which is the text the model reads security
- Tool “get_credit_pricing” rewrote its description, which is the text the model reads security
- Tool “get_sans_rules” rewrote its description, which is the text the model reads security
- Tool “pre_check_building_plan” rewrote its description, which is the text the model reads security
- Schema quality: 164 → 359 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Schema quality: good → excellent functional
- “pre_check_building_plan” reworded the description of “municipality” cosmetic
- “pre_check_building_plan” reworded the description of “project_name” cosmetic
- “calculate_sans_fenestration” reworded the description of “actual_glazed_area_m2” cosmetic
- “calculate_sans_fenestration” reworded the description of “actual_openable_area_m2” cosmetic
- “calculate_sans_fenestration” reworded the description of “floor_area_m2” cosmetic
- “calculate_sans_fenestration” reworded the description of “room_name” cosmetic
- “calculate_stair_compliance” reworded the description of “baluster_gap_mm” cosmetic
- “calculate_stair_compliance” reworded the description of “balustrade_height_mm” cosmetic
- “calculate_stair_compliance” reworded the description of “going_mm” cosmetic
- “calculate_stair_compliance” reworded the description of “headroom_mm” cosmetic
- “calculate_stair_compliance” reworded the description of “riser_mm” cosmetic
- “check_municipal_requirements” reworded the description of “municipality” cosmetic
- “get_sans_rules” reworded the description of “category” cosmetic
- “get_sans_rules” reworded the description of “sans_part” cosmetic
- “pre_check_building_plan” reworded the description of “external_wall_thickness_mm” cosmetic
- “pre_check_building_plan” reworded the description of “gully_height_above_ground_mm” cosmetic
- “pre_check_building_plan” reworded the description of “habitable_room_height_mm” cosmetic
- “pre_check_building_plan” reworded the description of “has_rodding_eyes_at_bends” cosmetic
- “pre_check_building_plan” reworded the description of “has_sacap_declaration” cosmetic
- “pre_check_building_plan” reworded the description of “has_safety_glass_below_800mm” cosmetic
- “pre_check_building_plan” reworded the description of “has_sans_forms” cosmetic
- Tool “calculate_sans_fenestration” changed its title: Calculate Sans Fenestration cosmetic
- Tool “calculate_stair_compliance” changed its title: Calculate Stair Compliance cosmetic
- Tool “check_municipal_requirements” changed its title: Check Municipal Requirements cosmetic
- Tool “get_common_rejection_pitfalls” changed its title: Get Common Rejection Pitfalls cosmetic
- Tool “get_credit_pricing” changed its title: Get Credit Pricing cosmetic
- Tool “get_sans_rules” changed its title: Get Sans Rules cosmetic
- Tool “pre_check_building_plan” changed its title: Pre Check Building Plan cosmetic
- 29 Oct 26 65
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://api.plancomply.co.za/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=plancomply.co.za | CN=WE1,O=Google Trust Services,C=US | 22 Sept 2026 | 21 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 67995b068d8dc7a813d16a04b48ed5bc |
| SANs: plancomply.co.za, api.plancomply.co.za, *.api.plancomply.co.za | ||||||
| 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 api.plancomply.co.za. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| za. | present | 45749 | 8 | Verified |
| co.za. | present | 41369 | 8 | Verified |
| plancomply.co.za. | 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=0; includeSubDomains; preload |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.plancomply.co.za/mcp | Verified | 200 | |
| http (plaintext) | http://api.plancomply.co.za/mcp | HTTPS enforced | 301 | https://api.plancomply.co.za/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 →
calculate_sans_fenestration ~157
Calculate SANS 10400-O statutory natural lighting (min. 10% floor area) and natural ventilation (min. 5% openable sash area) compliance for habitable rooms.
| Name | Type | Req | Description |
|---|---|---|---|
| actual_glazed_area_m2 | number | – | Total installed window glazed area in square metres (m²). |
| actual_openable_area_m2 | number | – | Total installed clear openable window sash ventilation area in square metres (m²). |
| floor_area_m2 | number | yes | Internal floor area of the habitable room in square metres (m²). |
| room_name | string | – | Name or label of the habitable room (e.g. "Bedroom 1", "Living Room", "Study"). |
No output schema declared.
No examples provided.
calculate_stair_compliance ~214
Evaluate stairway geometry and life safety against SANS 10400-M standards (riser max 200 mm, going min 250 mm, 2R + G formula 570-650 mm, headroom min 2,100 mm).
| Name | Type | Req | Description |
|---|---|---|---|
| baluster_gap_mm | number | – | Maximum clear gap between vertical balusters in millimetres (must not exceed 100 mm). |
| balustrade_height_mm | number | – | Height of balustrade in millimetres (min. 1,000 mm on landings, 850 mm on flights). |
| going_mm | number | yes | Stair tread horizontal going in millimetres excluding nosing (must not be less than 250 mm). |
| headroom_mm | number | – | Vertical headroom clearance in millimetres measured vertically from the nosing pitch line (must be min. 2,100 mm). |
| riser_mm | number | yes | Stair riser vertical height in millimetres (must not exceed 200 mm). |
No output schema declared.
No examples provided.
check_municipal_requirements ~104
Retrieve submission document checklists, statutory forms (Form 1/2), geotechnical/dolomite rules, and common rejection delay factors for South African metropolitan municipalities.
| Name | Type | Req | Description |
|---|---|---|---|
| municipality | string | yes | Municipality name or abbreviation (e.g. "City of Johannesburg", "COJ", "Tshwane", "Pretoria", "City of Cape Town", "COCT", "Ekurhuleni", "eThekwini", "Durban"). |
No output schema declared.
No examples provided.
get_common_rejection_pitfalls ~51
Retrieve top 25 common reasons municipal building control examiners reject building plans in South Africa, accompanied by verified remediation steps.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional category filter. Defaults to all. |
No output schema declared.
No examples provided.
get_credit_pricing ~30
Retrieve official Plan Comply pre-submission plan audit credit packages, volume discounts, and checkout details.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_sans_rules ~175
Search and query South African National Building Regulations (SANS 10400) clauses by Part (A to XA) or category (Dimensions, Glazing, Fire, Ventilation, Drainage, Stairs, Walls, Documentation).
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Category filter (e.g. "Dimensions", "Glazing", "Stairways", "Fire Safety", "Drainage", "Walls", "Energy Efficiency"). |
| query | string | – | Optional keyword search term to match within rule titles, descriptions, and guidance notes. |
| sans_part | string | – | SANS 10400 Part identifier (e.g. "Part A", "Part C", "Part K", "Part M", "Part N", "Part O", "Part P", "Part S", "Part T", "Part XA"). |
No output schema declared.
No examples provided.
pre_check_building_plan ~419
Run an automated multi-point regulatory validation on building plan specifications and return a compliance readiness score, defect warnings, and submission checklist.
| Name | Type | Req | Description |
|---|---|---|---|
| building_class | string | – | Occupancy classification (e.g. "H4 Single Dwelling House", "H3 Multi-Dwelling", "G1 Offices", "F1 Retail"). Default is "H4 Single Dwelling House". |
| external_wall_thickness_mm | number | – | External wall thickness in millimetres (standard cavity wall is min. 270 mm). |
| gully_height_above_ground_mm | number | – | Height of sewer gully head coping above finished ground level in millimetres (min. 150 mm). |
| habitable_room_height_mm | number | – | Specified clear finished floor-to-ceiling height in habitable rooms in millimetres (min. 2,400 mm). |
| has_renewable_water_heating | boolean | – | Whether min. 50% solar water heating or heat pump is specified as required by SANS 10400-XA. |
| has_rodding_eyes_at_bends | boolean | – | Whether rodding eyes or inspection chambers are provided at drainage bends > 45° and junctions. |
| has_sacap_declaration | boolean | – | Whether the drawing title block contains the registered architectural professional full name, registration number, category, and signature. |
| has_safety_glass_below_800mm | boolean | – | Whether safety glass (SANS 1263-1) is specified for all glazing with sill < 800 mm from FFL. |
| has_sans_forms | boolean | – | Whether SANS 10400 Form 1 and Form 2 (if structural work included) are prepared. |
| municipality | string | yes | Target South African municipality for plan submission (e.g. "City of Johannesburg", "Tshwane", "City of Cape Town", "Ekurhuleni", "eThekwini"). |
| project_name | string | – | Name of the building or architectural project. |
No output schema declared.
No examples provided.
How do I install the Plan Comply — SANS 10400 Building Plan Pre-Screening AI MCP server?
Plan Comply — SANS 10400 Building Plan Pre-Screening AI is a hosted endpoint at https://api.plancomply.co.za/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 · api.plancomply.co.za
claude mcp add --transport http za-co-plancomply-plancomply-mcp 'https://api.plancomply.co.za/mcp'
What is the Plan Comply — SANS 10400 Building Plan Pre-Screening AI MCP server?
Plan Comply — SANS 10400 Building Plan Pre-Screening AI is an MCP server listed in the public MCP registry as za.co.plancomply/plancomply-mcp. SANS 10400 architectural building plan compliance checks, municipal checklists, and SLA lookups. This page covers its hosted endpoint (https://api.plancomply.co.za/mcp).
Is the Plan Comply — SANS 10400 Building Plan Pre-Screening AI MCP server safe to use?
Plan Comply — SANS 10400 Building Plan Pre-Screening AI 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 Plan Comply — SANS 10400 Building Plan Pre-Screening AI MCP server expose?
Plan Comply — SANS 10400 Building Plan Pre-Screening AI exposes 7 tools: get_sans_rules, check_municipal_requirements, get_common_rejection_pitfalls, calculate_sans_fenestration, calculate_stair_compliance, and 2 more. Their descriptions and schemas cost roughly 1,150 tokens of context every time the server is loaded.
Does the Plan Comply — SANS 10400 Building Plan Pre-Screening AI MCP server require authentication?
No. We connected to Plan Comply — SANS 10400 Building Plan Pre-Screening AI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Plan Comply — SANS 10400 Building Plan Pre-Screening AI MCP server still maintained?
Plan Comply — SANS 10400 Building Plan Pre-Screening AI 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.