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

@jamjet/mcp-threat

v0.1.0

Published

Deterministic MCP threat controls: tool-definition drift, shadowing, token passthrough, trust baseline, and MCP Security Receipts. Pure, portable, reusable across JamJet MCP adapters.

Downloads

125

Readme

@jamjet/mcp-threat

Deterministic threat controls for MCP traffic: tool-definition drift, tool shadowing, token passthrough, and a local trust baseline, with a signed-hash MCP Security Receipt for every decision. Constraint, not classification: every detector is a pure function over tool definitions and call context, so the same input always produces the same finding and the same decision.

Used by @jamjet/mcp-shim and @jamjet/ext-authz. No network calls, no model calls, no telemetry.

Install

npm install @jamjet/mcp-threat

What it detects

| Detector | Risk it constrains | |---|---| | detectDrift | A server changed a tool's definition after you trusted it (rug pull) | | detectShadowing | A tool name impersonates or collides with one from another server | | detectTokenPassthrough | Tool arguments smuggle bearer tokens or JWTs to a third party | | first-seen baseline | Calls to servers you have never approved |

Usage

Evaluate a tools/list against your trust baseline, then gate each tools/call:

import {
  loadTrustBaseline, loadThreatConfig,
  evaluateToolsList, evaluateCall,
  decideFromFindings, buildMcpSecurityReceipt, appendReceipt,
} from '@jamjet/mcp-threat'

const baseline = loadTrustBaseline()          // ~/.jamjet/mcp-trust.lock by default
const config = loadThreatConfig()

const listEval = evaluateToolsList(server, advertisedTools, baseline, config)

const callEval = evaluateCall({
  server,
  tool,
  args,
  serverUnverified: listEval.serverUnverified,
  flagged: listEval.flagged,
  config,
})

const { decision, finding } = decideFromFindings(callEval.findings, config)
if (decision === 'BLOCKED' && finding) {
  appendReceipt(receiptPath, buildMcpSecurityReceipt(finding, decision, 'tools/call', new Date().toISOString()))
  // refuse the call
}

Approve a server into the baseline after review:

import { approveServer, loadTrustBaseline, saveTrustBaseline } from '@jamjet/mcp-threat'

Receipts

buildMcpSecurityReceipt mints a canonical-JSON, SHA-256 hashed record of the finding and the decision. Receipts are append-only JSONL and are AgentBoundary-family artifacts: the hash covers the full receipt body, so any later edit is detectable.

Configuration

loadThreatConfig(policyPath) reads the threat block of a policy file (for example ~/.jamjet/policy.yaml); called with no path, or on any parse error, it returns the safe defaults in THREAT_DEFAULTS. Each detector maps to one knob: on_first_seen, on_definition_drift, on_tool_shadow, on_token_passthrough. See the jamjet-policy repo for the portable policy schema and the conformance suite.

License

Apache-2.0