Plain thesis: McKinsey Sustainability's Frontier founding role and its own 100%-removals commitment are real and credited in full here. This brief also reports, plainly and without judgment, what a passive research pass actually found when it tried to read McKinsey's own website, because the answer (almost nothing) is itself the most distinctive fact we've found.
No jargon. McKinsey's climate work is real and credited in full; the fixes below are about the one thing this review actually found: a domain agents can't read. Here is what each one is worth.
Every plain request to mckinsey.com was refused this session, even robots.txt, the one file meant for automated clients; since mckinsey.org loads fine, tuning the edge to let legitimate agents read the sustainability story means the buyers using AI to evaluate advisors actually reach you.
Those landmark claims sit behind a domain agents can't reach, delivered as prose elsewhere; expressed as machine-readable fact, they're read accurately by the tools now doing this research instead of paraphrased or missed.
McKinsey's own "New at McKinsey" blog confirms it partnered with Stripe, Alphabet, Shopify, and Meta on the initial "$925 million carbon removal commitment" that became Frontier. Separately, McKinsey has validated 2025 near-term science-based emissions targets (1.5°C pathway vs. a 2019 baseline) and 2050 net-zero targets through SBTi.
Source: mckinsey.com/about-us/new-at-mckinsey-blog/mckinsey-partners-with-stripe-alphabet-shopify-and-meta-on-$925-million-carbon-removal-commitment (title/content corroborated via search index, live domain unreachable this session; see finding 3)
Beyond its Frontier membership, McKinsey states it is "committed to shifting its offset strategy to 100% carbon removals by 2030," moving away from traditional avoidance-based offsets toward both nature-based and technology-driven removal for its own residual emissions, one of the more concrete self-imposed removal-transition commitments we've found.
Source: mckinsey.com/about-us/environmental-sustainability (content corroborated via search index, live domain unreachable this session)
Every plain, passive attempt to read mckinsey.com this session failed: a direct curl to robots.txt stalled mid-TLS-handshake (connected, completed certificate verification, then no further response before timeout); a separate fetch of a sustainability sub-page returned a clean HTTP 403; repeated attempts with a browser-style User-Agent and forced HTTP/1.1 made no difference. This is consistent with an aggressive bot-management posture (commonly Akamai Bot Manager on large enterprise sites) rather than a broken server, and per this playbook's passive-only rule, no header-spoofing, TLS-fingerprint evasion, or browser-automation workaround was attempted. This brief reports what a plain client sees, which this session is: nothing.
Checked directly this session, 2026-07-16, both attempts against mckinsey.com
McKinsey's separate nonprofit-facing property, mckinsey.org, loaded without issue this session and shares the firm's real design system: its live stylesheet confirms the typefaces "McKinsey Sans" and "Bower", plus a navy/blue/gold palette, showing the block found in finding 3 is specific to the commercial marketing domain's edge configuration, not a firm-wide policy. Separately, and not a McKinsey-side finding: McKinsey Sustainability's own consulting rigor (abatement-cost curves, MRV-quality asks of clients) is the same kind of checkable, tCO2e-mapped methodology work EWP's 10,786-definition work library already runs at packet scale: a live, receipt-backed board instead of a bespoke one-off study, offered as an observation, not a pitch.
Source: mckinsey.org live CSS (fetched 2026-07-16) · EWP work library: internal working notes
McKinsey Sustainability's Frontier founding role and its own removals commitment are real, credited in full. The distinctive fact in this brief isn't a criticism; it's a structural observation: among the entities we've researched passively, mckinsey.com's edge is the only one that refused contact outright, even for a file (robots.txt) explicitly meant for automated clients. EWP's own posture runs the opposite way: every settlement is a public, checkable receipt from the first packet.
