npm not analyzable

local-mcp

v3.0.280
npm

LMCP — connect Claude Desktop, Cursor, Windsurf to Mail, Calendar, Contacts, Teams, OneDrive on macOS. Privacy-first: all data stays on your Mac.

maintainer
lanchuske
license
SEE LICENSE IN LICENSE
first seen
2026-05-22
last seen
2026-06-14
releases · 30d
102
short id
riskinsufficient evidence

Insufficient evidence to grade. This server's source has not been statically analyzed, so a low grade would only mean "nothing found", not "nothing there". We don't show a reassuring grade we can't stand behind. Attested signals (CVEs, provenance) below still apply.

Once the source is analyzed (see the analysis flag in the header), a graded score appears here. How analysis works: methodology.

graded 10m ago · see ecosystem CVEs →

capability exposuregrade factor +35
Inferred surface — each links to servers holding it:
vulnerabilities1 CVEs · grade factor +0
NONE
MAL-2026-4601 affects []
tool safety1 findings · grade factor +0
  1. highdangerous code

    env-secret-flows-to-network-js: A process environment value (often a secret/token) flows into a network call — possible credential exfiltration. (/tmp/obs-code-aTyMTA/package/setup

other grade factorsevidence elsewhere
embed badgereadme-ready
live risk-grade badge preview [![MCP Observatory risk grade](https://mcpobservatory.com/servers/npm:local-mcp/badge.svg)](https://mcpobservatory.com/servers/npm:local-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 lanchuske.