npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@seenty/mcp

v0.2.0

Published

Seenty MCP server — query your monitors, uptime and security findings (secrets, cloud misconfigs, CVEs) from AI clients

Readme

@seenty/mcp

Seenty MCP server — query your uptime monitors, check history and security findings from AI clients (Claude Desktop, Claude Code, Cursor, VS Code).

Ask things like:

  • "Did any of my monitors go down today?"
  • "What's the uptime of my landing page this month?"
  • "Is my security ok? Anything critical?"
  • "Do I have exposed secrets in my repos?"
  • "Which AWS users are missing MFA?"

Read-only by design. The server only exposes read tools with scoped API keys — it cannot create, modify or delete anything. Secret values, code snippets and cloud account IDs are masked or removed by the API before reaching the AI client.

Setup

1. Create an API key

In Seenty, go to Settings → API Keys → Generate New Key and select the permissions you want: "Read monitors & uptime" (monitors:read) and/or "Read security findings" (findings:read). Copy the sk_live_... key (shown only once). API access requires the Starter plan or above.

Treat the key like a password. It is read-only and revocable at any time from the same screen.

2. Configure your AI client

Claude Desktop (claude_desktop_config.json):

{
  "mcpServers": {
    "seenty": {
      "command": "npx",
      "args": ["-y", "@seenty/mcp"],
      "env": { "SEENTY_API_KEY": "sk_live_..." }
    }
  }
}

Claude Code:

claude mcp add seenty -e SEENTY_API_KEY=sk_live_... -- npx -y @seenty/mcp

Cursor (.cursor/mcp.json): same shape as Claude Desktop.

VS Code (.vscode/mcp.json — prompts for the key instead of storing it in plaintext, recommended):

{
  "inputs": [
    {
      "id": "seenty-key",
      "type": "promptString",
      "password": true,
      "description": "Seenty API key (monitors:read)"
    }
  ],
  "servers": {
    "seenty": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@seenty/mcp"],
      "env": { "SEENTY_API_KEY": "${input:seenty-key}" }
    }
  }
}

Tools

| Tool | Scope | What it does | |---|---|---| | list_monitors | monitors:read | List monitors with current status (filter by status, search by name/URL) | | get_monitor | monitors:read | Detail for one monitor + active incident + 5 recent incidents | | get_check_history | monitors:read | Raw check logs in a time range, with a failure summary | | get_uptime_stats | monitors:read | Aggregated uptime % and response time series (24h/7d/30d/12mo) | | get_security_summary | findings:read | Security posture overview: open findings by severity, source and type + top critical | | list_findings | findings:read | Security findings across domains, AWS, Azure and repos (secrets, misconfigs, CVEs...) | | get_finding | findings:read | Full detail for one finding with redacted evidence and remediation data |

Environment variables

| Variable | Required | Description | |---|---|---| | SEENTY_API_KEY | yes | API key with the monitors:read and/or findings:read scopes (sk_live_...) | | SEENTY_API_URL | no | API base URL override (defaults to https://engineapi.seenty.com) |

Development

npm install
npm run build
npx @modelcontextprotocol/inspector node dist/index.js