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

@strixgov/capabilities-mcp-common

v0.1.1

Published

Pre-classified capability registry for popular MCP servers (Slack, GitHub, Linear, Notion, Filesystem, Postgres, Email/SMTP/Gmail). Drop-in starter for @strixgov/tool-gateway.

Readme

@strixgov/capabilities-mcp-common

Pre-classified capability registry for popular MCP servers — Slack, GitHub, Linear, Notion, Filesystem, Postgres, Email. Drop-in starter for @strixgov/tool-gateway and @strixgov/mcp-adapter.

npm install @strixgov/capabilities-mcp-common @strixgov/tool-gateway

What's in it

Capability IDs follow the convention mcp.<server>.<tool>. 129 classifications across seven servers:

  • Slackmcp.slack.* (13 tools): reads LOW, outbound messages and canvases MEDIUM, drafts LOW.
  • GitHubmcp.github.* (~30 tools): reads/listings LOW, comments and branch ops MEDIUM, push/PR creation HIGH, merge_pull_request CRITICAL (irreversible).
  • Linearmcp.linear.* (10 tools): reads LOW, mutations MEDIUM, delete HIGH.
  • Notionmcp.notion.* (38 tools): reads LOW, page/database mutations MEDIUM, API-delete-a-block HIGH. Pack covers both Notion's older notion-* tool-naming convention (notion-fetch, notion-create-pages, ...) and the modern @notionhq/notion-mcp-server API-* convention (API-retrieve-a-page, API-post-search, ...) so the same pack matches whichever upstream you're wrapping.
  • Filesystemmcp.filesystem.* (11 tools): schema introspection LOW, write/edit MEDIUM, move_file HIGH. delete/symlink/chmod deliberately absent — heuristic CRITICAL handles them.
  • Postgresmcp.postgres.* (14 tools): schema introspection LOW, SELECT MEDIUM (exfiltration discipline — not auto-allowed), write_query / DDL HIGH. drop/truncate/arbitrary-SQL deliberately absent.
  • Email/SMTP/Gmailmcp.email.* (17 tools): mailbox reads LOW, reversible mutations MEDIUM, send_email / reply / forward HIGH (irreversible once delivered), delete_email HIGH.

NSA MCP report alignment

NSA Cybersecurity Information U/OO/6030316-26 | PP-26-1834 | May 2026 Ver. 1.0 warns that MCP's flexible-by-design protocol leaves per-call admission decisions to implementers — and that many MCP server implementations do not ship with a deny-by-default posture. This package is the default-deny starter for the seven popular MCP servers it covers: 129 tools pre-classified by risk tier (LOW / MEDIUM / HIGH / CRITICAL) with READ / WRITE / EXECUTE annotations, and a suggestedPolicy() that fails closed on unknown tools. Operators can override per-tool; the discipline is that overrides are explicit and auditable, not inherited from "no policy was defined." The durable map from each NSA-named concern to the file + invariant that addresses it lives at docs/launch/2026-05-23-nsa-mcp-technical-companion.md.

Suggested-policy semantics

suggestedPolicy() applies risk-aware defaults:

  • CRITICAL → DENY (operator must explicitly elevate)
  • LOW READ → ALLOW (schema introspection, file listing, mailbox reads — structurally safe)
  • MEDIUM / HIGH READ → APPROVAL_REQUIRED (Postgres SELECT and similar — auto-allow would expose exfiltration vectors)
  • WRITE / EXECUTE at any non-CRITICAL risk → APPROVAL_REQUIRED
  • Default → DENY (fail-closed for any unclassified tool)

This intentionally does NOT auto-allow every READ — that discipline shift happened when the Postgres pack landed, because SELECT * FROM users is the most common privacy-incident vector and pinning it at LOW READ would silently weaken the default deployment posture.

Usage

Pull the whole common set:

import { createGateway } from "@strixgov/tool-gateway";
import {
  mcpCapabilityMap,
  suggestedPolicy,
} from "@strixgov/capabilities-mcp-common";

const gateway = createGateway({
  capabilities: mcpCapabilityMap(),
  policy: suggestedPolicy(),
  // ...
});

Or just one server:

import { slackCapabilities }      from "@strixgov/capabilities-mcp-common/slack";
import { githubCapabilities }     from "@strixgov/capabilities-mcp-common/github";
import { linearCapabilities }     from "@strixgov/capabilities-mcp-common/linear";
import { notionCapabilities }     from "@strixgov/capabilities-mcp-common/notion";
import { filesystemCapabilities } from "@strixgov/capabilities-mcp-common/filesystem";
import { postgresCapabilities }   from "@strixgov/capabilities-mcp-common/postgres";
import { emailCapabilities }      from "@strixgov/capabilities-mcp-common/email";

Compose with the Claude Code companion pack:

import { claudeCodeCapabilities } from "@strixgov/capabilities-claude-code";
import { allMcpCapabilities } from "@strixgov/capabilities-mcp-common";

const capabilities = Object.fromEntries(
  [...claudeCodeCapabilities, ...allMcpCapabilities].map((c) => [c.id, c]),
);

Override before shipping

These are starter classifications. Override per-environment:

import { mcpCapabilityMap } from "@strixgov/capabilities-mcp-common";

const caps = mcpCapabilityMap();
// Production: never touch the default branch automatically.
caps["mcp.github.push_files"].risk = "CRITICAL";
caps["mcp.github.create_pull_request"].risk = "CRITICAL";

License

MIT