NPM Sentinel MCP

Created By
Nekzusa year ago
A powerful Model Context Protocol (MCP) server that revolutionizes NPM package analysis through AI.
Overview

What is NPM Sentinel MCP?

NPM Sentinel MCP is a powerful Model Context Protocol (MCP) server designed to revolutionize NPM package analysis through AI, providing real-time intelligence on package security, dependencies, and performance.

How to use NPM Sentinel MCP?

To use NPM Sentinel MCP, integrate it with Claude and Anthropic AI by configuring your claude_desktop_config.json or using NPX commands to run the MCP server for package analysis.

Key features of NPM Sentinel MCP?

  • Version analysis and tracking
  • Dependency analysis and mapping
  • Security vulnerability scanning
  • Package quality metrics
  • Download trends and statistics
  • TypeScript support verification
  • Package size analysis
  • Maintenance metrics
  • Real-time package comparisons

Use cases of NPM Sentinel MCP?

  1. Analyzing security vulnerabilities in NPM packages.
  2. Tracking package versions and dependencies for better management.
  3. Comparing multiple packages to make informed decisions.

FAQ from NPM Sentinel MCP?

  • Can NPM Sentinel MCP analyze all NPM packages?

Yes! It can analyze any package available in the NPM registry.

  • Is there a cost to use NPM Sentinel MCP?

No, it is free to use under the MIT License.

  • How does NPM Sentinel MCP ensure security?

It scans for known vulnerabilities and provides security advisories for packages.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Nekzus
Star
2
Language
TypeScript
License
MIT license
Tags

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago