github analyzed 574fc64

Context7

github

Fetch up-to-date, version-specific documentation and code examples directly into your prompts. Enhance your coding experience by eliminating outdated information and hallucinated APIs. Simply add `use context7` to your questions for accurate and relevant answers.

maintainer
upstash
license
first seen
2026-05-22
last seen
2026-06-16
releases · 30d
0
short id
risk59/100 · heuristic grade
C elevated
  • capability exposureinferred+22
  • recent driftinferred+20
  • tool safetyinferred+25
  • trust mitigatorsmixed−8

inferredmixed

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 12m ago · see ecosystem CVEs →

capability exposuregrade factor +22
Inferred surface — each links to servers holding it:
vulnerabilities0 CVEs

no known CVEs for this server.

tool safety3 findings · grade factor +25
  1. hightool poisoningresolve-library-id

    model-imperative: "You MUST"

  2. hightool poisoningquery-docs

    model-imperative: "You must"

  3. lowexfiltration comboresolve-library-id

    single tool reads + sends: shell, net, db

skills & danger signalsgithub-tarball
other grade factorsevidence elsewhere
embed badgereadme-ready
live risk-grade badge preview [![MCP Observatory risk grade](https://mcpobservatory.com/servers/smithery:upstash/context7-mcp/badge.svg)](https://mcpobservatory.com/servers/smithery:upstash/context7-mcp/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 upstash.