Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Plan Comply — SANS 10400 Building Plan Pre-Screening AI is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
7
tools declared
remote
at its publisher
—
calls last 7d
What it does
SANS 10400 architectural building plan compliance checks, municipal checklists, and SLA lookups.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http plan-comply-sans-10400-building-plan-pre-scre-mcp https://api.plancomply.co.za/mcp
# 2 — ask your agent for something these tools do
# get_sans_rules, check_municipal_requirements, get_common_rejection_pitfalls and 4 more
Plan Comply — SANS 10400 Building Plan Pre-Screening AI costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
PLAll 1 server
plancomply1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http plan-comply-sans-10400-building-plan-pre-scre-mcp https://api.plancomply.co.za/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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). When to use: Call this tool when you specifically need to execute 'get_sans_rules' on Plan Comply SANS 10400 AI (plancomply.co.za). Do NOT use this tool when another specialized tool fits better (use 'check
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sans_part | string | no | 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"). [Optional: omit to use server default filter]. |
| category | string | no | Category filter (e.g. "Dimensions", "Glazing", "Stairways", "Fire Safety", "Drainage", "Walls", "Energy Efficiency"). [Optional: omit to use server default filter]. |
| query | string | no | Optional keyword search term to match within rule titles, descriptions, and guidance notes. |
Retrieve submission document checklists, statutory forms (Form 1/2), geotechnical/dolomite rules, and common rejection delay factors for South African metropolitan municipalities. When to use: Call this tool when you specifically need to execute 'check_municipal_requirements' on Plan Comply SANS 10400 AI (plancomply.co.za). Do NOT use this tool when another specialized tool fits better (use 'get_s
| Parameter | Type | Required | Notes |
|---|---|---|---|
| municipality | string | yes | Municipality name or abbreviation (e.g. "City of Johannesburg", "COJ", "Tshwane", "Pretoria", "City of Cape Town", "COCT", "Ekurhuleni", "eThekwini", "Durban"). [Required: non-empty valid value must b |
Retrieve top 25 common reasons municipal building control examiners reject building plans in South Africa, accompanied by verified remediation steps. When to use: Call this tool when you specifically need to execute 'get_common_rejection_pitfalls' on Plan Comply SANS 10400 AI (plancomply.co.za). Do NOT use this tool when another specialized tool fits better (use 'get_sans_rules' or 'check_municipa
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | no | Optional category filter. Defaults to all. |
Calculate SANS 10400-O statutory natural lighting (min. 10% floor area) and natural ventilation (min. 5% openable sash area) compliance for habitable rooms. When to use: Call this tool when you specifically need to execute 'calculate_sans_fenestration' on Plan Comply SANS 10400 AI (plancomply.co.za). Do NOT use this tool when another specialized tool fits better (use 'get_sans_rules' or 'check_mun
| Parameter | Type | Required | Notes |
|---|---|---|---|
| room_name | string | no | Name or label of the habitable room (e.g. "Bedroom 1", "Living Room", "Study"). [Optional: omit to use server default filter]. |
| floor_area_m2 | number | yes | Internal floor area of the habitable room in square metres (m²). [Required: non-empty valid value must be supplied]. |
| actual_glazed_area_m2 | number | no | Total installed window glazed area in square metres (m²). [Optional: omit to use server default filter]. |
| actual_openable_area_m2 | number | no | Total installed clear openable window sash ventilation area in square metres (m²). [Optional: omit to use server default filter]. |
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). When to use: Call this tool when you specifically need to execute 'calculate_stair_compliance' on Plan Comply SANS 10400 AI (plancomply.co.za). Do NOT use this tool when another specialized tool fits better (use 'get_sans_rules' or 'check
| Parameter | Type | Required | Notes |
|---|---|---|---|
| riser_mm | number | yes | Stair riser vertical height in millimetres (must not exceed 200 mm). [Required: non-empty valid value must be supplied]. |
| going_mm | number | yes | Stair tread horizontal going in millimetres excluding nosing (must not be less than 250 mm). [Required: non-empty valid value must be supplied]. |
| headroom_mm | number | no | Vertical headroom clearance in millimetres measured vertically from the nosing pitch line (must be min. 2,100 mm). [Optional: omit to use server default filter]. |
| balustrade_height_mm | number | no | Height of balustrade in millimetres (min. 1,000 mm on landings, 850 mm on flights). [Optional: omit to use server default filter]. |
| baluster_gap_mm | number | no | Maximum clear gap between vertical balusters in millimetres (must not exceed 100 mm). [Optional: omit to use server default filter]. |
Retrieve official Plan Comply pre-submission plan audit credit packages, volume discounts, and checkout details. When to use: Call this tool when you specifically need to execute 'get_credit_pricing' on Plan Comply SANS 10400 AI (plancomply.co.za). Do NOT use this tool when another specialized tool fits better (use 'get_sans_rules' or 'check_municipal_requirements' or 'get_common_rejection_pitfall
No parameter schema on file.
Run an automated multi-point regulatory validation on building plan specifications and return a compliance readiness score, defect warnings, and submission checklist. When to use: Call this tool when you specifically need to execute 'pre_check_building_plan' on Plan Comply SANS 10400 AI (plancomply.co.za). Do NOT use this tool when another specialized tool fits better (use 'get_sans_rules' or 'che
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_name | string | no | Name of the building or architectural project. [Optional: omit to use server default filter]. |
| municipality | string | yes | Target South African municipality for plan submission (e.g. "City of Johannesburg", "Tshwane", "City of Cape Town", "Ekurhuleni", "eThekwini"). [Required: non-empty valid value must be supplied]. |
| building_class | string | no | Occupancy classification (e.g. "H4 Single Dwelling House", "H3 Multi-Dwelling", "G1 Offices", "F1 Retail"). Default is "H4 Single Dwelling House". |
| habitable_room_height_mm | number | no | Specified clear finished floor-to-ceiling height in habitable rooms in millimetres (min. 2,400 mm). [Optional: omit to use server default filter]. |
| external_wall_thickness_mm | number | no | External wall thickness in millimetres (standard cavity wall is min. 270 mm). [Optional: omit to use server default filter]. |
| has_safety_glass_below_800mm | boolean | no | Whether safety glass (SANS 1263-1) is specified for all glazing with sill < 800 mm from FFL. [Optional: omit to use server default filter]. |
| has_sacap_declaration | boolean | no | Whether the drawing title block contains the registered architectural professional full name, registration number, category, and signature. [Optional: omit to use server default filter]. |
| has_sans_forms | boolean | no | Whether SANS 10400 Form 1 and Form 2 (if structural work included) are prepared. [Optional: omit to use server default filter]. |
| has_renewable_water_heating | boolean | no | Whether min. 50% solar water heating or heat pump is specified as required by SANS 10400-XA. |
| has_rodding_eyes_at_bends | boolean | no | Whether rodding eyes or inspection chambers are provided at drainage bends > 45° and junctions. [Optional: omit to use server default filter]. |
| gully_height_above_ground_mm | number | no | Height of sewer gully head coping above finished ground level in millimetres (min. 150 mm). [Optional: omit to use server default filter]. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Plan Comply — SANS 10400 Building Plan Pre-Screening AI or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 2.0.1 · scanned 30 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest0ac27009d9aa755d554245b97bf93cf6c4037f1ca63ead020661aa083908a885
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_sans_rules | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| check_municipal_requirements | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_common_rejection_pitfalls | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| calculate_sans_fenestration | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| calculate_stair_compliance | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_credit_pricing | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| pre_check_building_plan | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest0ac27009d9aa755d
Scanned2026-10-30
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 2.0.1.
2.0.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Plan Comply — SANS 10400 Building Plan Pre-Screening AI can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.