Partner MCP servers can authenticate and authorize incoming traffic using three complementary defense-in-depth ingress controls:
Authorization: Bearer <token>): Cryptographically or statefully validates user-linked (user_oauth) or machine-to-machine (m2m) tokens issued by /oauth/token.dns.promises.reverse(ip)), verifies the hostname ends with .google.com, .googlebot.com, or .googleusercontent.com, and performs a forward A/AAAA lookup (dns.promises.lookup(host)) confirming the hostname resolves back to the connecting IP.108.177.64.0/20, 142.250.88.0/22, 172.217.80.0/20, 192.178.20.0/22, 192.179.0.0/20, 74.125.232.0/24, 136.121.40.0/21).Why Forward Confirmation Matters in Mode B
An attacker controlling their own IP block can configure a reverse PTR record claiming to be crawler.googlebot.com. Forward-Confirmed Reverse DNS (FCrDNS) defeats PTR spoofing by verifying that a forward DNS lookup of crawler.googlebot.com resolves back to the exact connecting source IP.
Select a sample source IP (such as a verified crawler IP 66.249.66.1, a published outbound CIDR IP 142.250.88.14, a spoofed PTR attacker IP 203.0.113.99, or an external IP 198.51.100.42) and an optional OAuth 2.1 Bearer token to evaluate all 3 ingress security modes side-by-side.