MCP server embeds requests session without certificate pinning
Summary
MCP servers making outbound HTTPS requests construct ad-hoc `requests.Session()` without any cert pinning or CA restriction. Enterprises with MITM-proxy requirements cannot enforce trust anchors.
Severity & confidence
Medium
Notable weakness with plausible abuse chains or partial mitigations already in place. Track, and resolve as part of your normal hardening cadence.
Confirmed
Observed directly by Jiffy scanners or validated by multiple independent sources. Indicators are reliable enough to drive automated action.
Indicators
Observed patterns and artifacts associated with this entry. Each indicator can be copied into your detection stack or SIEM.
(?i)requests\.Session\(\)
Detection rule
A YARA-style pseudo-rule auto-generated from the indicators above. Useful as a starting point — adapt the syntax for your target detection platform.
rule jiffy_ti_2026_000046
{
meta:
source = "jiffy-intel"
severity = "medium"
description = "Auto-generated from Jiffy Intel indicators"
strings:
$content_pattern_0 = "(?i)requests\\.Session\\(\\)"
condition:
$content_pattern_0
}Auto-generated from the indicators above. Adapt syntax for your detection stack before deploying.
Affected tools
| Tool | Versions | Status |
|---|---|---|
| MCP servers (Python) | * | vulnerable |
Example artifacts
Sanitized examples of artifacts Jiffy has observed exhibiting this pattern. Publisher handles are redacted; version ranges and status reflect the most recent scan.
- http-agent-mcpMCP serverStill live
- rest-client-mcpMCP serverStill live
How to remediate
- 01Require explicit CA trust bundle.
- 02Provide a jiffy-mcp-sdk wrapper that pins CA chains.
Timeline & sources
Timeline
- First observedMar 1, 20261 month ago
- Last updatedApr 20, 2026today
- PublishedMar 15, 20261 month ago
Sources
References
Scan for patterns like this
Point Jiffy at your GitHub org, IDE config, or a single artifact. Get a scored report in under a minute.
Start a free scan