Unverified50% confidenceFactExact time
The XCrawl MCP server supports passing the API key via the Authorization: Bearer request header, avoiding keys appearing in URLs.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/17/2026
First Seen
Valid until: 1/15/2027
Sources
Related Entities
Related Claims
UnverifiedFor MCP clients that cannot set request headers, the key can be written directly into the path: https://mcp.answerline.dev/<key>/mcp.77% similarUnverifiedWassenger MCP integration uses an Authorization: Bearer request header, which differs from the API's token request header.76% similarUnverifiedThe MCP server acts as an OAuth-protected resource and Entra ID as the authorization server; clients without a token receive an authentication challenge and discover the authorization metadata; the server must validate issuer, audience, validity period and scope or role; a token intended for a downstream API should not be automatically accepted as a token for accessing this MCP server.71% similarVerifiedAt the authorization layer, an MCP server can act as an intermediary proxy responsible for holding, managing, and rotating access credentials, so that the Agent itself does not need to directly handle the underlying keys70% similarUnverifiedThe current MCP specification supports HTTP Bearer Token as a transport-layer authentication mechanism, but makes no mandatory provisions regarding token issuance, binding of client identity, or server-side verification of token origin.69% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1055830API
curl https://kongchang.com/api/v1/knowledge/claims/1055830MCP
get_claim(id=1055830)