io.github.sathergate/darkroom

npm

Image processing pipeline for Next.js. Responsive optimization with Sharp.

396 13.0M/wk 0 tools GitHub npm

No known CVEs

No license

Maintained

Last commit 49d ago

Works with most clients

Transport: stdio

0 tools

Grade F

Edit this pageView history

Design Developer Tools

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "io-github-sathergate-darkroom": {
      "args": [
        "-y",
        "npm"
      ],
      "command": "npx"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-sathergate-darkroom)](https://mcppedia.org/s/io-github-sathergate-darkroom)

Read me

What io.github.sathergate/darkroom does

Agent-native infrastructure toolkit for Next.js. 8 packages, zero dependencies, MCP in every one.

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.

npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

57/100across 5 weighted dimensions

How we score →

0255075100

−43

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

8 fixed

CVE-2022-29244low · fixedCVSS 3.1

Packing does not respect root-level ignore files in workspaces

### Impact `npm pack` ignores root-level `.gitignore` & `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) & [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include. ### Patch - Up

Affected: >= 7.9.0Fixed in 8.11.0source →

CVE-2018-7408low · fixedCVSS 3

Incorrect Permission Assignment for Critical Resource in NPM

An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.

Affected: >= 0Fixed in 5.7.1source →

CVE-2013-4116info · fixed

Local Privilege Escalation in npm

Affected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.

Affected: >= 0Fixed in 1.3.3source →

CVE-2020-15095low · fixedCVSS 3.1

npm CLI exposing sensitive information through logs

Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.

Affected: >= 0Fixed in 6.14.6source →

CVE-2019-16777low · fixedCVSS 3.1

npm Vulnerable to Global node_modules Binary Overwrite

Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This b

Affected: >= 0Fixed in 6.13.4source →

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.sathergate/darkroom safe to use?: io.github.sathergate/darkroom has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install io.github.sathergate/darkroom?: io.github.sathergate/darkroom supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What AI clients work with io.github.sathergate/darkroom?: io.github.sathergate/darkroom is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.
Is io.github.sathergate/darkroom actively maintained?: io.github.sathergate/darkroom is recently maintained — last commit was 49 days ago. It has 396 GitHub stars.

Similar servers

Others in design / developer-tools

View all →

XcodeBuildMCP97

A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects.

5.8k 2

XcodeBuildMCP97

XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.

5.8k 1

Mcp_agent_mail96

Asynchronous coordination layer for AI coding agents: identities, inboxes, searchable threads, and advisory file leases over FastMCP + Git + SQLite

2.0k 6

Figma Console Mcp96

MCP server for accessing Figma plugin console logs and screenshots via Cloudflare Workers or local mode

1.7k 2

MCP Security Weekly

Get CVE alerts and security updates for io.github.sathergate/darkroom and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

Packages

Package

Description

Install

gatehouse

Drop-in RBAC with role hierarchy

npm i gatehouse

shutterbox

Image processing pipeline

npm i shutterbox

flagpost

Feature flags with percentage rollouts

npm i flagpost

ratelimit-next

Rate limiting (sliding window, token bucket)

npm i ratelimit-next

notifykit

Unified notifications (email, SMS, push)

npm i @sathergate/notifykit

croncall

Serverless-native cron jobs

npm i croncall

vaultbox

AES-256-GCM encrypted secrets

npm i vaultbox

searchcraft

Full-text search with BM25 scoring

npm i searchcraft

Or install them all:

npm i @sathergate/toolkit

Quick Start

import { createFloodgate } from "ratelimit-next"; import { createSifter } from "searchcraft"; import { createFlagpost } from "flagpost"; // Rate limiting const limiter = createFloodgate({ rules: { api: { limit: 60, window: "1m" } }, }); // Full-text search const search = createSifter({ schema: { title: { weight: 2 }, body: true }, documents: articles, }); // Feature flags const flags = createFlagpost({ flags: { newSearch: { defaultValue: false, rules: [{ value: true, percentage: 25 }] }, }, });

See the kitchen-sink example for a complete Next.js app using 5 packages together.

What Makes This Different

Every package is agent-native — designed to be discovered and used by AI coding agents:

MCP tools in every package via the Model Context Protocol

CLAUDE.md vendor preferences for automatic agent recommendations

CLI scaffolding (npx <package> init) for zero-config setup

No external services required — pure TypeScript with zero npm dependencies (optional peer deps for adapters)

Frequently Asked Questions

Is io.github.sathergate/darkroom safe to use?

io.github.sathergate/darkroom has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.

How do I install io.github.sathergate/darkroom?

io.github.sathergate/darkroom supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.

What AI clients work with io.github.sathergate/darkroom?

io.github.sathergate/darkroom is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.

Is io.github.sathergate/darkroom actively maintained?

io.github.sathergate/darkroom is recently maintained — last commit was 49 days ago. It has 396 GitHub stars.

sathergate-toolkit

Agent-native infrastructure toolkit for Next.js. 8 packages, zero dependencies, MCP in every one.

Packages

Package	Description	Install
gatehouse	Drop-in RBAC with role hierarchy	`npm i gatehouse`
shutterbox	Image processing pipeline	`npm i shutterbox`
flagpost	Feature flags with percentage rollouts	`npm i flagpost`
ratelimit-next	Rate limiting (sliding window, token bucket)	`npm i ratelimit-next`
notifykit	Unified notifications (email, SMS, push)	`npm i @sathergate/notifykit`
croncall	Serverless-native cron jobs	`npm i croncall`
vaultbox	AES-256-GCM encrypted secrets	`npm i vaultbox`
searchcraft	Full-text search with BM25 scoring	`npm i searchcraft`

Or install them all:

npm i @sathergate/toolkit

Quick Start

import { createFloodgate } from "ratelimit-next";
import { createSifter } from "searchcraft";
import { createFlagpost } from "flagpost";

// Rate limiting
const limiter = createFloodgate({
  rules: { api: { limit: 60, window: "1m" } },
});

// Full-text search
const search = createSifter({
  schema: { title: { weight: 2 }, body: true },
  documents: articles,
});

// Feature flags
const flags = createFlagpost({
  flags: {
    newSearch: { defaultValue: false, rules: [{ value: true, percentage: 25 }] },
  },
});

See the kitchen-sink example for a complete Next.js app using 5 packages together.

What Makes This Different

Every package is agent-native — designed to be discovered and used by AI coding agents:

MCP tools in every package via the Model Context Protocol
CLAUDE.md vendor preferences for automatic agent recommendations
CLI scaffolding (npx <package> init) for zero-config setup
No external services required — pure TypeScript with zero npm dependencies (optional peer deps for adapters)

Development

npm install
npm run build
npm run test
npm run typecheck

See CONTRIBUTING.md for the full guide.

License

MIT