AISB is built MCP-native. Every BEAST OS surface that produces auditable output — squad recommendations, IPMVP M&V envelopes, code-keeper jurisdictional verdicts, retrofit compliance scans, Hybrid Calibrator demand curves, embodied carbon trackers — is exposed as a Model Context Protocol tool surface that any compliant client agent can call. The platform is open by architectural commitment, not by marketing slogan.
The reason matters. The institutional CRE buyer market in 2026 is being primed by AI-native acquisition and brokerage platforms — Cherre, Dealpath, Cactus AI, the new Crexi AI launch, Fifth Dimension's Series A — but the operating-asset side of the asset class is structurally underserved. Anthropic's nine new data connectors in Q2 2026 all target finance data; none of them target Procore, Autodesk Construction Cloud, Aconex, e-Builder, or the construction-management substrate where actual building operations live. That whitespace is the AISB lane, and the way to make it durable is to ship the integration surface as an open protocol rather than a private API.
Why MCP, And Why Now
Three signals converge on MCP as the right developer integration substrate:
- Anthropic's MCP standard has grown to more than 10,000 community-published MCP servers as of Q2 2026, with 97 million SDK downloads. The protocol has crossed the threshold from emerging convention to default expectation for agent-to-agent integration.
- RealEstateCore — the ontology backbone for smart building data interoperability, governed by ProptechOS and a multi-vendor consortium — has converged with IFC 4.3 and Speckle.dev open standards for geometric and semantic model exchange. The data-model substrate is converging.
- The 88% pilot failure rate in CRE AI (Deloitte 2026, Schneider Sustainability Research 2026) decomposes into 64% eval-gap failures, 57% governance failures, and 51% reliability failures. Buyers are not asking for more closed black-box vendor APIs; they are asking for surfaces that can be audited, replaced, and federated.
MCP is the integration-layer answer to the governance and replaceability concerns. RealEstateCore plus IFC plus Speckle is the data-model answer to the same concerns. Together they form a stack that an enterprise procurement team can endorse on the same compliance posture as their existing vendor controls.
The BEAST OS Tool Surface
The following tool families are exposed via MCP and addressable by any compliant client agent. Authentication is per-client API key; rate limiting and per-call audit logs are first-class. Every tool returns provenance metadata — IPMVP option, ASHRAE anchor, jurisdictional code reference, confidence score — alongside its payload.
| Tool family | What it does | Anchored standards | Squad source |
|---|---|---|---|
| code-keeper | Jurisdictional code intelligence — IBC, ASHRAE 90.1, ADA, NEC, NFPA, SG CORENET X, HK BD, JP BSL, AU NCC, UK Building Regs, EU EPBD. Code-triggered upgrade detection, permit-risk forecasting. | IBC 2024, ASHRAE 90.1-2022, CORENET X (SG), EPBD 2024 recast | CRE-AD |
| retrofit-compliance-scan | Detects code-triggered upgrade obligations when owners modify existing buildings. Quarterly drift detection against updated jurisdictional packs. | Per-jurisdiction code pack + ASTM E2018-15 anchoring | CRE-AD |
| ipmvp-mv | Measurement and verification under IPMVP Options A/B/C/D with explicit uncertainty reporting and CV(RMSE) gates. Energy-savings claims are auditable, not asserted. | IPMVP 2022, ASHRAE Guideline 14, FEMP M&V Guidelines | CRE-TS |
| hybrid-calibrator | Translates per-client hybrid work policy into peak simultaneous headcount and a demand curve. Detects policy-space mismatch before it becomes a desk-shortage incident. | BOMA floor efficiency, ASHRAE 62.1 ventilation | CRE-SP |
| evm-theater-detection | Cross-checks earned value against Last Planner PPC and procurement progress to catch reports that look done but are not. | AACE TCM, Last Planner System (LCI) | CRE-PM |
| claims-early-warning | Pattern detection across RFIs, change orders, daily reports, meeting minutes, schedule variance, weather, and safety signals. Predicts construction claims 30 to 60 days ahead of formal filing. | AIA A201, FIDIC, advisory-only framing | CRE-CON |
| embodied-carbon-tracker | Real-time embodied carbon accounting during construction execution. LEED v4.1, ILFI, EC3 anchored. Tracks scope-change carbon impact alongside cost and schedule. | EC3, EN 15978, ISO 14040, LEED v4.1 | CRE-CON |
| privacy-broker | Privacy-first fusion gate for occupancy-sensor outputs. Differential privacy noise (Laplace, ε-budget per zone per day) plus k-anonymity floor plus regional consent enforcement. | GDPR Art.9, EU AI Act, BIPA, CCPA, Colorado biometric, SG PDPA | CRE-EN |
| pca-template | Property Condition Assessment template generation and section drafting per ASTM E2018-15, with commissioning and retro-commissioning hooks per ASHRAE Guideline 0. | ASTM E2018-15, ASHRAE Guideline 0 | CRE-TS |
Compatibility With The Open-Stack Substrate
AISB does not ask buyers to commit to a closed data model. The BEAST OS tool surface is compatible with the three open substrates that the CRE technology field is converging on:
- RealEstateCore as the building semantic ontology. AISB tool outputs reference REC entity types where applicable, and the tool surface accepts REC-keyed queries against client building data.
- IFC 4.3 (Industry Foundation Classes, buildingSMART) as the geometric and semantic model exchange format. CRE-AD generative-concept and CRE-AD coordination tool outputs are IFC-native rather than tied to a specific BIM-authoring vendor.
- Speckle.dev as the open data-flow substrate across BIM, geometry, and analysis tools. Where Forma, Hypar, TestFit, or Finch3D outputs are involved, Speckle is the conduit rather than a vendor's proprietary cloud.
The intent is explicit: a buyer who adopts BEAST OS today and decides in three years to migrate to a different stack should not encounter a data-extraction tax. The protocol surface, the data model, and the geometric exchange are open by commitment.
Audit Trail Is First-Class
Every MCP tool call is logged with full provenance — the calling agent identity, the tool family, the request payload hash, the response payload hash, the confidence score, the IPMVP option or ASHRAE anchor cited, and the timestamp. The audit ledger is append-only, content-addressed, and replayable. For regulated buyers — EU AI Act Article 9 high-risk system documentation, NIS2 incident reporting, SOC 2 control evidence — the audit trail is the artifact the procurement legal team will ask for. AISB ships it by default.
Onboarding
The developer onboarding path is intentionally minimal. There is no SDK installer to chase, no proprietary CLI, no closed-source library to vendor. The MCP surface is the integration; the documentation, sample client invocations, and per-tool envelope schemas are the artifacts a developer needs.
For partner agents, integrators, and enterprise procurement teams: reach the AISB team through the Agent Door to scope a developer engagement. For pilot conversations, the Enterprise page covers the BEAST-in-a-Box deployment options. For the architectural posture that anchors the integration commitment, The Open-Protocol Moat spells out why owner-side platform choice is the durable position.
Companion Reading
- The CRE Standards Gap — why BACnet, Modbus, LonWorks, KNX, and OPC UA fragmentation is the moat that MCP-native architecture crosses
- EU AI Act Readiness — procurement-friendly posture surface mapping BEAST OS primitives to Article 9 / Annex III / Article 14
- IPMVP Verification — the M&V backbone every tool output references
- The Open-Protocol Moat — architectural commitment that anchors the integration posture
- Enterprise — BEAST-in-a-Box deployment options for portfolio-scale buyers
Standards referenced: Model Context Protocol (Anthropic, 2024+), RealEstateCore (ProptechOS), IFC 4.3 (buildingSMART), Speckle.dev, IBC 2024, ASHRAE 90.1-2022 / Guideline 0 / Guideline 14, IPMVP 2022, ASTM E2018-15, EC3, EN 15978, ISO 14040, LEED v4.1, GDPR Art.9, EU AI Act, EU NIS2, AIA A201, FIDIC, AACE TCM, BIPA, CCPA, Colorado biometric, SG PDPA, SG CORENET X, HK BD, JP BSL, AU NCC, UK Building Regs, EU EPBD 2024 recast.
Companion reading
CBRE's 2026 Workplace Survey put the gap between 79% peak-day utilization and 54% portfolio average at 25 points — the single largest utilization-architecture story in CRE this year. Same closed-loop discipline (Detect → Decide → Verify with IPMVP Option D anchoring) that closes the AI-pilot 88% gap closes the utilization 25-point gap.