MCP Observatory
npm analyzed 1.4.1 unconfirmed MCP

@frontmcp/plugin-cache

v1.4.1
npm

Cache plugin for FrontMCP - Redis, Vercel KV, and in-memory caching with automatic tool result caching

maintainer
davidfrontegg
license
Apache-2.0
first seen
2026-06-09
last seen
2026-06-16
releases · 30d
3
short id
risk 10/100 · heuristic grade
A minimal
  • capability exposureinferred+4
  • inherited (deps)attested+15
  • trust mitigatorsmixed−9

attestedinferredmixed

The A–E grade is our heuristic synthesis — a "review this" prompt, not a verdict. Each factor is tagged by what backs it: attested (a verifiable record), reported (a third party's claim), or inferred (our own heuristic, e.g. permissions). See methodology.

graded 15m ago · see ecosystem CVEs →

risk trajectory 2 movements
  • A · 6 → A · 10
  • A · 0 → A · 6
capability exposure grade factor +4
Inferred surface — each links to servers holding it:
vulnerabilities 0 CVEs

No known CVEs for this server.

inherited (deps) · grade factor +15

inherited via dependencies 4
HIGH
mcp-from-openapi is Vulnerable to SSRF via $ref Dereferencing in Untrusted OpenAPI Specifications via @frontmcp/sdk · 1 hop CVE-2026-39885 fixed in 2.3.0
HIGH
@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse via @frontmcp/sdk · 3 hops CVE-2026-25536 fixed in 1.26.0
HIGH
Anthropic's MCP TypeScript SDK has a ReDoS vulnerability via @frontmcp/sdk · 3 hops CVE-2026-0621 fixed in 1.25.2
HIGH
Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default via @frontmcp/sdk · 3 hops CVE-2025-66414 fixed in 1.24.0
tool safety all quiet

No tool-safety findings — heuristic detectors run on the compute-risk cadence; a finding appears when a tool trips a rule.

embed badge readme-ready
live risk-grade badge preview [![MCP Observatory risk grade](https://mcpobservatory.com/servers/npm:@frontmcp/plugin-cache/badge.svg)](https://mcpobservatory.com/servers/npm:@frontmcp/plugin-cache/security)

Heuristic, inferred signals — false positives (legitimately powerful tools, forks, language ports) are expected. Treat each as "review this", not a verdict. See the ecosystem-wide picture on the security hub, or the fleet security of davidfrontegg.