# intercom probes, 2026-09-28T06:21Z, from a cloud container (one IP), no credentials, no payment
# Responses are cut at 6000 bytes (initialize), 20000 (tools/list), 2500 (protected resource), 9000 (authorization server), 4000 (REST). Nothing here was sent with a credential.

## 1. MCP initialize, POST https://mcp.intercom.com/mcp
$ curl -sS -i -m 25 -X POST https://mcp.intercom.com/mcp -H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' -d '<initialize>'
HTTP/1.1 200 Connection Established

HTTP/2 401 
date: Mon, 28 Sep 2026 06:21:34 GMT
content-type: application/json
content-length: 79
www-authenticate: Bearer realm="OAuth", error="invalid_token", error_description="Missing or invalid access token"
set-cookie: __cf_bm=[redacted by the prober: a session cookie, never published]
server: cloudflare
cf-ray: a420a6132d8a6498-BOS

{"error":"invalid_token","error_description":"Missing or invalid access token"}

## 2. Protected-resource metadata, GET https://mcp.intercom.com/.well-known/oauth-protected-resource/mcp (not named in the challenge; the path-aware well-known URI, the first fallback the specification names)
HTTP/1.1 200 Connection Established

HTTP/2 404 
date: Mon, 28 Sep 2026 06:21:35 GMT
content-type: text/plain; charset=UTF-8
content-length: 13
set-cookie: __cf_bm=[redacted by the prober: a session cookie, never published]
server: cloudflare
cf-ray: a420a616dfc9121b-BOS

404 Not Found

## 2b. Protected-resource metadata, GET https://mcp.intercom.com/.well-known/oauth-protected-resource (the root well-known URI, the second fallback; tried because step 2 answered 404, not 200)
HTTP/1.1 200 Connection Established

HTTP/2 404 
date: Mon, 28 Sep 2026 06:21:35 GMT
content-type: text/plain; charset=UTF-8
content-length: 13
set-cookie: __cf_bm=[redacted by the prober: a session cookie, never published]
server: cloudflare
cf-ray: a420a61a9b2c8f84-BOS

404 Not Found

## 3. Authorization-server metadata: no authorization_servers in step 2

## 4. REST, GET https://api.intercom.io/me, no Authorization header
HTTP/1.1 200 Connection Established

HTTP/2 401 
date: Mon, 28 Sep 2026 06:21:36 GMT
content-type: application/json; charset=utf-8
status: 401 Unauthorized
vary: Accept
x-intercom-version: 6e58849ed195d3709526dc7f0fdd8dce64c603f8
www-authenticate: Basic realm="intercom.io"
x-request-id: 0032o04tosqtq2oab7c0
x-frame-options: SAMEORIGIN
cache-control: no-cache
strict-transport-security: max-age=31556952; includeSubDomains; preload
referrer-policy: strict-origin-when-cross-origin
x-xss-protection: 1; mode=block
x-request-queueing: 0
x-runtime: 0.004662
x-content-type-options: nosniff
server: nginx

{"type":"error.list","request_id":"0032o04tosqtq2oab7c0","errors":[{"code":"missing_authorization","message":"No authorization was provided"}]}