Jiffy Intel — Threat intelligence for AI artifacts

Summary

MCP server advertised as a "usage analytics" helper forwards every tool-call argument it sees — including credentials passed as tool args, database URIs, and file paths — to a remote logging endpoint. The stated purpose is benign telemetry; the implementation is wholesale data capture.

Severity & confidence

Severity

Medium

Notable weakness with plausible abuse chains or partial mitigations already in place. Track, and resolve as part of your normal hardening cadence.

Confidence

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.

(?is)tools/call[\s\S]{0,500}(?:analytics|telemetry|metrics)\.(?:example|collector|ingest)

https?://[a-z0-9.-]+/(?:collect|ingest|telemetry|log)

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.

YARA-style pseudo-rule

rule jiffy_ti_2026_000037
{
    meta:
        source = "jiffy-intel"
        severity = "medium"
        description = "Auto-generated from Jiffy Intel indicators"
    strings:
    $tool_call_pattern_0 = "(?is)tools/call[\\s\\S]{0,500}(?:analytics|telemetry|metrics)\\.(?:example|collector|ingest)"
    $endpoint_1 = "https?://[a-z0-9.-]+/(?:collect|ingest|telemetry|log)"
    condition:
        $tool_call_pattern_0 or $endpoint_1
}

Auto-generated from the indicators above. Adapt syntax for your detection stack before deploying.

Affected tools

Tool	Versions	Status
Any MCP-capable agent	`*`	vulnerable
Claude Code	`*`	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.

usage-analytics-mcpMCP server
Removed
Source
MCP Registry
Versions
0.3.0 – 0.3.4
First observed
Feb 23, 2026
Last observed
Mar 21, 2026
dev-metrics-mcpMCP server
Removed
Source
GitHub (self-hosted)
Versions
1.0.0
First observed
Feb 27, 2026
activity-tracker-mcpMCP server
Under review
Source
MCP Registry
Versions
0.5.0
First observed
Mar 3, 2026

How to remediate

01Allowlist MCP servers.
02Deny servers whose stated telemetry scope includes tool-call arguments.
03Inspect egress via MCP gateway.

Timeline & sources

Timeline

First observedFeb 23, 20261 month ago
Last updatedApr 16, 20261 day ago
PublishedMar 11, 20261 month ago

Sources

scannercurated

References

blog.jiffylabs.aiJiffy Research

Jiffy Research — MCP Security Field Guide

https://blog.jiffylabs.ai/posts/mcp-security-a-security-teams-field-guide

owasp.orgOWASP

OWASP Top 10 for Agentic Applications

https://owasp.org/www-project-top-10-for-agentic-applications/

Related intel

Other entries of type Compromised Mcp, or the most recent published entries if no same-type matches exist.

Compromised McpLow

MCP server registers global tool names that shadow Jiffy primitives

MCP server that claims the tool name `scan` or `analyze` — names already used by Jiffy's first-party MCP. Collisions are resolved non-deterministically by the client, allowing the malicious server's tool to receive calls intended for Jiffy.

Jiffy IntelApr 28

Compromised McpCritical

Custom GPT Action schema includes an undocumented "admin" path

Custom GPT's OpenAPI schema defines a `/admin` path that the model can call, not mentioned in the GPT description. The path accepts arbitrary shell commands and runs them on the Action backend.