Institutional concept · Not affiliated · Passive recon only · Unlisted
McKinsey helped design carbon removal's price mechanism. Its own front door is the hardest one we tried.
In one sentence: McKinsey Sustainability co-founded Frontier in 2022 (alongside Stripe, Alphabet, Shopify, and Meta) and has committed to shifting its own offsetting entirely to carbon removals by 2030, real, credited commitments, but its main commercial domain rejected every plain, passive request this session made of it, including robots.txt(the file that tells search engines what to index), making it the single most locked-down edge we've probed.
The whole thing, plainly
McKinsey helped start and fund the carbon-removal market, and has promised to switch its own offsetting fully to real removals by 2030, both real, credited commitments.
Its main website blocked every plain, ordinary request we made, even the file that's supposed to be open to everyone. There is no ask here, just an honest report of what we saw.
Relationship, stated plainlyEcoWealth is not affiliated with McKinsey & Company in any way: not a client, Frontier co-member, or engagement partner. No contact has been made with McKinsey & Company, McKinsey Sustainability, or any of its teams. Everything here is independent, unsolicited desk research built from McKinsey's own public pages and press coverage of them.
Read this first. Independent research by EcoWealth Corporation. Not requested, produced, reviewed, or endorsed by McKinsey & Company. Every figure below comes from McKinsey's own public statements (its Frontier partnership post, its environmental-sustainability commitments) plus independently re-verified HTTP checks: no scanning, fuzzing, application, sign-up, or contact anywhere. Staged locally, noindex, not sent to anyone without explicit operator review.
Four facts from the public record
Credit-first: the Frontier founding role and the 100%-removals-by-2030 shift are real. The gap is structural, not editorial: the domain itself refused plain contact.
Frontier founding member, 2022
Alongside Stripe, Alphabet, Shopify, and Meta, McKinsey's own blog post confirms the $925M initial commitment.
100% removals by 2030
SBTi-validated 2025 near-term + 2050 net-zero targets, plus an explicit shift from avoidance credits to removals for its own offsetting.
mckinsey.com blocked every plain GET
Even robots.txt: TLS handshake stalls / 403, consistent with an aggressive bot-management posture. No evasion attempted.
mckinsey.org, reachable
The nonprofit arm's domain loaded fine and shares the real design system (McKinsey Sans + Bower, confirmed live): the block is domain-specific.
What a plain GET sees on mckinsey.com
Nothing
TLS handshake stalls or a 403; even robots.txt was unreachable this session, with no header-spoofing attempted.
What one EWP packet settles
$0.05–$0.25
Fund → claim → prove → settle, fully readable on-chain: the opposite posture, by design.
The note, in one more page
Capability brief
An agent's-eye read of McKinsey's public commitments and its edge
Four evidenced findings: the Frontier founding credit, the 100%-removals commitment, the total edge-block on mckinsey.com, and the honest EWP-methodology intersection, each with the exact source and re-check attempt.
EWP contract 0x76c17C…A14B settles real-world ecological labor on Base mainnet: fund → claim → prove → approve → on-chain settlement → carbon retirement where ecological. Every step is publicly checkable by a plain client, the opposite posture of the domain this page tried to read.
What this package is, and isn't
Isn't: a partnership pitch, an engagement request, a claim that mckinsey.com's bot-blocking is a flaw, or any claim of affiliation or contact with McKinsey.
Is: a credit-first read of McKinsey's own public commitments, an honest report of what a plain passive client actually sees on mckinsey.com, and a note on where EWP's methodology rigor overlaps with McKinsey's own consulting frameworks.
McKinsey helped design the price mechanism durable removal now runs on. Its own front door is built for people, not machines: EWP is built the other way around: every settlement is a public, checkable receipt from the first packet.
