Balmas MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to BALMAS local document anonymization with folder allowlists: Does secret minimization remain effective for newly supported document formats while returned content stays read-only?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Read files through privacy-preserving cleaned copies with locally consistent PII replacement tokens.

What we know

Discovery evidence describes a read-only file-access MCP that replaces PII with consistent local tokens before exposing content to agents.

Maintenance / activity evidence

balmas-mcp 0.3.0 published 2026-09-03T05:55:31.834Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: low.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Read-only according to discovery/package summary; exact filesystem scoping controls unresolved.
Authentication not yet verified.
Sensitive access: Local files, PII before redaction

Potentially valuable privacy boundary, but insufficient first-party evidence to assert exact protections.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Does secret minimization remain effective for newly supported document formats while returned content stays read-only?

The bounded review of the publisher's documented BALMAS local document anonymization with folder allowlists and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Potentially valuable privacy boundary, but insufficient first-party evidence to assert exact protections.
Read-only according to discovery/package summary; exact filesystem scoping controls unresolved.
PII transformation is described as local, but implementation and persistence details were not independently verified.
Sensitive access: Local files, PII before redaction
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
official docs/repository
supported file types
filesystem scope
PII categories
token persistence
auth/security model
First-party package/docs content could not be retrieved in this research pass.
Exact installation command beyond the npm package, auth model, supported file types, PII taxonomy and token persistence scope are unresolved.

Original activity observations

balmas-mcp 0.3.0 published 2026-09-03T05:55:31.834Z

Technical identity

npm/balmas-mcp

Exact implementation source: https://www.npmjs.com/package/balmas-mcp ↗
Reviewed resource type: MCP Server
Package identity: npm:balmas-mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry ↗
balmas-mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

Not runtime tested, no third-party installation, network authorization, paid calls, or mutation executed.
Do not claim production service is available based on README alone.
Publisher Claude Desktop env config; paid AI/privacy checks may transmit sensitive text
Official npm publisher package page README inspected for this exact npm identity; static research only. Some setup statements are conservatively summarized; no source code or live client execution checked. V2 review did not run any live client.
Check actual host syntax and supply credentials in secure client environment; do not paste placeholders verbatim.
Avoid write, payment, token transfer, publishing, sending, booking and remote account changes as tests.
Replace credential, action and registration placeholders; follow the matching publisher/client prerequisites. No execution performed.
Use the matching host, actual registration name and original installation environment; this does not revoke credentials.

Install / connect
Publisher instructions
Publisher Claude Desktop env config; paid AI/privacy checks may transmit sensitive text | Publisher npm README revisited on 2026-10-14; exact identity retained.
Reviewed setup example · Publisher instructions
npx -y balmas-mcp
Configure / authenticate
MCP100 setup guide
Register in client stdio config and set BALMAS_API_KEY (required) as environment variable.
Required environment variables: BALMAS_API_KEY
Check connection
Suggested check
Verify privacy tools listed, avoid sending private data as test.
Remove / uninstall / revoke
MCP100 setup guide
If your Claude Code MCP registration is named `balmas-mcp`, run the client removal command. For Claude Desktop/Cursor/Codex or another registered name, remove the matching entry in that host’s MCP settings. Hosted OAuth disconnect and stopping a self-hosted process are separate; npx has no permanent global package install.
Remove named client registration · Claude Code only · MCP100 composed guide
claude mcp remove balmas-mcp

Official Documentation & Sources

What it does

Discovery evidence describes a read-only file-access MCP that replaces PII with consistent local tokens before exposing content to agents.

Capability: Files & Knowledge
Resource type: MCP Server
Best fit: Read files through privacy-preserving cleaned copies with locally consistent PII replacement tokens.

Representative uses

Read redacted copies of local files
Preserve consistent token mapping so references remain usable across files

Limitations

First-party package/docs content could not be retrieved in this research pass.
Exact installation command beyond the npm package, auth model, supported file types, PII taxonomy and token persistence scope are unresolved.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Not documented in the reviewed sources
Permissions: Read-only according to discovery/package summary; exact filesystem scoping controls unresolved.
Data handling: PII transformation is described as local, but implementation and persistence details were not independently verified.
Cost: unknown
Risk and cautions: Potentially valuable privacy boundary, but insufficient first-party evidence to assert exact protections.

Access scope and cautions

Write actions: None in the reviewed inventory
Sensitive access: Local files PII before redaction
Risk level: moderate

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The available discovery description lists: Read redacted copies of local files; Preserve consistent token mapping so references remain usable across files. These descriptions do not establish a fully verified tool inventory.

Can it modify data or perform write operations?

The reviewed inventory lists no write actions. An empty inventory alone does not establish read-only authority. Discovery-described permission context (not independently verified): Read-only according to discovery/package summary; exact filesystem scoping controls unresolved.

What data-handling boundary should I consider?

PII transformation is described as local, but implementation and persistence details were not independently verified. Recorded sensitive-access context: Local files; PII before redaction.

What limitations and risks should I check before use?

Potentially valuable privacy boundary, but insufficient first-party evidence to assert exact protections. First-party package/docs content could not be retrieved in this research pass. Exact installation command beyond the npm package, auth model, supported file types, PII taxonomy and token persistence scope are unresolved. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.