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

@sysdig/mcp-core

v0.4.0

Published

Product-agnostic MCP server plumbing for Sysdig MCP servers (transport, OAuth proxy, metrics, telecaster, tool-authoring kit, e2e testkit)

Readme

@sysdig/mcp-core

Product-agnostic plumbing for building Model Context Protocol servers on top of Sysdig REST APIs.

This package contains everything that is not specific to a single Sysdig product: transport selection (stdio + streamable HTTP), the OAuth2 proxy, credential/env resolution, the SysdigClient fetch wrapper, Prometheus metrics, optional Telecaster instrumentation, the shared platform tools (3 customer/user tools plus 13 platform IAM tools for teams/users/roles), the tool-authoring kit, and the e2e testkit. A product package (e.g. @sysdig/secure-mcp-server) consumes it, registers its own domain tools, and hands the result to startServer().

Installation

npm install @sysdig/mcp-core zod

zod is a peer dependency (^3.25 || ^4.0); install it alongside this package.

Usage

import { startServer } from "@sysdig/mcp-core";
import { getClient, toolError, READ_ONLY, WRITE } from "@sysdig/mcp-core";

startServer({
  product: "SDS",                 // Sysdig product code (SDS = Secure, SDC = Monitor)
  serverName: "sysdig-secure",
  serverVersion: "1.0.0",
  metricsPrefix: "secure_mcp_",
  logPrefix: "[secure-mcp-server]",
  registerTools(server) {
    // Core auto-registers the shared platform tools first, then calls this.
    server.registerTool(
      "my_tool",
      { description: "…", inputSchema: { /* zod */ }, annotations: READ_ONLY },
      async (params, extra) => {
        const client = getClient(extra.sessionId);
        const data = await client.get("/some/endpoint");
        return { content: [{ type: "text", text: JSON.stringify(data) }] };
      },
    );
  },
});

startServer(config)

Boots the whole server given a ServerConfig. Transport is selected via the SYSDIG_MCP_TRANSPORT env var (stdio default, or http). Everything product-specific is threaded through ServerConfig; everything else is read from process.env.

| Field | Required | Description | | --- | --- | --- | | product | yes | Sysdig product code, threaded into the OAuth _product= param | | serverName | yes | MCP server name advertised to clients | | serverVersion | yes | MCP server version advertised to clients | | registerTools | yes | Callback that registers product tools on the McpServer | | metricsPrefix | yes | Prometheus metric name prefix | | defaultHost | no | Last-resort fallback host (default https://app.sysdigcloud.com) | | logPrefix | no | Log-line prefix | | serviceDocumentationUrl | no | Documentation URL advertised in OAuth metadata |

Tool-authoring kit

Domain tools import their helpers from this package, not from a relative path:

  • getClient(sessionId) — resolves the SysdigClient (stdio singleton or per-session HTTP client).
  • toolError(...) — builds a standard MCP error result.
  • READ_ONLY / WRITE — tool annotation presets.

Every SysdigClient request method (get, getOrNull, getText, post, put, patch, delete) accepts an optional trailing RequestOptions argument for call-specific overrides. Its headers are merged over the client's defaults (Authorization, Content-Type, Accept), with caller-supplied values winning on key collision — e.g. to attach an x-sysdig-request-metadata header on a single call:

await client.get("/prometheus/api/v1/query", {
  headers: { "x-sysdig-request-metadata": JSON.stringify({ source: "sysdig_mcp" }) },
});

Testkit

End-to-end helpers live under the @sysdig/mcp-core/testkit entry point (matrix reconciliation, the spawn-over-stdio runner, pickFirstId, reporting).

License

Proprietary — © Sysdig, Inc. See the repository for details.